Loading...
Loading...
Found 10,556 Skills
Shared kernel design workflow across all supported languages and DSLs. Provides language selection table, naming conventions, versioning rules, KernelPlan structure, composition patterns, clone workflow, implementation workflow, devlog template, and designer output contract. Use when: (1) choosing which language-specific kernel design skill to load, (2) the intended implementation language is not fixed yet, (3) you need naming or versioning guidance before selecting a DSL, (4) you are implementing any kernel regardless of DSL, (5) you are updating docs that refer to kernel design skills.
Build a production-quality CLI tool for any module or application. Auto-detects language, recommends CLI libraries, and follows a 5-step approval-gated workflow: Analyze, Design, Plan, Execute, Summarize. Don't use for building GUI/TUI apps, web APIs, or authoring one-off shell scripts.
Ultra-lightweight channel for refactor processes - used when changes are obviously too small to justify the full scan → design → apply three-stage workflow. AI directly identifies 1-3 low-risk optimization points, confirms with the user once, modifies in-place using classic methods, and validates itself by running tests. No scan checklist, no design documentation, no multi-step HUMAN verification required. Trigger scenarios: When the user says "quick refactor", "small refactor", "simply optimize XX function", "modify directly", "skip all those steps", and the scope of changes is clearly limited to a single function/single component, with tests available for self-validation.
1CRM integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1CRM data.
Azure AI Vision integration. Manage data, records, and automate workflows. Use when the user wants to interact with Azure AI Vision data.
OnTask integration. Manage data, records, and automate workflows. Use when the user wants to interact with OnTask data.
Document the pitfalls encountered or good practices discovered during this work into searchable learning documents, which can be accessed by both AI and humans when similar tasks arise in the future. Two tracks: The pitfall track records experiences where "things should have worked but didn't" — including bugs, configuration traps, environment issues, and integration failures; The knowledge track records findings that "should be the default approach going forward" — including best practices, workflow improvements, and reusable patterns. Trigger scenarios: Proactively prompt at the end of feature-acceptance or issue-fix workflows, or when the user mentions phrases like "document knowledge", "learning", "document learnings", or "record this experience". Spec documents record what was done, while learning documents record what pitfalls were encountered / what was learned — they complement each other and are not interchangeable.
Phase 1 of the feature workflow — Draft a design document for the new feature, serving as the sole input for subsequent implementation and acceptance. First gather evidence (read architecture docs, review relevant code, grep to prevent term conflicts, check archives), then write a complete first draft in one go (including YAML frontmatter + three-tier structure + test design), submit it to the user for overall review, and iterate until approval. After approval, extract {slug}-checklist.yaml from {slug}-design.md for use in the next two phases. Trigger scenarios: "Start designing the solution", "Write design doc", "Prepare to implement XX", with the prerequisite that you already know what to do, who it's for, and how to define success.
Rapyd integration. Manage data, records, and automate workflows. Use when the user wants to interact with Rapyd data.
Tactiq platform help — Chrome extension AI meeting note-taker with bot-free live transcription for Google Meet, Zoom, and MS Teams. Use when Tactiq transcription accuracy is poor with accents, AI credits running out too fast, setting up Tactiq workflows to push notes to Slack or Notion, connecting Tactiq to HubSpot or Salesforce via Zapier, figuring out which Tactiq plan to pick, or comparing Tactiq to Fathom or Fireflies. Do NOT use for choosing between note-takers generally (use /sales-note-taker) or reviewing a specific call for coaching (use /sales-call-review).
Threat Stack integration. Manage data, records, and automate workflows. Use when the user wants to interact with Threat Stack data.
LeadGenius integration. Manage data, records, and automate workflows. Use when the user wants to interact with LeadGenius data.