Loading...
Loading...
Found 7,438 Skills
Use this when you are exploring the codebase. It lets you ask the AI who wrote code questions about how things work and why they chose to build things the way they did. Think of it as asking the engineer who wrote the code for help understanding it.
Stripe integration. Manage Customers, Products, Payouts, Transfers. Use when the user wants to interact with Stripe data.
Manage tasks using the fine CLI. Use this skill whenever the user asks to create, view, update, or work with tasks, project requirements, feature specs, or work tracking through markdown files. Also use it when the user mentions "fine" in the context of project management, or asks about task status, step progress, or wants to break work into tracked steps.
Use when the user asks to create a pull request. Build a complete PR using best-practice structure with rich details on changes, verification, QA evidence, risks, and rollout notes. Include issue linkage and clear testing commands/results in the PR body.
Service Now integration. Manage Incidents, Problems, Tasks, Users, Groups. Use when the user wants to interact with Service Now data.
Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs
Use when starting any implementation task, feature request, bug fix, or refactoring work. Triggers on /plan command, before any code is written, when requirements need structured analysis, or when transitioning from brainstorming to implementation. Forces question-asking, approach comparison, and explicit approval before any code.
This skill should be used when the user has a written implementation plan to execute in a separate session with review checkpoints.
Inspect, triage, approve, and merge GitHub Renovate pull requests with gh. When no repository is provided, use the default preset repository set, build a candidate execution plan, and execute only after explicit user confirmation. Use when the user asks to check, batch-handle, approve, or merge Renovate PRs.
2-layer parallel agent hierarchy. Layer 1 deploys 3-50+ agents, each with independent context. Layer 2 adds 2+ sub-agents per member. No upper limit on either layer.