테스트·보안 스킬

Systematically validate your business hypotheses before building anything. Master Steve Blank's Customer Development methodology that became the foundation of Lean Startup and YC's approach. Use when: **Starting a new venture** to avoid building something nobody wants; **Before writing a line of code** to validate problem-solution fit; **Pivoting decisions** to systematically test new directions; **Early-stage fundraising** to prove market validation; **Product roadmap planning** to prioritiz...

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

Run automated Lighthouse audits for Core Web Vitals and SEO. Use when: checking page performance; auditing SEO technical issues; monitoring Core Web Vitals; comparing before/after optimization; batch auditing multiple URLs

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

Use when analyzing server logs to understand how AI crawlers (GPTBot, ClaudeBot, PerplexityBot) interact with your site. Use when optimizing content placement for LLM retrieval, diagnosing why AI search isn't citing your content, or auditing crawl patterns to find optimization gaps.

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

Process large codebases (>100 files) using the Recursive Language Model pattern. Orchestrates parallel sub-agents to map-reduce across files without context rot. Use when: analyzing large repositories; auditing security or auth across many files; finding patterns across 50+ files; processing large log files or data dumps

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

Use when testing skills, commands, or agents for quality. Use after creating new skills, before deploying agents, or when debugging inconsistent agent behavior. Triggers on "evaluate", "test quality", "is this skill working", or QA of AI workflows.

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

Optimize landing pages for maximum conversions using proven frameworks from Unbounce and Oli Gardner—apply the "one goal, one message, one action" principle with data-driven design, copy, and CTA best practices. Use when: **Create a new landing page** for a campaign; **Optimize an existing landing page** that isn't converting; **Review landing page design** before launch; **Improve form conversion rates** on lead gen pages; **A/B test landing page elements** systematically

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

25+ proven headline formulas that stop the scroll, capture attention, and drive clicks. Templates and examples for every situation. Use when: Writing headlines for landing pages, ads, or articles; Creating email subject lines that get opens; Crafting social media hooks; A/B testing headline variations; Overcoming headline writer's block

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

Master the art of calls-to-action that convert. Direct CTAs, transitional CTAs, button copy, and microcopy that turns readers into customers. Use when: Writing button text for landing pages and emails; Creating CTAs for different stages of awareness; Designing click-worthy microcopy; A/B testing CTA variations; Building email sequences with graduated CTAs

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

Master Gary Halbert's direct response copywriting principles from "The Boron Letters" (1984). The timeless fundamentals that separate pros from amateurs. Use when: Writing direct response copy (sales letters, emails, ads); Creating headlines that demand attention; Building mailing lists and segmentation; Improving copy through the A-pile test; Learning copywriting fundamentals from scratch

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

Calculate A/B test statistical significance. Use when: determining if test results are significant; calculating required sample size; estimating test duration; analyzing conversion experiments; making data-driven decisions

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

Run an opt-in deep codebase audit with persisted findings. Confirm cost before dispatch; filing and telemetry need separate approval.

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

Verify the active host install, package, command ownership, enforcement, wrapper self-test, and active-dispatch coverage gap. Read-only.

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

The secret-source gate. Routed to when changed code reads, writes, or passes a secret — API key, token, password, connection string, signing key, certificate, or any value that grants access. Validates that every secret comes from the approved store and never lands in source, log, test fixture, error response, image, or LLM prompt. The auth-crypto-reviewer agent is dispatched as the reviewer.

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

The banned-primitive gate. Routed to when changed code hashes, signs, encrypts, derives keys, generates security-relevant randomness, configures TLS, or imports a crypto library. Rejects broken primitives, disabled TLS verification, and home-rolled crypto; the approved-primitive list lives in security-controls.md. The auth-crypto-reviewer agent is dispatched as the reviewer.

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

Run an opt-in deep codebase audit with persisted findings. Confirm cost before dispatch; filing and telemetry need separate approval.

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

Sanctioned, logged bypass of a gate or hard rule — one audit line, then proceed.

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

Threat-model a sensitive design with STRIDE on request. Read-only analysis of threats, controls, and implementation constraints.

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

Fix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.

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

Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only.

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

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

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

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

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

Use when a researcher, maintainer, or contributor found or suspects a malicious skill on ClawHub and needs a private reporting workflow: opening a GitHub private vulnerability report, preparing a proposal-only PR, creating `proposals/<GHSA-ID>/clawscan.yml`, running ClawScan against the malicious skill, and explaining what evidence belongs in private versus public channels.

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

Use when an OpenClaw maintainer or owner is reviewing a ClawHub malicious-skill profile proposal PR: checking `proposals/<GHSA-ID>/clawscan.yml`, reading the private vulnerability context without leaking it, running the SkillTrustBench Profile Gate or equivalent local benchmark, updating the accepted baseline, and promoting an accepted candidate into `internal/profiles/clawhub/clawscan.yml`.

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

Odoo 18 development reference for Python models and ORM (search, domain, read_group, compute fields), XML/CSV data and views, OWL/JS client code, QWeb reports, security (ACL, record rules, groups), cron and server actions, migrations and module upgrades, tests, i18n, and performance. Use this skill whenever work involves Odoo 18 or custom addons—even if the user only pastes a traceback, mentions addons/ or __manifest__.py, describes form/list/kanban/XML errors, HTTP controllers, or business rules on models—including building features, fixing bugs, refactoring, or reviewing addon code. Includes CSS/SCSS asset authoring and review for Odoo addons.

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