Loading...
Loading...
Found 9,710 Skills
Hot-reload Go apps with cosmtrek/air during development. Use when setting up dev workflows for Go HTTP servers, configuring .air.toml, or debugging hot-reload issues with SQLite, port binding, or file watchers.
Comprehensive map for multi-brain, orchestration, and agent governance. Triggers when users ask to 'view the orchestration ecosystem', 'how do agents work together?', 'multi-brain workflows', or 'give agents access'.
Finerio Connect integration. Manage data, records, and automate workflows. Use when the user wants to interact with Finerio Connect data.
Issue Workflow Stage 3——Fix code precisely based on confirmed root cause and solution, verify the effect, and document it in {slug}-fix-note.md. This is the final stage of the issue workflow—no verification loop means the workflow is incomplete. Two entry points: the standard path is triggered from easysdd-issue-analyze (with existing {slug}-analysis.md), and the quick path is triggered directly from easysdd-issue-report (without {slug}-analysis.md, as the root cause was determined by AI reading code during the report stage). Trigger scenarios: user says 'Start fixing the bug', 'Fix according to analysis', 'Start modifying code'. During repair, only modify the files stated in the solution; do not optimize casually or introduce new abstractions—these actions will make the scope spread to untraceable levels.
Onboard a new repository or a repository with scattered documents into the easysdd system. Two paths are automatically determined: the empty repository path (no spec-like documents or easysdd/ directory in the repository) builds the skeleton from scratch; the migration path (the repository already has scattered documents or partial easysdd/ structure) first generates an audit report + migration mapping plan, which is confirmed by the user one by one before implementation. This skill only does two things: "build the skeleton" and "organize existing documents". After the skeleton is built, all sub-workflows can run directly. Trigger scenarios: the user says "Use easysdd in this project", "Build easysdd structure", "Initialize easysdd", "Migrate to easysdd".
Cisco Meraki integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cisco Meraki data.
Phase 3 of the issue workflow —— Fix code precisely according to confirmed root causes and solutions, verify the results, and document it in {slug}-fix-note.md. This is the final stage of the issue workflow —— no verification closure means the workflow is incomplete. Two entry points: the standard path is triggered from cs-issue-analyze (with existing {slug}-analysis.md), and the fast track is triggered directly from cs-issue-report (without {slug}-analysis.md, as the root cause was identified by AI through code reading during the report phase). Trigger scenarios: User says "Start fixing the bug", "Fix according to the analysis", "Start modifying the code". During the fix, only modify the files specified in the solution; do not make incidental optimizations or introduce new abstractions —— these actions will cause the scope to expand to an untraceable extent.
Background knowledge for droid-control workflows -- not invoked directly. Deliverable verification against commitments.
AdRoll integration. Manage data, records, and automate workflows. Use when the user wants to interact with AdRoll data.
Hotmart integration. Manage data, records, and automate workflows. Use when the user wants to interact with Hotmart data.
Guide for operating the bitdrift bd CLI and analyzing live bitdrift account data — workflows, charts, sessions, issues, keys, connectors, and app health investigations. Trigger when the user wants to run bd commands, inspect live platform data, debug an app with bitdrift, create or edit workflows, read charts or metrics, triage crashes, inspect session timelines, or automate bitdrift operations from the CLI.
Interview-driven automation design tool. This skill should be used when the user wants to design a new skill, agent, automation, shortcut, or any other automatable workflow. Runs a coverage-driven JTBD interview (text or voice), then exports a one-page markdown spec plus an SVG design map.