Loading...
Loading...
Found 8 Skills
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
Use when building, editing, validating, testing, or debugging an n8n workflow through the n8n-mcp MCP server — designing a flow, configuring a node, writing an expression or Code node, wiring credentials, or fixing one that misbehaves. The entry-point skill for the n8n-mcp-skills pack: it routes you to the right specialist skill, gives working knowledge of every n8n-mcp tool from turn one, and states the rules that keep workflows from breaking in production. Always consult it first on any n8n, workflow, node, or automation task — even a quick one-off, and even when the user names no skill — because n8n's surface drifts between versions and the specialist skills prevent silent failures.
Compatibility router for the shared optimization knowledge base and the language-specific optimization catalog skills. Use when: (1) selecting which optimization catalog skill to load, (2) the implementation language is not fixed yet, (3) a workflow still references the legacy optimization-catalog skill name, (4) deciding whether a finding is shared or language-specific, (5) updating the generalized knowledge-base structure.
ListenHub CLI skills router. Routes to the correct skill based on user intent. Triggers on: "make a podcast", "explainer video", "read aloud", "TTS", "generate image", "做播客", "解说视频", "朗读", "生成图片", "幻灯片", "slides", "音乐", "music", "generate music", "翻唱", "cover song", "parse URL", "解析链接", "提取内容".
Like and unlike posts on X through Shift's Skill Router.
Use this skill first for ANY PixiJS v8 task; it routes to the right specialized skill for the job. Covers the full PixiJS surface: Application setup, the scene graph (Container, Sprite, Graphics, Text, Mesh, ParticleContainer, DOMContainer, GifSprite), rendering (WebGL/WebGPU/Canvas, render loop, custom shaders, filters, blend modes), assets, events, color, math, ticker, accessibility, performance, environments, migration from v7, and project scaffolding. Triggers on: pixi, pixi.js, pixijs, PixiJS, v8, Application, app.init, Sprite, Container, Graphics, Text, Mesh, ParticleContainer, DOMContainer, GifSprite, Assets, Ticker, renderer, WebGL, WebGPU, scene graph, filter, shader, blend mode, texture, BitmapText, create-pixi, how do I draw, how do I render, how do I animate in pixi.
Internal conversation-entry router for Claude Code. Performs a lightweight intake pass at the start of substantive work: decide whether a more specific skill should be invoked first, whether specialized agent delegation is warranted, how much context is actually needed, and whether the task needs planning or can proceed directly. Not a user-facing slash command.
The single entry point into the daily-work arc — a hybrid menu/argument router. Trigger whenever the user invokes /dev-workflows:daily, types /daily, asks "what should I do now", "where was I", "start my day", "what's next today", "wrap up my day", "end my day", or seems unsure which skill fits their current daily-work moment. Bare invocation shows a 5-station menu (starting / working / filing findings / reporting / wrapping up); with an argument (start | work | file | report | wrap, synonyms accepted) it jumps straight to the station and hands off to the right skill: ado-backlog:my-work, the situational toolbox (grill-then-plan, debug-mantra, study-design-verify, naming-audit, fit-gap-analysis, problem-description, ticket-trace, scrutinize, review-pr, dual-verifier, drive-to-legacy, crm-archaeology, generating-test-cases), findings-to-ado-backlog or ado-create-work-items (github-backlog twins on request), management-talk, or invoice-generator.