Loading...
Loading...
Found 1,180 Skills
Use when the user asks to review code, review changes, review a commit, review a PR, audit code quality, check for security issues, or generate a code review report. Trigger on phrases like "review my changes", "코드 리뷰", "check my code", "review the last commit", "what do you think of this diff", "compare branches", "code audit" — even if they don't say "code review" explicitly. For persistent file output use `code-review-md` (markdown) or `code-review-html` (markdown + HTML).
End-to-end orchestration for non-trivial software feature development. Use this skill whenever the user asks to implement a PR-sized feature, break down a plan, have subagents review a plan, run a plan-review-development-acceptance loop, coordinate multiple review perspectives, produce an acceptance report, or generate an HTML PR summary. Prefer this skill for multi-step code changes even if the user only says "build this feature" and the task is not a tiny one-file edit.
Use when the user has one or more video clips and wants to add post-production on top — AI-generated cover as first frame, HTML/CSS captions synced to SRT, kinetic illustration overlays at hook moments, chapter chips, end-card CTA, or any other timed motion graphics. Most often used as the downstream of `/wjs-segmenting-video` — pick up where that skill stopped (raw cropped clip + per-clip SRT) and produce the upload-ready MP4. Backed by HyperFrames so everything compiles to ONE final encode — no cascade of re-encodes. Triggers — "加封面", "加字幕", "加动画", "加 CTA", "做后期", "post-production", "title card", "kinetic captions", "end card".
Map triaged findings to the correct Azure DevOps work item types for the TARGET project's process, and emit backlog_input.json ready for creation. Use this AFTER triage and BEFORE creating items — when the user asks "what type should these be", "make these into work items / tickets", "turn these findings into a backlog", "classify these for ADO", or "build the backlog input". The type you choose MUST exist on the target board: a Basic-process project has no Bug or User Story, so picking those silently fails at creation time. This skill discovers the project's process first, applies industry typing rules (defect vs new capability vs grouping parent), maps severity to Priority, builds the per-type fields (titles, tags, repro/description as escaped HTML), carries each finding's `key` through, and hands off to ado-create-work-items.
A long-tail product collection skill covering low-frequency DingTalk products: OA approval query and handling / legal smart contract / attendance / live / DING urgent messages / Open Platform apps and MCP development / Agoal goal management / log daily-weekly reports / spreadsheet / Open Platform doc search and OpenAPI escape hatch / standalone and doc-embedded whiteboard / DingTalk recruiting / DWS skill marketplace installation / Organization Brain Hrbrain / native Markdown / native HTML / PAT behavior authorization / multi-organization profile. Use when the user mentions any of the above products, especially Agoal/goal management/strategy decoding/business contracts and field configuration/scorecard/OKR/goal rules and periods/personal goals/goal templates/weekly-monthly report rule submission statistics/on-time/late/missing/follow-up, or querying/creating contract ledgers, batch importing contracts, drafting contracts from transcripts, archiving contracts, managing contract projects/counterparties/payments, or checking pending approvals/approve-reject-transfer-revoke approvals/clock-in/scheduling/daily-weekly report content filling/standalone whiteboard creation with content/whiteboard node read-write/cell read-write/recruiting positions/JD/creating positions/searching and installing skills/developer console apps/enterprise internal apps/checking app status or deletability/app member and role summary/app version history/enterprise internal app robot configuration, message mode, or online status/local robot connector/Stream connection/MCP services or tools/publishing or debugging MCP/fetching or invoking published MCP/turning OpenAPI, Swagger, Postman, curl, or HTTP interfaces into MCP or for Agent use/unwrapped OpenAPI/llms.txt/dws api/talent pool/employee profile/career history/performance/native .md files/Markdown version comparison/local draft diff/Markdown comments/native .html files/creating HTML pages/PAT authorization/switching organization/cross-organization/profile, and other related operations. Weekly/monthly report content filling belongs to report; rule-level on-time, late, missing statistics and personnel follow-up belong to Agoal; submitting daily/weekly/briefing reports with approvers, CC recipients, or approval flows belongs to OA approval. Real-time listening for future approval tasks or instance changes is not part of this skill; use dingtalk-event. After a match, the skill's Product Index Table locates the specific sub-product and command prefix, then executes according to that sub-product's instructions.
Explains concepts, PRs, and designs for a specific reader as concise crash-course material without unnecessary verbosity, and verifies the diagrams and claims with tools. Build the reader persona—including what they already know, what they do not know, and how they read—from questions and public information, and write only the resulting delta. Create diagrams with vlmkit-anim against a fact sheet, re-run and cross-check code and output quoted in the body, and pass the HTML through vlmkit's validation gates. Use when the user says “explain this to me / to <person>”, “crash-course material”, “explanatory documentation”, “I want to understand this PR”, “explain it so I understand”, “I can't keep up with what the agent wrote”, or when a reviewer asks what a change does and the answer needs more than a paragraph. Also use it when the user wrote an explanation themselves and lost confidence in it.
Classify and wire Remotion Studio config options as either startup-fixed or reloadable while preventing mixed lifecycle behavior across consumers. Use when adding, changing, or reviewing a Config setter or CLI option consumed by Studio, its preview server, compiler, HTML bootstrap, public-folder watcher, or render queue.
Start here for Yandex DataLens when the task has not yet settled on a tool, or when the question is about DataLens itself rather than about carrying something out in it: what DataLens is and what it can do; which installation is in play — Yandex Cloud, on-premise, or the internal Yandex Team one — and how they differ in hosts, auth, and capabilities; what a collection, workbook, connection, dataset, chart, or dashboard is and how they relate; and whether to reach for the MCP server, the Python SDK, the HTTP API, or the web UI. Use it to orient and to route to the skill that does the work. NOT for doing the work once the approach is chosen — that is `datalens-sdk` for Python and `datalens-html-pages` for standalone HTML reports — and not for interpreting what business metric values mean.
Build or change an Anfra Data App — one self-contained HTML file in the repo's `apps/` that queries datasets, and can trace fields' lineage, through the `Anfra` SDK global and renders them with its own HTML, CSS and JS — then check it in `anfra serve`. Use for a dashboard, report, page or interactive analysis over the repo's datasets.
Ensures zero-mismatch integrity between server-rendered HTML and client-side React trees. Use when debugging hydration errors, fixing text content mismatches, handling browser extension DOM pollution, implementing selective hydration with Suspense, using the React 19 use() hook for deterministic server-to-client data bridges, or applying Next.js use cache for data drift prevention. Use for hydration mismatch, SSR, hydrateRoot, suppressHydrationWarning, onRecoverableError, two-pass rendering.
Review code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md workflow compliance. Supports any tech stack - HTML/CSS/JS, React, TypeScript, Node.js, Python, NestJS, Next.js, and more. Use when completing features, before commits, or reviewing pull requests.
Automatically injects the project's extracted design soul into any frontend task. Use this skill on EVERY request that involves building, editing, or reviewing UI — including components, pages, layouts, styles, animations, and design decisions. Triggers on: any prompt containing words like "build", "create", "make", "design", "component", "page", "layout", "button", "form", "card", "nav", "header", "modal", "style", "css", "tailwind", "animate", "responsive", "ui", "frontend", "screen", "dashboard", "landing", "section", or any request to write JSX, TSX, HTML, or CSS. Do NOT trigger on backend-only tasks, database queries, API routes with no UI, or pure logic/utility functions with no visual output. This skill has no slash command — it runs silently in the background on every frontend task. The user never needs to invoke it manually.