테스트·보안 스킬

Retrieve AWS Security Agent findings from penetration tests and code reviews, store sensitive details outside Git tracking, and prioritize risks. Produces a readable remediation plan and helps fix the highest-priority issues after user confirmation.

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

• Retrieve findings from completed security scans
• Prioritize vulnerabilities by risk and confidence
• Store exploit details outside Git tracking

Run automated UI or API release tests through AWS DevOps Agent using an existing test profile. Check workflows, features, and regressions, follow progress updates, and save the completed test report as a Markdown file.

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

• Checking workflows that involve multiple user actions
• Testing features and regressions before a release
• Testing API endpoints

Review requirements or design documents alongside source code using AWS Security Agent. Identify security risks with STRIDE, a framework for classifying threats, and receive a report covering severity, affected assets, impacts, and recommended fixes.

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

• Review security risks before implementing a feature
• Analyze threats in requirements.md or design.md
• Check whether a design change weakens security

Run penetration tests, simulated attacks on a live web application, with AWS Security Agent. Register and verify the target domain, test selected endpoints, track progress, and save detailed findings in a Markdown report.

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

• Test a live web application for vulnerabilities
• Register and verify a target domain
• Check or stop a running penetration test

Check code changes since a chosen Git reference with AWS Security Agent. Run a standalone diff scan before a commit or pull request, then collect findings by severity in a local Markdown report.

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

• Checking uncommitted changes before a commit
• Scanning branch changes before a pull request
• Reviewing changes since a specific Git reference

Scan a workspace with AWS Security Agent by uploading its source code to AWS. Review verified findings by severity, see affected code and remediation guidance, save detailed reports, and manage scan progress or cancellation.

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

• Scanning an entire repository for vulnerabilities
• Reviewing critical and high-severity findings first
• Checking scan progress or stopping a scan

Use AWS Secrets Manager credentials in database connections and API calls through asm-exec, a command wrapper that resolves secret references at runtime. This pattern helps keep plaintext passwords, tokens, and API keys out of the agent's context.

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

• Connecting to a database with secret references
• Passing an API token to curl at runtime
• Supplying database credentials to a Docker container

Prepare a workspace for AWS Security Agent by creating or reusing an agent space, a service role with AWS permissions, and an S3 bucket. It links these resources and saves local configuration for subsequent scans and penetration tests.

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

• Prepare for the first security scan
• Check an existing Security Agent configuration
• Reuse an existing agent space

Plan, build, run, and analyze controlled failure experiments with AWS Fault Injection Service. Match failure scenarios to suitable actions, define targets and alarm-based stop conditions, configure permissions and logging, and examine how applications respond to disruption.

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

• Choose experiments for AZ outages or network failures
• Create experiment templates with targets and stop conditions
• Run and monitor resilience experiments in pre-production

Configure AWS WAF to filter traffic to web apps and APIs. Set up rules against common exploits, bots, login abuse, and HTTP floods, then use logs and observation mode to tune rules and reduce false positives.

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

• Attach web traffic filtering rules to an app or API
• Tune managed rules to reduce false positives
• Limit HTTP floods with rate-based rules

Test deployed Amazon MWAA workflows by checking readiness, starting a confirmed run, and monitoring its final status. Supports Python DAGs and Serverless YAML workflows, with diagnosis and fixes handed to related skills before controlled retesting.

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

• Test a deployed Python DAG
• Verify a Serverless YAML workflow runs successfully
• Retest workflows after fixes and redeployment

Assess which AWS security services fit a workload, including coverage and cost considerations. Review configuration and reported findings through read-only checks, distinguish verified evidence from unknowns, and prepare recommendations for separate implementation.

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

• Compare AWS security services for a workload
• Review GuardDuty or Inspector configuration and findings
• Assess protection coverage and improvement priorities

Automate website checks with Playwright, a browser automation tool. Create reusable scripts to test login flows, links, and layouts at different screen sizes, capture screenshots, and verify the page after each requested interaction.

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

• Comparing desktop and mobile layouts
• Testing login flows with supplied test credentials
• Checking website links and interactions

Build features or fix bugs by writing one failing test, then the smallest implementation that passes it. The skill focuses tests on agreed public interfaces, so they check observable behavior without depending on internal code structure.

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

• Building a feature with tests first
• Fixing a bug with a failing test
• Agreeing where integration tests should observe behavior

Guide feature development and bug fixes by writing a test first, checking that it fails for the expected reason, and adding only enough code to pass. Then clean up the code while keeping all tests passing.

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

• Developing a new feature from a failing test
• Reproducing a bug before fixing it
• Refactoring while keeping tests passing

Compare code with OpenSpec specifications, task lists, and design documents before archiving a change. Produce a report covering unfinished work, missing requirements, scenario coverage, and design consistency, with prioritized issues and specific recommendations.

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

• Checking unfinished tasks before archiving a change
• Comparing implementation with requirements and design
• Finding scenarios without implementation or tests

Verify completed changes with checks matched to their size, including builds, tests, and specification alignment. Record the evidence in a report, resolve failed checks through user decisions, and guide development branch cleanup.

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

• Check completed changes before closing development
• Compare implementation with specifications and design
• Decide how to handle failed verification checks

Checks work before reporting completion, committing changes, or creating a pull request. It requires fresh verification commands, reviews their output and exit codes, and ties claims about tests, builds, fixes, and requirements to actual evidence.

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

• Verify test results before reporting success
• Check a build before committing or opening a pull request
• Reproduce a bug to confirm its fix

Verify completed Comet Classic changes with builds, tests, security checks, and requirements checks. Record results and supporting evidence in a report, return failures to the build phase, and advance passing changes to the archive phase.

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

• Checking a completed Comet Classic change
• Choosing light or full verification for a change
• Recording test results and verification evidence

Verify a Classic change using builds, tests, security checks, and a final integrated code review. Choose light or full verification based on scope and risk, record evidence in a report, and route failures back for repair.

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

• Check a completed Classic implementation before archiving
• Verify core and high-risk scenarios for a small change
• Compare a larger implementation with specifications and design

Verify completed code changes with checks suited to their size, including builds, tests, and design comparisons where required. Save verification evidence and guide the user through deciding how to handle the development branch.

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

• Checking completed changes before closing development
• Comparing implementation with specifications and design
• Recording verification results

Check a running product against acceptance criteria and record evidence of its behavior. Report setup, build, and user journey checks separately, including observed results, skipped checks, and precise manual instructions when runtime access is unavailable.

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

• Checking whether a feature meets acceptance criteria
• Testing normal flows, empty states, and error cases
• Separating setup and build checks from behavior checks

Test Ralph workflow presets using shell scripts and collect logs, completion status, iteration counts, and event metrics. Use the results to investigate configuration failures, timeouts, and problems with how work passes between roles.

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

• Check presets after configuration changes
• Validate a newly added preset
• Audit the full preset collection

Validate terminal interfaces from screenshots or captured text. An AI judge checks required content, layout, and rendering against predefined or custom criteria, then reports pass or fail with specific feedback on problems.

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

• Checking terminal rendering after code changes
• Verifying screen state after interactions
• Testing layouts at different terminal sizes