Categories
Indexed Skills (2)
workflow-generator
FIRE when user intent matches any of the following conditions — EXPLICIT TRIGGERS: /workflow-generator; "generate workflow"; "create workflow diagram"; "show workflow" ARCHITECTURAL VISUALIZATION INTENT: user wants to visualize, diagram, draw, map, or generate a system architecture diagram / component diagram / service topology / service map / architecture overview / system overview / data flow diagram / pipeline diagram for the current project or a specified project path. PHRASING VARIANTS THAT SHOULD ROUTE HERE: "how does this system work", "what talks to what", "show me the components", "map the services", "diagram this", "visualize the stack", "show request flow", "show data flow", "trace the pipeline", "architecture of this project", "system map", "service dependencies", "component graph", "what calls what", "show me the architecture", "draw the architecture", "explain the system design", "infrastructure diagram", "dependency graph", "call graph", "module graph", "what imports what", "import graph". CAPA
generate-tech-stack
FIRE this skill when the user's intent is to discover, list, visualize, document, or summarize the technologies used in a software project. This includes all of the following triggers: EXPLICIT COMMANDS: /generate-tech-stack; "generate tech stack"; "create tech stack"; "show tech stack"; "build tech stack"; "make tech stack page"; "tech stack report". DISCOVERY / INVENTORY INTENT: user wants to know what libraries, packages, dependencies, frameworks, tools, or services a project uses — phrased as: "what libraries does this use", "what packages are installed", "what dependencies does this project have", "list all tools", "what frameworks are in use", "show me the dependencies", "what's in requirements.txt", "scan my project", "audit the stack", "inventory the project", "what's this project built with", "what tech does this use", "show all packages", "detect the stack". VISUALIZATION / DOCUMENTATION INTENT: user wants an HTML page, visual report, or summary document of the project's technology choices — phrased
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.