experiment-design-kit
Toolkit for structuring hypotheses, variants, guardrails, and measurement plans.
Découvrez les skills tools knowledge base, comparez leurs dépôts et consultez leurs instructions.
Toolkit for structuring hypotheses, variants, guardrails, and measurement plans.
Style and formatting rules for API/SDK documentation, samples, and tutorials.
Use when researching, clustering, and prioritizing keywords for SEO roadmaps.
Use for structured technical SEO audits, incident response, and validation.
Playbook for activating current students, alumni, and partners as advocates.
Best-practice kit for BI dashboard layout, storytelling, and adoption.
Library of reusable solution briefs, architecture, and pricing frames per industry.
Use when planning features and need current API docs, library patterns, or external knowledge; when testing hypotheses about technology choices or claims; when verifying assumptions before design decisions - ga...
Expert in Claude Agent SDK development. Use when users ask about SDK API, agent configuration, MCP servers, hooks, permissions, file checkpointing, or when they mention @AGENT_SDK_DOCS.md. Provides accurate API...
Domain expert routing. When the knowledge base cannot answer user questions, find and notify the corresponding expert based on the question domain. Only available in IM mode. Trigger condition: No results in 6-...
Research standards/patterns via MCP Ref. Generates Standards Research for Story Technical Notes subsection. Reusable worker.
Builds interactive HTML presentation with 6 tabs (Overview, Requirements, Architecture/C4, Tech Spec, Roadmap, Guides). Creates presentation/README.md hub. L2 Worker under ln-100-documents-pipeline.
RICE prioritization per Story with market research. Generates consolidated prioritization table in docs/market/[epic-slug]/prioritization.md. L2 worker called after ln-220.
Research best practices via MCP Ref/Context7/WebSearch and create documentation (guide/manual/ADR/research). Single research, multiple output types.
This skill should be used to validate and auto-fix Stories/Tasks against 2025 standards. Penalty Points system (goal = 0), delegates to ln-002 for documentation, Plan Mode support. Auto-discovers team/config.
Creates task management documentation (docs/tasks/README.md + kanban_board.md). L2 Worker in ln-100-documents-pipeline. Sets up Linear integration and task tracking rules.
Creates reference documentation structure + smart documents (ADRs/Guides/Manuals) based on TECH_STACK. Only creates justified documents (nontrivial technology choices). L2 Worker in ln-100-documents-pipeline.
This skill should be used when the user asks about Railway features, how Railway works, or shares a docs.railway.com URL. Fetches up-to-date Railway docs to answer accurately.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or to...
Load automatically when user asks to learn Medusa development (e.g., "teach me how to build with medusa", "guide me through medusa", "I want to learn medusa"). Interactive guided tutorial where Claude acts as a...
This skill should be used when the user asks to "research a topic", "deep research", "investigate thoroughly", "multi-source research", "comprehensive analysis", or needs to conduct research across web, documen...
This skill should be used when the user asks to "add warning", "remove warning", "list warnings", "check file warning", "check package warning", "manage grudges", or needs to manage file and package warnings in...
Interactive skill for creating new Bases Views. Guides through adaptive questioning, then generates all necessary files.
Use this skill when the user asks to save, remember, recall, or organize memories. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check your notes', 'clean up memories'...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.