Loading...
Loading...
Found 3,180 Skills
Converts DOCX/PDF/PPTX to high-quality Markdown with automatic post-processing. Fixes pandoc grid tables, simple tables, image paths, CJK bold spacing, attribute noise, and code blocks. Benchmarked best-in-class (7.6/10) against Docling, MarkItDown, Pandoc raw, and Mammoth. Trigger on "convert document", "docx to markdown", "parse word", "doc to markdown", "解析word", "转换文档".
Capture a forward-looking idea as a seed with trigger conditions, scope, and rationale so it surfaces automatically during future feature design. Use for "plant seed", "save this idea for later", "defer this idea", "remember this for when", "seed", or "/plant-seed". Do NOT use for TODOs, immediate tasks, bug reports, or work that should happen in the current session.
Run comprehensive 3-wave review against all source files in the repo, producing a prioritized issue backlog. Use for "full repo review", "review entire repo", "codebase health check", "review all files", "full codebase review". Do NOT use for PR-scoped reviews (use comprehensive-review) or single-concern reviews (use individual agents).
Phase-gated git commit workflow with validation, staging, and CLAUDE.md compliance enforcement. Use when creating commits, staging changes, or when PR workflows need standardized commits. Triggers: "commit changes", "save work", "create commit", or internal skill invocation from PR workflows. Do NOT use for merge commits, rebases, amends, cherry-picks, or emergency rollbacks requiring raw git speed.
Validate-then-fix workflow for PR review comments: Fetch, Validate, Plan, Fix, Commit. Use when user wants to address PR feedback, fix review comments, or resolve reviewer requests. Use for "fix PR comments", "address review", "pr-fix", or "resolve feedback". Do NOT use for creating PRs, reviewing code without fixing, or general debugging unrelated to PR comments.
Safe bulk editing across multiple Hugo markdown posts: find/replace, frontmatter updates, content transforms with mandatory preview before apply. Use when user needs batch text replacement, bulk frontmatter field changes, heading/link/whitespace normalization, or regex-based content transforms across posts. Use for "batch edit", "find and replace across files", "add field to all posts", "bulk update tags". Do NOT use for single-file edits, structural refactoring, or content generation.
Validate Perses resources: run percli lint locally or with --online against a server. Check dashboard definitions, datasource configs, variable schemas. Report errors with actionable fixes. Use for "perses lint", "validate perses", "check dashboard", "perses validate". Do NOT use for plugin schema testing (use perses-plugin-test).
RED-GREEN-REFACTOR testing for agents: dispatch subagents with known inputs, capture verbatim outputs, verify against expectations. Use when creating, modifying, or validating agents and skills. Use for "test agent", "validate agent", "verify agent works", or pre-deployment checks. Do NOT use for feature requests, simple prompt edits without behavioral impact, or agents with no structured output to verify.
Manage editorial content pipeline through 6 stages: Ideas, Outlined, Drafted, Editing, Ready, Published. Use when user wants to view pipeline status, add ideas, move content between stages, schedule posts, or archive published content. Use for "content calendar", "pipeline status", "add idea", "schedule post", or "move to drafted". Do NOT use for creating Hugo content files, deploying posts, or modifying site configuration.
Quick status check for current branch and PR state showing local changes, CI results, reviews, and merge readiness. Use when user wants branch status, PR state, CI check results, review status, or merge readiness. Use for "pr status", "what's the status", "is my PR ready", "check CI". Do NOT use for creating PRs, pushing changes, or fixing review comments.
Pre-publication validation for Hugo posts: front matter, SEO, links, images, draft status, and taxonomy. Use when user wants to check a post before publishing, validate blog content, or run pre-publish checks. Use for "pre-publish", "check post", "ready to publish", "validate post", or "publication check". Do NOT use for content writing, editing prose, or generating new posts.
Audit and maintain blog taxonomy (categories/tags) for consistency, SEO, and navigation: scan content, detect orphans and duplicates, merge and rename terms, verify builds. Use when user asks to "audit tags", "fix taxonomy", "consolidate categories", "merge tags", or "clean up taxonomy". Do NOT use for writing new content, individual post SEO optimization, or major content restructuring.