테스트 설계, 취약점 진단, 품질 보증 (1.4만건)
Operate E2B agent sandboxes using the CLI. Use when user needs to run code in isolation, test packages, execute commands safely, or work with binary files in a sandbox environment. Keywords: sandbox, e2b, isolated environment, run code, test code, safe execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test agent delegation patterns to verify hierarchy and escalation paths. Use after modifying agent structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Handle failures and errors during workflow. Use when build breaks, tests fail unexpectedly, or agent gets stuck. Semi-automatic recovery with user confirmation for destructive actions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create .agent/baseline.md and later compare against it. Use when capturing baseline build/lint/test results or investigating newly introduced findings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Evaluate a codebase for agent-friendliness based on autonomous agent best practices. Use when asked to "evaluate for agents", "check agent readiness", "audit for autonomous execution", "assess agent-friendliness", or when reviewing infrastructure for unattended agent operation. Also use when asked about making a codebase more suitable for AI agents or autonomous workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement hooks for permission control and security in custom agents. Use when adding security controls, blocking dangerous operations, implementing audit trails, or designing permission governance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deterministic custom subagent selection helper. Use when you need a reproducible, auditable decision on which custom subagents to activate for a user query (runs scripts/agent_evaluator.py).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use these when you want low-noise lint/test output (good for LLM/CI logs) while staying aligned with repo policy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when architecting new Claude Code agents following Anthropic best practices. Guides through YAML frontmatter creation, agent structure definition, role boundaries, and validation. Critical for creating minimal agent files (~150 lines) with proper skill invocations. Examples: <example>Context: User wants to create a new agent for security auditing user: "Create a security-auditor agent" assistant: "I'll use the agent-creator skill to build this agent following Anthropic best practices" <commentary>New agent creation requires the agent-creator skill to ensure proper structure and YAML frontmatter.</commentary></example> <example>Context: Existing agent file is too verbose and needs refactoring user: "The architect agent is 2000 lines, refactor it to minimal structure" assistant: "I'll use the agent-creator skill to refactor this into a minimal ~150 line agent with a separate skill file" <commentary>Agent refactoring requires the agent-creator skill to separate identity from technical procedures.</commentary></example>
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Initialize or improve AGENTS.md files that define how coding agents operate in a repo. Use when asked to set up or replace an agent init command (Codex, Claude), standardize multi-agent behavior, or audit an existing AGENTS.md for clarity, commands, boundaries, and repo-specific context. For Claude Code, also create CLAUDE.md as a symlink to AGENTS.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and implement evaluation frameworks for AI agents. Use when testing agent reasoning quality, building graders, doing error analysis, or establishing regression protection. Framework-agnostic concepts that apply to any SDK.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Answer Engine Optimization (AEO) audit methodology for LLM visibility. Use when auditing brands for ChatGPT/Gemini mentions, checking LLM citations, analyzing AI search visibility, or when user mentions "AEO", "LLM visibility", "ChatGPT mentions", "Gemini citations", or "AI search optimization".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add a new AI provider to agentconfig.org's comparison system. Use when integrating a new coding assistant (e.g., Cursor, Claude Desktop, GitHub Copilot alternative) with proper type system updates, implementation data, UI components, tests, and documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze recent changes and add test coverage for HEAD commit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive documentation of Claude's capabilities for visual regression testing, CI/CD integration, and quality assurance automation. Use when setting up testing infrastructure, implementing visual regression, or understanding agent testing capabilities. (project)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate adversarial inputs, edge cases, and boundary test payloads for stress-testing LLM robustness
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert chaos engineer specializing in controlled failure injection, resilience testing, and building antifragile systems. Masters chaos experiments, game day planning, and continuous resilience improvement with focus on learning from failure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for adding new LLM models to Letta Code. Use when the user wants to add support for a new model, needs to know valid model handles, or wants to update the model configuration. Covers models.json configuration, CI test matrix, and handle validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review documentation for quality, clarity, SEO, and technical correctness. Optimized for Docus/Nuxt Content but works with any Markdown documentation. Use when asked to: "review docs", "check documentation", "audit docs", "validate documentation", "improve docs quality", "analyze documentation", "check my docs", "review my documentation pages", "validate MDC syntax", "check for SEO issues", "analyze doc structure". Provides actionable recommendations categorized by priority (Critical, Important, Nice-to-have).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete DataForSEO API integration for SEO data and analysis. Use when the user asks for keyword research, search volume, SERP analysis, backlink audits, competitor analysis, rank tracking, domain authority, technical SEO audits, content monitoring, Google Trends, or any SEO-related data queries. Covers all DataForSEO APIs including SERP, Keywords Data, DataForSEO Labs, Backlinks, OnPage, Domain Analytics, Content Analysis, Business Data, Merchant, App Data, and AI Optimization APIs. Outputs CSV files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the backend verification loop after Kotlin/Spring code changes — Kotlin style + unit tests via `gradlew verify`, plus integration tests when repos/migrations changed — and drive fixes until green. Use after editing backend code or when the user asks to verify/check the build.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Multi-step reasoning engine for complex analysis and systematic problem solving. Use when: (1) Complex debugging scenarios with multiple layers, (2) Architectural analysis and system design, (3) Problems requiring hypothesis testing and validation, (4) Multi-component failure investigation, (5) Performance bottleneck identification. Triggers: "--think", "--think-hard", "--ultrathink", "analyze step by step", "break down this problem", "systematic analysis". IMPORTANT: Do NOT use for simple single-step tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.