Loading...
Loading...
Found 2,348 Skills
Transform feature descriptions into well-structured project plans following conventions
Generate and critically evaluate grounded improvement ideas for the current project. Use when asking what to improve, requesting idea generation, exploring surprising improvements, or wanting the AI to proactively suggest strong project directions before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on this project', 'surprise me with improvements', 'what would you change', or any request for AI-generated project improvement suggestions rather than refining the user's own idea.
Break down characters/looks, locations/views, props/states, and cross-scene continuity from a short-drama script, and write them into creator-readable visual settings. Use when the user says “break down characters/scenes/props,” “make asset settings,” “decide whether to reuse or create a new variant,” “update looks/prop states,” or brings an existing script directly for visual asset preparation; do not write image prompts, and do not generate media.
Document a recently solved problem to compound your team's knowledge
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Use this skill whenever the user mentions changelogs, release notes, version updates, "what changed", product updates, app store descriptions, or needs to summarize recent development work for non-technical audiences.
Review GitBook change requests from Claude Code by calling the GitBook REST API directly with curl (no CLI) — the reviewer-side companion to cr-create (the authoring side over the same API). Discover the change requests that need review (filter by who opened them, by space, or across a whole org), get the GitBook app link to review the diff, summarize what actually changed in a CR, then leave comments and optionally submit a review verdict (approve / request changes). Use this whenever someone wants to review docs change requests over the raw API (curl/HTTP), asks "what CRs are open / waiting on me / opened by <person>", "show me the change requests in <space>/<org>", "summarize what changed in this CR", "review this change request", "leave a comment on a CR", or "approve / request changes on a CR". For the authoring side (create a CR, push content, request reviewers, fix comments) over the API, use cr-create instead.
Patterns for writing clear, consistent API field descriptions including types, constraints, examples, and edge cases.