Loading...
Loading...
Found 9,439 Skills
Main entry for WeChat Official Account content: completes topic selection, material collection, writing, and review, and independently adds image matching, typesetting, or draft box publishing as requested by users. It is also responsible for distributing style settings, learning & revision, data review, and multi-platform rewriting to the corresponding wewrite-* modules. Trigger keywords: 公众号 (Official Account), 微信文章 (WeChat article), 微信推文 (WeChat tweet), 草稿箱 (draft box), 微信排版 (WeChat typesetting), 写公众号 (write Official Account article), 写一篇 (write an article). General articles, blogs, emails, short videos, and website SEO do not trigger this skill.
Manage issues within Gitea/Forgejo milestones — list, add, remove, progress tracking, burndown, bulk assign, and move between milestones.
Create Gitea/Forgejo pull requests — interactive, with flags, from forks, WIP conventions, and quick patterns.
Use when an agent drives Godot 4.7 on a Mac for any task: headless --script jobs, --import, --check-only, command-line exports, GUT tests, windowed screenshots, the headless editor (-e) or an MCP server into a running editor; when a run hangs or fails silently, a capture is black, Godot 3 code breaks in 4.x, 'Identifier not found', export templates are missing; or when a Godot brief (2D, 3D, shaders, VFX, UI, multiplayer, export) must go to the right scenario-godot-* specialist.
This skill should be used when the user asks about "pantsing", "discovery write", "write without an outline", "discovery draft", "write into the dark", "story kernel", "reconcile a chapter", "dead end", "drafting sprint", "writing cadence", or wants to draft a story by discovery with retrospective bible reconciliation. NOT for outline-first drafting, or mysteries and other clue-dependent genres where setup must come before payoff (use chapter-writing), or a reverse outline of an existing linear draft, a subplot cut, or another revision pass on existing chapters (use revision-continuity).
どのスキルを導入するか決める。全員が入れる既定のスキル、作業に応じて追加するスキル、npx skills によるホームへの導入と削除、統合済みの旧スキルを入れない判断、リポジトリ固有のスキルを置くかどうかの判断を定義する。スキルを初めて導入するとき、philtzjp/skills に新しいスキルが追加されたとき、作業に必要なスキルが入っていないとき、不要になったスキルを外すときに使う。
Adds the registered Enterprise lifecycle adapter to a compatible Core installation. Use only when the user explicitly enables the Enterprise layer.
The single entry point for every local VN action: opening a lightweight VN preview import, or planning and building a rough cut as a local VN video-editor draft with `cawcut vn`. Media can be the user's own local files supplied directly, or another CawCut skill's generated output — both are first-class. Always starts by asking whether the user wants a quick preview-and-import or the full editing flow. The editing flow inventories supplied media, confirms the project aspect ratio, recommends feasible editing styles, resolves missing music or sound effects, presents a shot-by-shot edit plan for approval, then assembles and validates the draft before asking whether to open it in VN. Use when creating or editing VN projects, assembling the user's own photos/clips or generated media into a timeline, making a slideshow or rough cut, previewing local files in the VN app, or invoking `/cawcut-vn`. Fully local; no login needed. NOT for generating source media.
Use when the developer wants the agent to work without approving every write - "tu dong hoan toan", "cu lam het di", "dung hoi tung buoc", "work autonomously", "approve everything for this task", a long build session - or when an apply preview says autopilot is active, paused, expired or not covering a statement. Requests one developer-approved lease, works strictly inside it, stops where it stops, and reports every write it made.
Set up and scaffold Notion Apps with the Notion Apps SDK and `ntn`; use when starting a Notion App project.
Create a plan for the specified task and store it as GitHub issues in the repository of the current working directory. Given the URL of a GitHub issue, it turns that issue into the parent "plan" issue (Goal, Context and a checklist of phases) and creates one child issue per phase, linking every phase as a native GitHub sub-issue of the parent. Stops for user approval before creating any issue. After creation, the plan is meant to be implemented with the codely-plan-phase-implement-github skill.
Delegate complete browser tasks to qz, an autonomous agent in the user's browser. Use when a separate agent should plan and carry out the browser work, such as cross-site research, comparisons, structured data collection, or multi-step web workflows. Provide the goal and expected deliverable; qz executes the task and returns results or questions that need user input.