Loading...
Loading...
Found 10,506 Skills
Use when the user asks to commit changes, organize commits, write commit messages, or split working-tree changes into Conventional Commits. Trigger on phrases like "commit my changes", "커밋해줘", "커밋 분리", "make commits", "/conventional-commit", or whenever the user wants to turn current changes into Conventional Commit-style commits. For commit + push use `conventional-commit-push`; for rewriting non-Conventional commit history use `conventional-commit-rewrite`.
Backup-first skill for inspecting, archiving, and maintaining local Codex state to keep it fast, clean, and recoverable.
Create and edit Omni Analytics semantic model definitions — views, topics, dimensions, measures, relationships, and query views — using YAML through the Omni CLI. Use this skill whenever someone wants to add a field, create a new dimension or measure, define a topic, set up joins between tables, modify the data model, build a new view, add a calculated field, create a relationship, edit YAML, work on a branch, promote model changes, or any variant of "model this data", "add this metric", "create a view for", or "set up a join between". Also use for migrating modeling patterns since Omni's YAML is conceptually similar to other semantic layer definitions.
First onboarding and scaffolding creator for cheat-on-content. Unified process - all users follow the same 5-stage closed-loop, with the only difference being that users who have posted videos will have an extra step during init: fetch existing videos to build historical context (used for subsequent cheat-seed to provide more tailored topic suggestions and more accurate baselines). Trigger phrases: "Initialize" / "init" / "First use" / "I'm a new user" / "setup cheat-on-content". **Must be executed during the user's first session; other sub-skills will automatically route to this when .cheat-state.json does not exist.**
Create a PRD from current context, then break it into tracer-bullet issues and publish everything to the project issue tracker. Use when user wants end-to-end issue creation from a plan, idea, or requirement.
Open a named, traced browser session into an RVF cognitive container with a ruvector trajectory recording every action
Process Street integration. Manage Organizations, Integrations. Use when the user wants to interact with Process Street data.
Use when given a GitHub issue URL or number to investigate and implement a fix. Triggers on "fix issue", "fix bug", "fix
Fetch review comments from an existing GitHub pull request and implement the requested changes. Use when user says 'address PR feedback', 'implement review comments', 'fix the PR review', 'reviewer asked for changes', or 'my PR got comments'. Do NOT use for initial PR creation (use create-pr) or for writing your own review (use review-diff).
Sales rep / account manager persona for Spark. Client relationship tracking, pipeline review, follow-up cadence, and deal context.
Use when an agent reports a discovered task via Nexus, to review, approve as official task, reject, or escalate to idea
Inspect active background research work including running processes, scheduled follow-ups, and pending tasks. Use when the user asks what's running, checks on background work, or wants to see scheduled jobs.