Loading...
Loading...
Found 11,598 Skills
Use when implementing any feature or bugfix, before writing implementation code
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Start here for first-time CARTO use — install the CLI, authenticate, switch profiles, understand JSON output and async job patterns. Also orients on the two parallel access paths into the CARTO platform (CLI for authoring/scripting, MCP server for inline interactions in chat hosts) and which skills cover each.
Create a git commit with clear, conventional commit messages. You MUST read this when the user wants to commit staged changes, write a commit message, or finalize code changes with proper conventional commit format since it describes how to follow the user's specific requirements.
Three modes. Session mode (default): extracts generalizable lessons from RESEARCH.md and git history at session end; lessons that imply a new or significantly changed skill are handed off to skill-creator. Personalize mode: searches the skills registry via `npx skills find`, reads the target skill(s), checks compatibility and scope overlap against installed skills, interviews the user to understand what they want and what to skip, then creates or improves skills using skill-creator. Registry mode: curates `skillpacks/skill_dictionary.yaml` and `skillpacks/presets/*.yaml` by assessing external packs, judging necessity/compatibility, and recommending subsets. Create mode: designs a brand- new skill from scratch using skill-creator. Never edits SKILL.md directly — all changes go through skill-creator's draft→test→iterate loop, human merges. Trigger phrases: "end session", "extract lessons", "personalize my skills", "integrate this skill", "update skillpack", "find a skill for", "create a skill", "improve skill", "refresh the skillpack registry", "assess this skill pack", "update skill_dictionary.yaml", "update index.yaml".
Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts. Use when user asks 'where are we in development', 'what stage are we in', 'full project audit'.
Single-pass feature implementation using Explore → Code → Test. Ships focused changes at maximum speed, with a built-in circuit breaker that stops and recommends `/apex` or `/forge` when the task turns out more complex than it looked. Use this whenever the user wants a quick win on a single, focused task — even when they don't say "oneshot" (e.g. "just", "quickly", "small change", "#42", or a GitHub issue URL for a small fix).
Generate a 65-second founder-style product video from a product URL + user-supplied imagery. Output is a 16:9 1080p MP4 — 4 × 15s SeeDance acts of a talking founder + 5s branded end card + background music. The user's actual product screenshots appear on the founder's phone in reveal shots, so on-screen UI is real, not AI-imagined. Triggers — "founder video", "product video", "60s pitch video", "make a video of [founder] for [URL]", "talking founder explainer". Requires Pika MCP. Uses a supplied brand kit folder (`brand.json` or an exported build-a-brand kit with `brand.md`, tokens, logo assets); if no kit exists, run build-a-brand first.
Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.
Turn Hermes into an autonomous project executor using Kanban boards inside Obsidian vault with visual rendering and REST API control
The orchestrator and entry point for the engineering skills suite. Use this skill whenever the task involves doing engineering work to a high bar — reviewing code or a design, designing a new system or component, debugging a hard problem or running an incident, implementing a substantive change, writing documentation, or sanity-checking an approach. Use it when the user phrases things casually ("rip into this", "be brutal", "is this approach right", "what am I missing", "what would you change", "look at this") or formally ("review this PR", "audit this design"). Use it proactively for any non-trivial engineering work, before declaring something done. The skill triages the work, dispatches to the right specialty skill(s), enforces verification, and produces an evidence-backed result. The goal is to ensure no AI shortcut, sycophantic agreement, or stylistic distraction gets in the way of work that holds up to senior-engineer scrutiny.
Identify sector rotation, capital switching and style migration directions, help judge the current market main line, compensatory growth directions and rotation sustainability. Suitable for market style observation, sector comparison, post-market review and next-stage main line judgment.