Loading...
Loading...
Found 378 Skills
Autonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, self-improve skill, benchmark skill, eval my skill, run evals on. Outputs: an improved SKILL.md, a results log, and a changelog of every mutation tried.
Verify a research claim or academic citation by tracing it through publication → methodology → raw data → independent replication. Routes through perplexity-research for the actual web lookup, then formats results as a citation-checked brain page. Use when a book/article/conversation cites a study and you want to confirm the claim is real, replicated, and accurately characterized.
Write, structure, or review a PhD/Master's research proposal. Use when drafting a research proposal, preparing for committee review, writing a thesis outline, or aligning methodology with academic requirements.
Use this skill when planning a content strategy or deciding what content to create. Trigger phrases include: "build a content strategy," "plan our content," "create a content calendar," "what content should we create," "map our content to the funnel," "build topic clusters," "define our content pillars," "plan our editorial calendar," "how do we distribute content," "measure content ROI," or "what content drives leads." This skill covers topic cluster methodology, content pillars, keyword-to-content mapping, editorial calendar building, content formats by funnel stage, distribution strategy, and measuring content ROI. Distinct from writing individual content pieces.
Assesses how ready a business is for AI adoption across six dimensions. Evaluates data maturity, tech stack, team skills, process documentation, budget, and culture. Generates a comprehensive ai-readiness-report.md with scores, gap analysis, and recommended starting points. Aligned with OneWave AI's audit methodology.
Collaborative domain modeling through pictographic stories. Use when gathering requirements, understanding business workflows, onboarding team members, or preparing for event storming. Follows Stefan Hofer & Henning Schwentner's methodology with actors, work objects, and activities.
Kanban methodology including boards, WIP limits, flow metrics, and continuous delivery. Activate for Kanban boards, workflow visualization, and lean project management.
Zero Script QA - Testing methodology without test scripts. Uses structured JSON logging and real-time Docker monitoring for verification. Use proactively when user needs to verify features through log analysis instead of test scripts. Triggers: zero script qa, log-based testing, docker logs, 제로 스크립트 QA, ゼロスクリプトQA, 零脚本QA, QA sin scripts, pruebas basadas en logs, registros de docker, QA sans script, tests basés sur les logs, journaux docker, skriptloses QA, log-basiertes Testen, Docker-Logs, QA senza script, test basati sui log, log docker Do NOT use for: unit testing, static analysis, or projects without Docker setup.
Research and use customer language across Product and Marketing. Sales Safari methodology for finding watering holes, extracting pain language, and creating "OH YEAH!" resonance.
Use when integrating Atomic Design methodology with React, Vue, Angular, or other frameworks. Framework-specific implementation patterns.
Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with multi-agent evaluation
Provides startup advice using Eric Ries' Lean Startup methodology focusing on Build-Measure-Learn cycles, validated learning, and rapid experimentation. Use when advising on MVPs, product iterations, pivot decisions, growth metrics, or when user mentions Lean Startup, Eric Ries, validated learning, or rapid experimentation.