Loading...
Loading...
Found 1,550 Skills
Audit installed skills across project, global, and plugin levels. Lists skills with line counts, identifies improvement opportunities (conciseness, clarity, overlap, token waste). Use when reviewing skill quality, finding bloated skills, or optimizing token budgets.
TDD applied to documentation - create production-ready skills. Use when authoring new skills. Includes writing style guidelines for clear prose.
Create effective AI skills. This skill should be used when user wants to create a new skill (or update an existing skill) that extends an AI with specialized capabilities, knowledge, workflows, or tool integrations.
Convert documentation websites, GitHub repositories, and PDFs into Claude AI skills. Use when creating Claude skills from docs, scraping documentation, packaging websites into skills, or converting repos/PDFs to Claude knowledge.
Use when planning, scaffolding, validating, or packaging Claude skills inside Advanced Memory MCP.
Coach product managers with evidence-based feedback, growth plans, and operating cadence.
Create AI evaluation plans with benchmarks, rubrics, and error analysis workflows.
Capture and persist lessons learned from a session to compound knowledge over time. Triggers on "/lessons-learned", "what did we learn", "save lessons", "update skills with what we learned", or at the end of a complex multi-session task. PROACTIVE USE: This skill should also be suggested or invoked (1) when resuming from context compaction (the previous context likely contained unrecorded lessons), (2) after resolving a non-trivial bug or debugging session, (3) after significant friction or failed approaches that yielded insight, (4) after a council-of-bots review that surfaced fixes. Identifies reusable patterns, bug fixes, workflow insights, and tool quirks, then persists them to the right places: auto-memory (project-specific), skill files (reusable across projects), or both.
Create, review, and iterate on Claude Code skills using Anthropic's official best practices and latest API documentation. Use when creating skills, reviewing existing skills, writing skill descriptions, designing skill architecture, or when user says "create a skill", "review my skill", "skill best practices", "skill description help". Do NOT use for creating plugins, commands, agents, or hooks - use plugin-dev skills for those.
Replace with a description of what this skill does and when Claude should use it. Include keywords that help agents discover and activate this skill.
A guide for creating effective Skills. It is used when users want to create new Skills (or update existing Skills) to extend Claude's capabilities, including professional knowledge, workflows or tool integration.
Deep test, analyze, and audit Claude skills. Use this skill whenever the user wants to test a skill's behavior, analyze how it uses the Claude API, inspect inputs/outputs from scripts, or run security and code review audits against skill scripts. Trigger on: "test my skill", "analyze this skill", "audit skill scripts", "review skill for security issues", "what does this skill actually do when it runs", "inspect API calls from skill", "run a skill through its paces", "check my skill for bugs or vulnerabilities". Also trigger when the user shows you a SKILL.md and asks you to evaluate, critique, or stress-test it.