Loading...
Loading...
Found 3,061 Skills
Use when creating or iterating on a detailed per-subsystem technical design specification from a system spec, before starting OpenSpec workflow. Triggers: "design spec", "subsystem spec", "write the spec for S1", "phase breakdown", "implementation phases", "mid-level spec", "technical design". Encodes opinionated progressive phase discipline with FP progression and contract boundaries. Do NOT use for high-level system specs (use brainstorming) or for OpenSpec artifacts (use openspec directly).
Synthesize unstructured thinking into a structured, actionable plan. Use when user provides stream-of-consciousness thoughts, scattered notes, or a brain dump and needs them organized into a coherent plan with goals, actions, and priorities. Trigger phrases: "synthesize", "organize my thoughts", "turn this into a plan", "make sense of this", "structure this", "formalize these notes", "what should I do with all this".
Query Gate Simple Earn (Uni) flexible. Use this skill whenever the user asks about Simple Earn, subscribe or redeem intent, position query, interest query, or top APY. Trigger phrases include "Simple Earn", "Uni", "subscribe", "redeem", "flexible earn", "positions", "interest", "top APY", or any request involving Simple Earn subscribe, redeem, positions, or interest.
Answer questions about OCSF (Open Cybersecurity Schema Framework). Use when the user asks about OCSF classes, objects, attributes, profiles, extensions, or event normalization.
Craft elegant technical specifications with ASCII artistry, flow diagrams, and the Grove voice. The swan glides with purpose—vision first, then form, then perfection. Use when creating specs, reviewing documents, or transforming technical plans into storybook entries.
Guide for Writing and Optimizing AGENTS.md, following the principle of progressive disclosure. This skill must be loaded when users create, modify, or refactor AGENTS.md, discuss AI agent instruction structures, rule placement, or mention terms like "progressive disclosure", "modularity", "AGENTS.md best practices". Even if users simply say "help me write an AGENTS.md", "optimize this configuration file", or "split the rules", this skill should be used.
Template and guide for creating skills. Demonstrates the standard skill structure with resources, docs, examples, and templates directories. Use this as a reference when building new protocol integrations.
Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"
Shared references and cross-cutting rules used by all Infrahub skills. Contains GraphQL query syntax, .infrahub.yml configuration format, and common rules for git integration, display label caching, and Python environment setup. DO NOT TRIGGER directly — loaded automatically by other Infrahub skills when they need shared references.
Gets, checks, and verifies the current UTC date and time for unambiguous temporal reference. Use when starting tasks, verifying temporal context, ensuring date awareness before time-sensitive operations, or when incorrect date assumptions are detected.
Generate Triton operator requirement documents suitable for Ascend NPU. Used when users need to design new Triton operators, write operator requirement documents, or perform operator performance optimization design.
Guides users through documenting business flows step-by-step in EventCatalog. Use when user asks to "document a flow", "map a business process", "create a flow diagram", "walk through a process", "document an end-to-end flow", or "map out how something works in my architecture".