Loading...
Loading...
Found 1,474 Skills
Gathers inputs, defines initiatives, prioritises with an impact/effort matrix, sequences dependencies, and produces a roadmap table. Invoked when the user asks to plan a technical roadmap, prioritise engineering initiatives, or create a quarter/half-year engineering plan.
Create, visualize, and analyze lithological and stratigraphic logs for well data. Use when Claude needs to: (1) Create lithology columns from depth intervals, (2) Parse geological descriptions into structured logs, (3) Visualize stratigraphic columns with patterns and colors, (4) Perform well-to-well correlations, (5) Extract statistics like net-to-gross ratios, (6) Define rock type lexicons and legends, (7) Export lithology data to CSV/LAS/JSON.
Build and operate multi-agent workflows with OpenAI Agents SDK (Python): define agents/tools/handoffs, add guardrails, run conversations, and debug orchestration behavior. Use when users ask for agent orchestration with OpenAI-native patterns, handoff routing, or production-ready agent loops.
Use when writing DALI data loading or preprocessing code with `nvidia.dali.experimental.dynamic` (ndd), or when converting DALI pipeline-mode code to dynamic mode, or when the user asks about DALI dynamic mode, imperative DALI, or ndd. Use this skill any time someone mentions 'ndd', 'dynamic mode', or wants to load/augment data with DALI outside of a pipeline definition.
Mandatory only on the task-file path of `spec-loop-plan-task` after implementation approval. Use when implementation deviates from the approved task, when uncertainty must be clarified instead of guessed through, when new blocking questions arise, or before presenting the current task or subtask to the User. Governs clarification routing, canonical task updates when explicit User clarification, accepted review feedback, or explicit post-implementation User approval changes the current task definition, the post-implementation `Implementation notes` check, and whether the increment may move to `review`. May be applied in parallel with other implementation-related skills.
Generate tone-of-voice and brand-system files for use with the PPTX Generator and other brand-aware skills. TRIGGERS - Use this skill when user says: - "help me create a brand system" / "set up my brand" - "generate my tone of voice" / "create my voice guidelines" - "configure my brand for presentations" / "set up brand for slides" - "create brand files" / "initialize my brand" - Any request about defining brand identity, voice, or visual system for content creation Creates brand.json, config.json, brand-system.md, and tone-of-voice.md files.
Query Catalog, database, and table metadata resources in Alibaba Cloud Data Lake Formation (DLF). Provides read-only queries via the DLF OpenAPI Python SDK, supporting listing and viewing Catalogs, databases, tables with their detailed information and Schema definitions. Use cases: "list available Catalogs", "list databases", "view table schema", "search tables", "search tables by name", "fuzzy search", "view DLF metadata", "what databases are in the data lake", "what columns does a table have", "find tables whose name contains xxx". This Skill only contains read-only operations — no create, modify, or delete operations.
Design HTTP APIs for Bun + Hono backends using Clean Architecture, Zod contracts in a shared package, OpenAPI generation from Zod, and thin controllers. Supports two selectable conventions — standard REST (resource paths with GET/POST/PATCH/PUT/DELETE) and POST-only action-based paths — picking one per project. Use when defining new endpoints, auditing or refactoring existing routes, shaping request/response contracts and envelopes, establishing API standards, or mapping typed application errors to HTTP status codes. Do not use for GraphQL, tRPC, non-Hono runtimes, or frontend-only concerns.
QLC+ (Q Light Controller Plus) lighting software — workspace files (.qxw), scenes, chasers, sequences, collections, EFX, RGB matrices, fixture definitions (.qxf), Virtual Console, and timing calculations. Use this skill whenever the user is working with QLC+ workspace XML, creating/editing scenes/chasers/shows, debugging timing or crossfade issues, generating fixture definitions, setting up Virtual Console widgets (cue lists, solo frames, buttons, sliders), troubleshooting HTP/LTP conflicts, fixing corrupted .qxw files, configuring QLC+ plugins (DMX USB, Art-Net, MIDI, E1.31), or asking any question where QLC+ is the software being used. Also trigger for SpeedModes, FadeIn/Hold/Duration, FixtureVal, RunOrder, or QLC+ function types. Do NOT trigger for general DMX hardware questions without QLC+ context, fixture buying advice, DAW-only questions, or custom protocol implementations.
Estrategista de produto no SynkOS. Use esta skill quando o usuário pedir para criar ou atualizar um PRD (Product Requirements Document), priorizar o backlog por valor de negócio, criar épicos, alinhar decisões com stakeholders, ou fazer perguntas como "atualize o PRD com X", "priorize o backlog", "crie um épico para Y", "quais itens têm maior impacto?", "como comunicar esse tradeoff ao cliente?", "o backlog está alinhado com os objetivos de produto?". Ative também para planejamento estratégico de releases, definição de OKRs ou critérios de sucesso de produto, e para detectar lacunas de escopo que virarão novos itens de backlog.
Gerente do ciclo de vida de stories e orquestrador de handoffs no SynkOS. Use esta skill quando o usuário pedir para decompor um épico em stories, criar stories com critérios de aceite, fazer backlog grooming, planejar sprint, orquestrar handoffs entre roles (architect → dev → qa), ou fazer perguntas como "quebre esse épico em stories", "crie a story para X", "o backlog está priorizado?", "faça o checkpoint da story Y", "orquestre o handoff para QA". Ative também para resolver dependências entre stories, escalar stories bloqueadas, e garantir que cada story tem ownerRole e reviewRole definidos antes de entrar em implementação.
Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories — run /create-stories [epic-slug] after each epic is created.