테스트·보안 스킬

Orchestrate ambiguity auditing across selected layers with rubric-driven scoring, remediation flow, and next-step gating

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

Define security, attack surface, integration, and observability architecture with compliance escalation

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

Cascade approved evolution changes through downstream layers, assess impact, run consistency checks, and write evolution audit record

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

Smart Kotlin unit testing with auto-detection, coverage analysis, and AI edge cases. Use when generating tests for biz/ layer classes, analyzing test coverage gaps, or discovering edge cases.

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

How to run and test the docs/index.html AGSL shader web gallery locally (static server, WebGL2-capable Chrome flags, CDP verification hooks).

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

Use this skill for all verification: unit, component, E2E, native, and release checks. Required alongside mobile-core for every implementation.

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

Use this skill for any Ionic Vue + Capacitor mobile work: Vue architecture, Composition API, TypeScript, state, env config, shared conventions. Required for every implementation task alongside mobile-testing.

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

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

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

Use test-driven development for behavior-changing feature or fix work, and whenever the user mentions TDD, test-first, red-green-refactor, tracer bullets, integration tests, or public-interface behavior tests. Skip for docs-only, path-only rename, formatting-only, or purely mechanical chores unless explicitly requested.

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

Bun runtime, package manager, bundler, and test runner. Use when running scripts with bun, managing packages, serving HTTP with Bun.serve, querying databases with Bun.sql/bun:sqlite/Bun.redis, shell scripting with $, using S3/file I/O, writing tests with bun:test, bundling or compiling to executable, or using any Bun-specific API (spawn, glob, semver, FFI, workers, plugins, HTMLRewriter).

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

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

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

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

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

Use when deploying or managing an app that uses Prisma Composer (`@prisma/composer`): wiring its services and Modules, running it locally, testing composed services, or standing up / tearing down an environment. Triggers on "prisma composer", "@prisma/composer", "prisma app", `prisma deploy`, `prisma dev`, `compute()`, `module()`, `contract()`, `service.load()`, `mockService`, `bootstrapService`.

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

Implement centralized audit logging and SIEM integration. Configure log retention and security monitoring. Use when implementing audit trail requirements.

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

Enables ultra-granular, line-by-line code analysis to build deep architectural context before vulnerability or bug finding.

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

Audit trail register: timestamp, user, module, record, action, field changed, old and new value, and the reason for the change. Use for change history and control evidence.

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

Use when an agent, harness, gateway, MCP workflow, or multi-step automation claims completion and the available traces, checkpoints, approvals, tool calls, or deployment records must be judged without

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

Multi-phase dialectical stress-test for HIGH-STAKES decisions only (architecture choices, irreversible product calls, strategic bets). Heavy-cost skill — do NOT use for routine questions, brainstorming, or simple tradeoffs. User must explicitly invoke or describe a decision they call "high-stakes", "irreversible", or "needs stress-testing". Triggers: "stress test this decision", "dialectic on", "challenge this thesis", "should I really".

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

Create and troubleshoot Ocana agents. Use when creating a new Ocana agent, refreshing/repairing management token auth, diagnosing `ocana_agent_create` failures, checking `gatewayReachable`, handling agents stuck in `provisioning`, debugging `226/NAMESPACE` or missing `/usr/bin/openclaw`, or testing lifecycle/reprovision flows for a newly created agent.

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

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

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

Reads invocation logs from eval_tracker and recommends which of the 50+ skills to prune or consolidate. Run monthly to keep the skill surface tight. Triggers: "audit skills", "prune skills", "which skills do I never use", "skill cleanup".

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

Structured build workflow: branch, delegate to coding agent, test, screenshot, and commit. Triggers on: "$devprocess", "build this properly", "use the coding agent workflow", or any feature/refactor/infrastructure change that is too large for a direct edit. NOT for: one-line fixes, doc edits, prompt tweaks, or simple config changes — do those directly.

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

Use when working with Constructor Io — constructor.io product search and discovery platform management including catalog sync, search configuration, autosuggest, browse, recommendations, quizzes, and A/B testing. Covers catalog health, search performance, conversion tracking, and personalization effectiveness.

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

Use when working with Dagster Deep — dagster deep data orchestration management covering job and asset inventory, run monitoring, schedule and sensor health, partition status, resource configuration, and daemon health checks. Use when investigating run failures, analyzing asset materialization, monitoring schedule ticks, or auditing Dagster configurations.

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