테스트·보안 스킬

Create and repair C++ tests, configure GoogleTest and CTest, and investigate failures or inconsistent results. The workflow also covers measuring which code tests exercise and using runtime checks to detect memory errors and race conditions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing C++ unit and integration tests
• Configuring GoogleTest and CTest
• Investigating tests that fail inconsistently

Review Solidity automated market makers, liquidity pools, and token swaps using security checklists and safer code examples. Check repeated calls during transfers, manipulated prices, share calculations, swap limits, and administrator permissions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Auditing liquidity pool contracts
• Reviewing deposit and withdrawal calculations
• Adding swap limits and deadlines

Define success criteria before AI coding, then assess new capabilities and check that existing behavior still works using code, rules, models, or human review. Track repeated-attempt success metrics and reports to compare prompt changes, agent changes, or model versions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Defining success criteria before AI implementation
• Checking existing behavior after prompt or agent changes
• Measuring reliability across repeated attempts

Write Django and Django REST Framework tests with pytest-django, starting with tests before implementation. Covers test data generation, simulated external services, model and API checks, and coverage reports showing which code the tests exercise.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Developing Django features by writing tests first
• Testing API authentication and input validation
• Generating reusable test data

Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing coding agents on real development tasks
• Evaluating a new tool or model before adoption
• Checking performance after agent updates

Add regression tests to AI-assisted code changes so previously found bugs are checked automatically. Test required API fields and sandbox response contracts, then run tests and builds before AI review to catch recurring omissions and inconsistent behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add regression tests after fixing a bug
• Check required API response fields
• Review sandbox and production response consistency

Measure web page speed, API response times, and build or test duration. Save baseline measurements as JSON tracked in Git, then compare results before and after changes to identify performance regressions and assess launch targets.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing performance before and after a code change
• Investigating reports that a page feels slow
• Checking performance targets before launch

Have an AI agent assess its completed work for accuracy, completeness, clarity, actionability, and conciseness. Receive a scorecard with evidence, an average score, and prioritized improvements tied to the original request.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess code after a multi-file implementation
• Check deliverables after a multi-step workflow
• Evaluate a design document or written analysis

Trace button clicks and form actions through each state change to uncover conflicting updates, unintended resets, and asynchronous timing problems. Report where the final screen behavior differs from what the user expects, with specific fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating buttons that appear to do nothing
• Checking shared state after a major refactor
• Auditing critical user flows before release

Test deployed web pages through browser automation. Check forms, login flows, loading and responsiveness metrics, visual changes at three screen widths, and accessibility issues, then receive a report with fixes and a release verdict.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Testing a feature deployed to staging or preview
• Checking forms and login flows before release
• Comparing layouts at three screen widths

Test an authorized web application, map its exposed pages and inputs, and verify suspected vulnerabilities with reproducible evidence. Produce a security report covering confirmed findings, their impact, reproduction steps, and suggested fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check a staging web application for vulnerabilities
• Verify whether a suspected vulnerability is reproducible
• Compile evidence and fixes into a security report

Investigate suspected malicious changes in open-source software on GitHub by comparing repository history, APIs, and archives. Attempt to recover deleted evidence, identify signs of compromise, and produce a report separating verified facts from hypotheses.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate suspicious commits or workflow changes
• Attempt to recover commits hidden by rewritten history
• Trace possible credential leaks

Set up the 1Password CLI and use stored passwords or API keys in commands and configuration templates. Choose an authentication method, retrieve secret references, and pass credentials to processes through environment variables.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Installing and configuring the 1Password CLI
• Running commands with stored API keys
• Filling configuration templates with stored secrets

Test how API-accessible language models respond to attempts to bypass safety filters. The skill covers prompt templates, input transformations, parallel response comparisons, and Hermes configuration, with automated scoring of refusals, answer quality, and speed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Evaluating model resistance to safety-filter bypass attempts
• Comparing responses to transformed inputs
• Comparing refusals, answer quality, and speed across models

Find personal information exposed on data brokers and people-search sites, then manage removal requests for consenting individuals. Tracks submissions, checks whether listings disappear, schedules repeat scans, and collects steps that require human help.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding sites exposing personal information
• Managing removal requests for a consenting family member
• Checking progress and verifying removals

Test an app from the perspective of a frustrated, less technical user. Find confusing steps and barriers, separate actionable usability problems from personal complaints, and produce screenshots, suggested fixes, and prioritized tickets.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing usability before a launch or demo
• Checking the experience of a new user
• Finding friction in signup and subscription flows

Check code changes before committing with security scans, tests, linting, and an independent agent review. Compare failures against the previous baseline, then use a separate agent to fix reported problems and repeat verification.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking feature changes before a commit
• Scanning added code for secrets and injection risks
• Separating new test failures from existing failures

Guide development through test-driven development (TDD): write a test, confirm it fails, add minimal code, then clean up. Apply this cycle to features and bug fixes while checking that existing behavior still passes its tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding features with tests written first
• Reproducing a bug in a test before fixing it
• Refactoring while keeping tests passing

Independently reviews deliverables handed over through Kanban, checks them against acceptance criteria and test evidence, and records an approval, actionable change request, or escalation when a human decision or external prerequisite is needed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing deliverables against acceptance criteria
• Rechecking corrections after a change request
• Returning reproducible defects to the implementer

Explore a web app in the browser to find functional, visual, and usability issues. The skill organizes screenshots, console errors, and reproduction steps into a Markdown bug report, with findings grouped by severity and category.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Explore key user flows before release
• Check forms with valid, invalid, and empty input
• Document layout issues and JavaScript errors

Test local web applications with Playwright, a browser automation tool. Check frontend functionality, investigate interface behavior, capture screenshots, and inspect browser logs, with a helper script that manages one or more application servers during testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking buttons and forms in a local web app
• Investigating interface problems with screenshots and logs
• Testing with both frontend and backend servers running

Review a codebase for bugs, security risks, failures under expected load, missing tests, slow paths, and unnecessary code. Receive prioritized findings with concrete failure cases, small proposed fixes, and the consequences of leaving each issue unresolved.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess the quality of an inherited codebase
• Find risks under expected concurrent usage
• Identify unnecessary code and dependencies

Plan a paid evaluation with predefined success criteria, comparison groups, decoy items, and stopping rules. Rehearse without spending, then run a three-item paid pilot and use its spending table to inform approval.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Define evaluation criteria before spending
• Rehearse an evaluation at zero cost
• Check spending with a three-item paid pilot

Audit an existing test suite to find low-value or duplicate tests and code kept solely for those tests. Receive findings for review, with changes limited to batches you explicitly approve.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing the value of existing tests
• Finding duplicate tests
• Finding code kept only for tests