테스트·보안 스킬

Audits Google Cloud Filestore instances for missing or outdated backups, overly broad file share access, and zone isolation requirements. Produces a health scorecard, prioritized findings, an instance inventory, and proposed backup remediation.

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

• Finding file shares without recent backups
• Auditing NFS access ranges and root privileges
• Checking physical zone isolation and separation

Evaluate whether Google SecOps rules detect threats described in articles or supplied text. Generate simulated attack logs, identify coverage gaps, summarize matching rules, and create rules for uncovered threats, with user approval before adding them.

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

• Evaluate detection coverage for threats described in a blog
• Test existing rules with simulated attack logs
• Review matching rules and their alerting status

Audit and strengthen security for applications running on GKE. Configure pod traffic restrictions, sandbox isolation, namespace security standards, and Secret Manager volume mounts to protect workloads at the application and namespace level.

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

• Auditing GKE security settings
• Restricting communication within a namespace
• Isolating risky pods and applying security standards

Audit Google Mobile Ads SDK integration in iOS, Android, or Unity projects. Check test IDs, ad units, SKAdNetwork IDs, adapter compatibility, and ad preloading, then report findings and next steps in a table.

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

• Audit mobile ad integration before launch
• Check for remaining test IDs and invalid formats
• Review SKAdNetwork IDs and adapter compatibility

Review agent skills for risky behavior, excessive permissions, and hidden data sharing. It combines static scanning, which checks known risk patterns without running code, with source review to produce an evidence-based installation verdict.

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

• Reviewing a skill before installation
• Checking permissions in an installed skill
• Investigating credential access or external data sharing

Create or improve unit tests for Apache ShardingSphere classes. Cover the target class’s behavior and affected branches, verify explicitly requested coverage goals, and consolidate suitable scenarios into parameterized tests, which run the same checks with different inputs.

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

• Add missing unit tests for a target class
• Verify an explicitly requested coverage target
• Consolidate suitable tests with different input data

Verify Kortix changes with focused tests and real inputs and outputs. This skill guides test placement, API and CLI workflows, browser checks, database verification, and reporting of results, including skipped cases.

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

• Verify a bug fix with focused tests
• Check API and CLI behavior through real inputs and outputs
• Test database query conditions

Build end-to-end tests that follow user journeys in browsers and mobile simulators or emulators. Guides e2e configuration, AI-driven actions, precise outcome checks, failure investigation, and exploratory bug hunts backed by reproducible tests.

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

• Testing browser user journeys with AI-driven actions
• Checking app flows on mobile simulators and emulators
• Investigating failed tests through reports and traces

Check new or updated pull requests in isolated checkouts, run the full test suite, and verify temporary test deployments through their public delivery path. Post pass or fail results with evidence to GitHub.

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

• Checking newly opened or updated pull requests
• Rechecking after a force-push or base branch change
• Finding failures in routing, caching, or redirects

Prepare draft responses to security questionnaires received in Gmail using approved answers and policies. Fill a copy in the original spreadsheet layout, flag uncertain questions, and save a reply draft for security review.

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

• Preparing a first draft of a prospect's security questionnaire
• Filling SIG, CAIQ, or custom spreadsheets with approved answers
• Identifying questions that need security team input

Track tests that pass and fail on unchanged code using GitHub CI history. Score their instability over multiple runs, propose reasoned skips in a pull request, maintain a tracking issue, and summarize findings in Slack.

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

• Investigate tests that alternate between passing and failing
• Propose temporary skips with evidence and reasons
• Track quarantined tests in one GitHub issue

Assess reported phishing emails by checking sender authentication, links, and attachments. Post a risk rating, supporting evidence, and a recommended action to Slack, leaving blocking, deletion, and other changes to the security team.

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

• Triage newly reported suspicious emails
• Reassess a specific reported email
• Explain the evidence behind a risk rating

Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.

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

• Reviewing GitHub repository access requests from Slack
• Preparing AWS IAM permissions for a specific task
• Routing sensitive access requests for additional review

Run Lighthouse audits locally across multiple site pages using Unlighthouse, without an API key or API quota usage. Receive median scores for performance, accessibility, best practices, and SEO, alongside individual page results and reports.

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

• Audit many site pages without using API quota
• Check for site-wide regressions after deployment
• Compare mobile and desktop audit results

Set up or run repeated verification in Codex with explicit checking commands and stopping conditions. This alias corresponds to Claude Code’s `/pua:loop` command and requires command output as evidence before reporting completion.

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

• Setting up repeated verification
• Defining verification commands
• Specifying when verification should stop

Review an authorized security issue in its private workflow. Check the affected code, assess whether the report is valid, explain severity and attack prerequisites, and propose a remediation plan with focused tests.

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

• Checking whether a vulnerability report is valid
• Assessing impact and severity
• Planning fixes and focused tests

Implement an authorized fix for a reviewed security issue, check the plan against current code, and add regression tests to catch recurrence. Verify affected components and open a pull request that closes the issue while respecting disclosure rules.

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

• Implementing an approved security remediation plan
• Rechecking a reviewed fix against current code
• Adding regression tests for a security boundary

Run OpenShell’s Release Canary checks to verify that published development packages and Helm charts install and support basic sandbox operations. Use workflow logs and local Kubernetes reproduction steps to investigate failures before a public release.

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

• Checking published development artifacts before release
• Testing changes to the Release Canary workflow
• Investigating installation or sandbox test failures

Generate an OpenShell SBOM, an inventory of software components, with Syft. Fill missing license details from public registries, export CSV files for compliance review, and inspect or validate SBOMs attached to container images.

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

• Generating a dependency inventory for a release
• Filling missing dependency license information
• Exporting CSV files for license review

Turn plain-language requirements and optional API documentation into OpenShell sandbox network policies in YAML. Define allowed destinations, programs, and API operations, with optional middleware settings for inspecting or transforming traffic and controlling what happens when processing fails.

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

• Restrict API access to reading operations
• Allow only specific API methods and paths
• Limit internal service access by program and IP range

Operate Chrome or Brave using signed-in browser sessions to verify deployed pages, reproduce bugs, inspect page structure, and examine errors or network traffic. An optional macOS bridge extends control to native applications and operating system input.

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

• Verify page appearance after deployment
• Reproduce blank pages and disappearing content
• Inspect console errors and network traffic

Strengthen existing tests with fast-check by checking properties across generated inputs. Find bugs that example tests miss and reduce failing inputs to small, reproducible cases. Property testing is available; the other listed workflows remain planned.

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

• Checking parser behavior across generated inputs
• Testing serialization and deserialization round trips
• Finding pure functions covered only by example tests

Map sensitive data across the systems you manage, explore what a compromised asset could expose, and maintain a risk register. Record likelihood, impact, owners, mitigations, and review dates to support ongoing security planning.

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

• Locating sensitive data across managed systems
• Assessing the impact of a compromised server or worker
• Recording risk owners, mitigations, and review dates

Evaluate AI agent outputs with code checks and model-based grading. Run repeated trials to measure reliability, compare prompts or models, and check whether changes reduce quality, with saved transcripts for reviewing the results.

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

• Comparing two prompts on the same test cases
• Checking quality after agent configuration changes
• Turning real failures into repeatable evaluation cases