Loading...
Loading...
Found 113 Skills
Execute approved implementation plans phase by phase with automated and manual verification. Use when the user explicitly says "implement the plan", "execute the plan", or "start implementing" and has a plan file ready. Do not use for ad-hoc coding tasks without a plan.
Route spec content into the correct delta spec file. Reads .spec-driven/specs/INDEX.md first, then decides whether to update an existing spec file, create a new spec file, create a new category, modify requirements, or remove specific requirements.
Add research-powered enrichment columns to Extruct company tables. Use when the user wants to add enrichment columns (e.g. funding, verticals, tech stack) to an existing Extruct table, run column configs from enrichment-design, or monitor enrichment progress. Triggers on: "enrich", "add column", "add data point", "research column", "enrich table", "enrichment", "add a field", "run enrichment", "monitor enrichment".
Edit an existing PRD. Use when the user says "edit this PRD".
Auto-detect project tech stack and configure language-specific references
MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. Routes to type-specific guidance (generic flowchart, architecture flowchart) and tells you when to proceed directly, when to use a different diagram type, or when the tool isn't the right fit at all.
Use this skill when the user asks to create, scaffold, update, or review a MoviePilot agent skill. This includes adding a new built-in skill under the repository `skills/` directory, editing an existing built-in skill, writing `SKILL.md` frontmatter and workflow instructions, choosing `allowed-tools`, adding helper scripts when needed, and bumping the built-in skill `version` so changes can sync into `config/agent/skills`.
Draft and submit one high-signal idea when probe next routes propose, using directive plus ZENON Red org and phase context.
Create/refresh lean repo memory docs and root AGENTS.md guidance for handoffs, stale status, next steps, or post-work capture.
End-to-end guidance for protein design pipelines. Use this skill when: (1) Starting a new protein design project, (2) Need step-by-step workflow guidance, (3) Understanding the full design pipeline, (4) Planning compute resources and timelines, (5) Integrating multiple design tools. For tool selection, use binder-design. For QC thresholds, use protein-qc.
Intelligent skill suggestion engine that analyzes user intent and project context to recommend appropriate documentation skills
Interactive conversational guidance - user implements with step-by-step advice. Use when you want hands-on implementation with expert guidance while maintaining control.