Loading...
Loading...
Found 11,732 Skills
Ask and record decisions item by item regarding substantive unresolved user trade-offs in planning, product specifications, design, technical solutions, implementation, or release. Applicable to scope, priorities, trade-offs, risks, acceptance, dependencies, visual direction, or release authorization that cannot be closed from code, configurations, authoritative artifacts, or deterministic execution; it is not automatically triggered by new phases or new modules.
Audio design role for Phaser 4 mobile 2D games. Responsible for planning, generating, reviewing, compressing, authorizing, or integrating music, sound effects, voice, mixing, and mobile audio interactions.
Remind the user to rebuild OMC after editing TypeScript when running from a local fork. Triggered automatically by the AI whenever it notices it (or the user) just changed a src/**/*.ts file in an OMC dev install.
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Generate ONE reviewer-defensible, implementable research idea with a concrete method and falsification plan from a stated research direction. Use when the user asks for a research idea, novelty analysis, bottleneck diagnosis, or paper-shape suggestion. Skip code review, debugging, and unconstrained brainstorming without research context.
WeChat Official Account Graphic Pipeline · Use this when the final state is **formatted WeChat Official Account HTML** or **article saved to your own WeChat Official Account draft box** (only saves drafts, never sends mass messages). The input is **already written** Markdown/HTML. This pipeline does not write the main content, only performs deterministic operations afterwards: rendering → pre-uploading images → cover design → saving drafts. ⚠️ It will **write to your own WeChat Official Account backend**, so users should not run it without explicit intention when the draft is completed. Binding an account + DOUBAOYA_API_KEY is required to save drafts; not needed for local rendering only / theme switching. Trigger words: How to send after writing the main content / Need formatted WeChat Official Account HTML / Continue formatting and send to draft box / Write for WeChat Official Account / Convert to WeChat Official Account formatting / Push to WeChat Official Account draft box / Re-push draft / Publish to draft box with cover / Save article to WeChat Official Account draft box / WeChat Official Account Graphic Pipeline / dby-publish / Save to WeChat Official Account draft box / WeChat Official Account draft box / Submit to WeChat Official Account draft box on behalf / addDraft / draft/add / Push graphic to WeChat Official Account / Send draft to WeChat Official Account backend.
Draft and open a GitHub pull request from your branch, with title, summary, and test plan written from the actual commits and diff, then created with the gh CLI, embedding verifykit proof artifacts inline when a bundle is present. Use when the user asks to open a PR, says "create a pull request", "raise a PR", "submit this for review", or "gh pr create", even if they don't spell out the title or body.
Own the GitHub issue lifecycle with five modes: create issues from a plan or description (kept independent for parallel worktree work), start a `ready` issue into its own worktree, close one out once its PR merges, sync PR↔issue links after merge, and triage the tracker for lifecycle and priority gaps. Use when the user says "create issues from this plan", "file an issue", "start issue #42", "close #42", "wrap up #42 now the PR merged", "sync my issues", "triage the backlog", "prioritize my issues", "set the priority on #42", "issuekit", or wants issues opened, started, landed, reconciled, ranked, or reviewed with the gh CLI.
Create a git commit with a Conventional Commits message derived from the actual diff. Use when the user asks to commit changes, says "commit this", runs "/commitkit", or wants a well-formed commit message written for staged work, even if they don't spell out the format.
Manage promotions in a Yandex KIT store over its REST API: discounts, promo codes, promocode groups (shared codes and single-use coupon batches) and gifts. Use when creating or updating discounts, promocodes, promocode groups or gifts, or when binding them to products, categories or collections.
Unified entry for Feishu instant messaging, covering sending, replying, forwarding, merged forwarding, urgent messaging and resource downloading, reading chat history, Reaction, Pin and group member management, constructing V2 interactive cards, and WebSocket event subscription. This Skill must be used when users request to send messages or notifications, view or export group chats, manage group members, create Feishu cards for alerts/approvals/reports/dashboards/marketing promotions/festival greetings/brand displays/hand-drawn or dark-themed creatives/cards with buttons or charts, listen to real-time message or approval events, or process message attachments. This Skill must be triggered as long as the target carrier is Feishu chat or group messages, or the request contains terms like msg/chat/card/event, post/interactive, oc_/om_, Reaction, Pin, urgent messaging or local images in messages, even if the user doesn't explicitly mention CLI. Do not use it for email reading/replying/drafting, nor for meeting recording, Minutes or verbatim transcripts; use feishu-cli-mail and feishu-cli-meetings for those respectively. Use feishu-cli-platform for global message search.
Run a gated software development lifecycle for a repo. Use for `/jig init` (understand the codebase and scaffold project memory), `/jig task "<request>"` (start an issue/bug/feature through spec→implement→test→review→ship), `/jig status`, `/jig config` (view/set/validate settings), `/jig memory-refresh`, and `/jig resume`. Triggers on "jig", "run the lifecycle", "start a task", "sdlc", "sdlc init/status".