Loading...
Loading...
Found 10,410 Skills
Split uncommitted changes into focused, logical commits using git-hunk. Use when asked to "split changes", "split commits", "organize commits", "commit by hunk", or "separate changes into commits".
End-to-end pipeline for writing and publishing an article to the WeChat Official Account draft box. Triggered when the user says "help me write a new article", "write an article for the Official Account", "add illustrations, typeset and send to draft box", "post directly to WeChat Official Account", "publish with illustrations", "write and publish", or any combination of writing + illustrating + posting to WeChat that requires no manual confirmation steps.
Run an interactive naming session for a project. Use when the user wants to name a project, app, package, tool, or repo. Presents names in rounds, tracks preferences, and refines suggestions based on selections.
Use when starting a new project with Maestro or when no .maestro.md context file exists yet. Run once per project.
Create new tasks in TeamBition projects
Enter copilot mode — human drives, Claude assists. Relaxes worktree enforcement, allows main commits.
Inventory all founder resources across 8 categories for a one-person company. Use when Codex needs to systematically confirm what resources the founder has — experience, network, skills, relationships, channels, assets, time/money constraints, hard limits — by first doing a broad scan of each category, then drilling into specifics (distribution, usable portions, how to use, cost of use), and producing a confirmed detailed resource inventory written to `opc-doc/`. Does NOT analyze directions, preferences, suitability, or risk tolerance — those belong to downstream skills.
Capture idea or task as todo from current conversation context
Audit milestone completion against original intent before archiving
Gather phase context through adaptive questioning before planning
Validate built features through conversational UAT
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.