테스트·보안 스킬

OSINT username search across 400+ social networks. Hunt down social media accounts by username.

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

Supply chain investigation, evidence recovery, and forensic analysis for GitHub repositories. Covers deleted commit recovery, force-push detection, IOC extraction, multi-source evidence collection, hypothesis formation/validation, and structured forensic reporting. Inspired by RAPTOR's 1800+ line OSS Forensics system.

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

Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in, and reading/injecting secrets for commands.

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

The PRIMARY development workflow for the Archon project (remote-coding-agent). Use this skill instead of any PRP skills when working on Archon code. Routes to 10 specialized cookbooks based on what the user is trying to do: RESEARCH — "how does the orchestrator work?", "where is session state defined?", "trace the workflow execution flow", "what is IWorkflowStore?" INVESTIGATE — "should we use Drizzle or Prisma?", "what's the best way to add WebSockets?", "can we migrate to Turso?", "how do other projects handle rate limiting?" PRD — "write a PRD for dark mode", "spec out the notification feature", "product requirements for webhook retry" PLAN — "plan the auth refactor", "design the caching layer", "create an implementation plan for #42" IMPLEMENT — "implement the plan", "execute .claude/archon/plans/auth.plan.md", "build the feature from the plan", "code this up" REVIEW — "review PR #123", "review my changes", "code review the diff" DEBUG — "debug the failing test", "why is streaming broken?", "root cause analysis on the timeout issue" COMMIT — "commit these changes", "commit the auth refactor" PR — "create a PR", "open a pull request for this branch" ISSUE — "report this to gh", "create a gh issue", "log it in github", "file a bug for this", "create a feature request" This skill triggers on ANY development task: researching, investigating, planning, building, reviewing, debugging, committing, or shipping code. NOT for: Running Archon CLI workflows in worktrees (use /archon instead).

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

Use when the user wants to review a pull request, understand what a PR changes, assess risk of merging, or check for missing test coverage. Examples: "Review this PR", "What does PR #42 change?", "Is this PR safe to merge?"

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

Build, test, and debug Hermes Agent RL environments for Atropos training. Covers the HermesAgentBaseEnv interface, reward functions, agent loop integration, evaluation with tools, wandb logging, and the three CLI modes (serve/process/evaluate). Use when creating, reviewing, or fixing RL environments in the hermes-agent repo.

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

Replicate and validate a GitHub issue by spinning up Archon, analyzing the issue, and systematically testing all described symptoms using browser automation. Use when: User wants to reproduce a bug, validate a GitHub issue, confirm a reported problem, or investigate whether an issue is real before working on a fix. Triggers: "replicate issue", "reproduce issue", "validate issue", "confirm bug", "test issue", "can you reproduce", "try to replicate", "verify the bug". Capability: Checks out main, pulls latest, starts Archon, reads the GitHub issue, then uses agent-browser to systematically test every symptom and produce a findings report. NOT for: Fixing issues (use /archon or /exp-piv-loop:fix-issue), general UI testing (use /validate-ui).

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

Verify a released archon binary works end-to-end via a specific install path. Use when: cutting a new release, reproducing a user bug report on the released version, or validating that a hotfix binary actually works after a re-tag. Triggers: "test the release", "test 0.3.1 via brew", "verify the curl install", "smoke test the binary", "did the release binary work", "run /test-release", "verify the release". NOT for: testing dev work (use bun link directly), testing unreleased changes (build locally via scripts/build-binaries.sh first), or running the full validate suite (bun run validate is separate).

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

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

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

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

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

Complete security architecture overhaul for claude-flow v3. Addresses critical CVEs (CVE-1, CVE-2, CVE-3) and implements secure-by-default patterns. Use for security-first v3 implementation.

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

15-agent hierarchical mesh coordination for v3 implementation. Orchestrates parallel execution across security, core, and integration domains following 10 ADRs with 14-week timeline.

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

Systematic exploratory QA testing of web applications — find bugs, capture evidence, and generate structured reports

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

Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows

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

Core module implementation for claude-flow v3. Implements DDD domains, clean architecture patterns, dependency injection, and modular TypeScript codebase with comprehensive testing.

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

Manages Cargo.lock file updates and resolves --locked flag issues in CI/CD. Triggers when user mentions: - "cargo test --locked failed" - "cannot update the lock file" - "Cargo.lock is out of date" - "PR failed with --locked error" - "fix Cargo.lock"

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

Discover, build, verify, and optionally export (HTML, optional PDF) the evidence manifest of one SDD Composy task in evidence_required, routing it toward review_required. Use when acceptance evidence must be assembled or checked — 'juntar as evidências da task', 'gerar o relatório de evidências', 'verify the evidence manifest'. Do NOT use to run tests (sdd-qa), review code (sdd-review), or inspect the trace (sdd-trace).

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

Independent, traceable code review of one SDD Composy task in review_required against its approved PRD, stories, TechSpec, evidence, and project rules, with stable findings and severities. Use when a task passed QA and evidence — 'revisar a TASK-003', 'code review da task', 'review this task's diff'. Do NOT use for code review outside an SDD workspace (use the host code review), for QA (sdd-qa), or for verification (sdd-verify).

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

Independent quality assurance for one SDD Composy task in qa_required: CA coverage, unit/integration/E2E, accessibility, responsiveness, environment, and evidence inventory, producing the QA report and requesting evidence_required. Use when a task finished execution — 'rodar o QA da task', 'testar a TASK-003', 'validar a implementação'. Do NOT use for code review (sdd-review), the final verdict (sdd-verify), or test runs outside an SDD task.

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

Audit of existing Vue components in the project. Use when reviewing Vue design system consistency, identifying duplicate patterns, evaluating legacy components (Options API), or before implementing something new.

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

Accessibility auditing and remediation skill for Vue 3 + Reka UI. Use when reviewing components, verifying WCAG 2.1 AA, fixing ARIA issues, or validating keyboard navigation in Reka UI components.

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

Run a bounded, provider-neutral SDD Composy correction loop on one approved task (EXECUTE, QA, EVIDENCE, REVIEW, VERIFY; at most 3 iterations) with explicit approval, safe-stop guards, and fresh verification. Use to continue an approved TASK autonomously — 'rodar o loop na TASK-003', 'continuar a task até passar', 'start a loop on task 4'. Do NOT use for the host's recurring loop runner, for fleets (sdd-fleet), or for a task without human approval.

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

Implement exactly one SDD Composy task in the ready state with dependency preflight, TDD RED evidence, allowed paths, real verification commands, and the guarded transition to qa_required. Use when a ready task should be executed — 'executar a TASK-003', 'implementar a próxima tarefa', 'run task 4'. Do NOT use for changes without an approved task (sdd-quick), for autonomous multi-stage correction (sdd-loop), or for QA, review, or verification.

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

Adversarial verification of one SDD Composy task in verify_required: reproduce every claim with fresh commands, build the truth table, refute stale evidence, and produce the verdict that gates complete. Use when review is done and the task claims to be finished — 'verificar a TASK-003', 'a task está pronta mesmo?', 'is this task really complete'. Do NOT use for QA, code review, or a general 'verify my work' outside an SDD task.

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