Loading...
Loading...
Found 3,215 Skills
Identify and fix common testing mistakes across unit, integration, and E2E test suites. Use when tests are flaky, brittle, over-mocked, order-dependent, slow, poorly named, or providing false confidence. Use for "test smell", "fragile test", "flaky test", "over-mocking", "test anti-pattern", or "skipped tests". Do NOT use for writing new tests from scratch (use test-driven-development), refactoring architecture (use systematic-refactoring), or performance profiling without a specific test quality symptom.
Run Go quality checks via make check with intelligent error categorization and actionable fix suggestions. Use when user requests "run quality checks", "check PR quality", "verify code quality", or "run make check". Use before creating commits or during PR review. Do NOT use for non-Go repositories, repositories without a Makefile, or manual linter invocation.
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.
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.
Transform dense technical communication into clear, structured business formats using proposition extraction and deterministic templates. Use when user needs to convert technical updates, debugging narratives, status reports, or dependency discussions into executive-ready summaries. Use for "transform this update", "make this executive-ready", "summarize for my manager", "professional format", or "status report". Do NOT use for writing new content from scratch, creative writing, or generating documentation that doesn't transform an existing input.
Perses plugin scaffolding and creation: select plugin type (Panel, Datasource, Query, Variable, Explore), generate with percli plugin generate, implement CUE schema and React component, test with percli plugin start, build archive with percli plugin build. Use for "create perses plugin", "new panel plugin", "new datasource plugin", "perses plugin scaffold". Do NOT use for dashboard creation (use perses-dashboard-create).
Fetch PR feedback from all GitHub sources and validate every comment before acting. Use when user needs to process PR review comments, address reviewer feedback, or triage pull request discussions. Use for "review comments", "PR feedback", "address reviews", "address feedback", or "what did reviewers say". Do NOT use for creating new PRs, code review of local changes, or general code analysis without an existing PR.
Use this skill to prevent destructive operations when working on production systems or running agents autonomously.
Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
Configure multiple Obsidian environments for development, testing, and production. Use when managing separate vaults, testing plugin versions, or establishing a proper development workflow with isolated environments. Trigger with phrases like "obsidian environments", "obsidian dev vault", "obsidian testing setup", "multiple obsidian vaults".
Convene a four-voice council for ambiguous decisions, tradeoffs, and go/no-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.
Manage Feishu document permissions (权限管理) — add/remove collaborators, set public sharing, check access levels. Use when the user mentions sharing (分享/共享), permissions (权限), collaborators (协作者), access control (访问控制), visibility (公开/私有), link sharing (链接分享), or wants to manage who can view/edit a document. Also trigger when user says "把文档分享给XX"、"谁能看这个文档"、"设成公开". DO NOT TRIGGER for creating or editing document content — use feishu-doc for that.