Loading...
Loading...
Found 192 Skills
use-skill to fetch and run GitHub-linked skills ephemerally, without installation.
Find an open-source, reverse-engineered tool for a closed app, API, device, protocol, file format or game, then read or fetch it. Use when a task needs to talk to something that has no official API, SDK, driver or spec, or only a limited one. Examples include "control my Tuya plug locally", "read a .psd or .dwg file", "unofficial WhatsApp, Instagram or Bilibili client", "Bambu printer protocol", "talk to my car's API", "Garmin or CGM data", "decompilation of a game" and "OpenAI-compatible proxy for a web chatbot". The skill searches a curated index of 12,000+ verified projects ranked by stars, language, license and activity.
Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, impact and evidence. Agent-autonomous for facts and for actions covered by standing authorization; signed for every new judgment. Never merges.
Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.
Manage and generate .gitignore files using the official GitHub gitignore template library via the `ign` CLI. Use when initializing new project repositories, automatically detecting project stack from files, adding language/framework/IDE ignore rules, inspecting applied templates, or safely modifying existing .gitignore files.
Pick the right deepseek-stack skill for a task and explain how the pack fits together. Use when the user asks which skill to use, what the pack contains, or types /ds-help.
Architecture and building-blocks reference for the Docyrus platform — what the platform is made of (apps, data sources, fields, enumerations, custom queries, automations) and how the pieces fit together. Use when you need conceptual context about how Docyrus works, what its building blocks and capabilities are, or to decide which dedicated skill to use for a task. This is the conceptual map and router; hands-on how-to lives in the dedicated design / CLI / API skills it points to (data sources, automations, agents, AI tools, templates, webforms, ACL, querying, the CLI, and the REST API).
Front-door on-demand cho phát triển framework HOẶC distill/author một skill — SELF-CONTAINED, chạy được ở BẤT KỲ project nào (không phụ thuộc file repo-local). Gọi khi đang sửa chính framework, hoặc đang viết/chưng cất một skill trong phiên của dự án khác. KHÔNG dùng cho dev tính năng dự án thường (đó là phần lớn phiên — ADR-004).
Investigate, document, or change an unfamiliar legacy codebase using local repository maps, scoped source context, and verified evidence. Use for undocumented internal frameworks, cross-module behavior, or large repositories; a known-file edit or single-symbol search usually needs only direct search.
Experience a source-accessible library or developer tool through outcome-oriented slices before reading its implementation, and report honest coverage and observable findings without repairing or publishing them.
Load this skill when you are required to create projects. Do not load this skill when you are creating reproduction/poc repo.
Use, debug, or maintain `@wot-ui/cli` and the open-wot repository. This Skill covers wot CLI commands, Agent/MCP integration, doctor/usage/lint, component knowledge queries, client adapters, offline data extraction, build testing, release package inspection, and repository development; if a task directly involves writing wd-* component pages or explaining component APIs, use the wot-ui-v2 Skill instead.