Loading...
Loading...
Found 10,112 Skills
Create, modify, and maintain Taskfiles following Task (https://taskfile.dev) best practices. Use when: (1) Creating new tasks or Taskfiles, (2) Modifying existing task definitions, (3) Adding new task includes, (4) Debugging task execution issues, (5) Questions about Taskfile syntax or patterns, (6) Running or understanding "task" commands, (7) Questions about available tasks or task namespaces. Triggers: "taskfile", "Taskfile.yaml", "task command", "task:", "create task", "add task", "task --list", "task tg:", "task inv:", "task wt:", ".taskfiles/", "how to run", "available tasks", "task syntax", "taskfile.dev" This skill covers the repository's specific conventions in .taskfiles/ and the root Taskfile.yaml.
Hand off to a fresh Claude session. Use when context is full, you've finished a logical chunk of work, or need a fresh perspective. Work continues from hook.
This skill should be used when the user asks to "create note", "capture thought", "save this", "document idea", "write note", "jot down", "quick note", "remember this", "capture this", or mentions wanting to save knowledge, ideas, or learnings for later reference in their secondbrain.
This skill enriches vague prompts with targeted research and clarification before execution. Should be used when a prompt is determined to be vague and requires systematic research, question generation, and execution guidance.
Create comprehensive GitHub pull requests with quality validation
Generates new content drafts based on reference content analysis
Run an internal dogfooding program/sprint and produce a Dogfooding Pack (charter, scenario map, routines, dogfooding log + triage board spec, weekly report, ship/no-ship gate). Use for “dogfooding”, “eat our own dog food”, internal beta, and product teams using the product daily to find friction before shipping.
Stage all changes, create commit, and push to remote. Use when asked to "push everything", "commit and push all", "push all my changes", or for bulk operations. Includes safety checks for secrets, API keys, and large files. Requires explicit user confirmation before executing. Use with caution.
Tracks competitor page changes over time. Captures snapshots, detects diffs, alerts on significant changes. Supports Tavily site discovery for URL enumeration. Use when monitoring competitive intelligence, pricing changes, or feature tracking.
Guides creation of effective Agent Skills with proper structure and validation. Use when users want to create a new skill, update an existing skill, or need guidance on skill design patterns, SKILL.md format, or verify.py implementation. NOT when just using existing skills (use those skills directly).
Create Technical Specifications (SPEC) - Layer 10 artifact using YAML format for implementation-ready specifications
Use when syncing all git repos under ~/code across machines, typically at end-of-day (push) or start-of-day (pull). Triggers on「同步代码」「code-sync」「下班同步」「上班更新」.