Loading...
Loading...
Found 2,510 Skills
Create, update, or inspect a pull request; prepare its title, description, review evidence, and metadata; publish a branch for review.
Draft, edit, review, and refine all human-facing writing, from short-form copy to connected prose. Use it whenever readers must follow ideas, context, reasoning, narrative, or tone. Use it across technical surfaces such as package and repository descriptions, README and technical document content or information architecture, CLI wording, JSDoc and docstrings, explanatory source comments, runtime messages, test titles, labels, and repository collaboration through issues, pull requests, and Discussions. Do not use for LICENSE text, formatting-only work, or tasks that neither evaluate nor change wording or information architecture. Agent responses are not a trigger on their own.
Routes questions about the Cursor Origin API to the right section of the Origin docs and names the few rules to check first. Use when a task mentions Origin, the Origin API, Origin Apps, or Origin webhooks, including creating an Origin App, authenticating as one, calling Origin endpoints, or handling Origin webhook deliveries.
Use when creating or updating a PR in the kimi-code repository: how to write each section of the PR template concisely so that reviewers can easily understand it, including the "Behavior Changes and Affected Users" table.
Capture screenshots of the Sentry UI in a web browser, lay them out in a pull request description as before/after tables, and upload them with `gh --attach`.
Run the software factory. Use when the user types /factory alone or /factory help (prints the help), /factory
Watches a pull request through CI and review, fixes real findings and stops when it is ready, merged or blocked. Use when the user asks to watch, monitor or babysit a PR, or /ds-watch-pr.
Finish a PR by repeatedly requesting a Kelos review, waiting for its check, addressing valid review findings, squashing commits, and updating the PR until a review approves and that iteration is finalized. Use when the user says "finish-pr" or asks for this review-and-fix loop. Defaults to the PR for the current branch.
Track Remotion CI flakes in issue
Write a branch's PR body that tells a reviewer how much attention it needs, with a visual summary, harvested evidence and a fresh-context one-way or two-way door call, then put it and an attention label on the branch's PR. Use when a branch is ready for review, when the user says "write the PR body", "update the PR description", "how risky is this PR", or "is this ready to merge", and when another skill closes a branch.
Monitor a pull request through review and CI. Use when the user asks to monitor, watch, or babysit a PR.
Find what your goal needs that the workspace has not built: once a week a deployed agent reads the company goal, takes stock of every play, agent, model and connector in the workspace, and suggests at most five missing pipelines from the published catalog, each opened with what it noticed ("thousands of accounts, none scored"), as a pull request you can decline lines in and a Slack post. Triggers: "what should we be running", "what are we missing for our goal", "suggest new plays for our goal", "which pipelines should we set up next", "we have 25 plays and do not know which 5 matter", "tell us what to build, do not wait to be asked". Cargo project, defineAgent, harness claudeCode, catalog.json, plan/company-plan.md, Slack. Skip when: you want existing initiatives graded against last week's runs, which is weekly-planning; or something deployed is failing, which is workspace-health.