From 5608ad603772903860160444358f394b2cae6196 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Mon, 26 Oct 2026 03:13:05 +0000 Subject: [PATCH] fix: restore cursor-team-kit wording in poteto-mode The adapter already says this port bundles deslop, control-cli, and control-ui. The two bullets go back to the upstream sentences. Co-authored-by: Kaitian Xie --- .agents/skills/poteto-mode/SKILL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.agents/skills/poteto-mode/SKILL.md b/.agents/skills/poteto-mode/SKILL.md index f4d44ab..8663079 100644 --- a/.agents/skills/poteto-mode/SKILL.md +++ b/.agents/skills/poteto-mode/SKILL.md @@ -24,9 +24,9 @@ Remaining triggers: - Nontrivial multi-step → write the throughput checkpoint (Feature step 3). - Any prose surface, your reply to the user included → the **unslop** skill. Write the reply per **Writing the reply**. Agent-facing prose also follows the **skill-creator** skill when available (for authoring SKILL.md files). - Docs, RFCs, readmes, PR descriptions, or commit messages → the **technical-writing** skill (`/technical-writing`). -- Before commit → the bundled `deslop` skill (`/deslop`). +- Before commit → the `deslop` skill from the `cursor-team-kit` plugin (`/deslop`). - Before review → the **no-comments** skill (`/no-comments`). -- Shipping UI / IDE / CLI → the matching control skill. This port bundles `control-cli` (CLIs and TUIs) and `control-ui` (browser / Electron / web UIs). For bug fixes, reproduce first on the same surface yourself. Hand to the user only under the narrow Bug fix step 1 exception. +- Shipping UI / IDE / CLI → the matching control skill. `cursor-team-kit` publishes `control-cli` (CLIs and TUIs) and `control-ui` (browser / Electron / web UIs). For bug fixes, reproduce first on the same surface yourself. Hand to the user only under the narrow Bug fix step 1 exception. - Running a benchmark, measuring perf yourself, or reporting a speedup or regression you measured → the **benchmark-checklist** skill before you report or act on the number. - Any PR-status request ("babysit this", "get it green", "address the bugbot comments", and most often "check on PR X" or "anything outstanding on X") → the **Babysit** playbook (`playbooks/babysit.md`), not Cursor's built-in babysit skill, whose description matches the same words. Never triggered by merely opening a PR. Declare its mode before polling. The playbook's step 1 owns the request-to-mode mapping. Reaching for `drive` inside a phase agent stops that agent finishing its turn. - Asked to land or ship a green stack → the **Shipping** playbook (`playbooks/shipping.md`). Green is not safe. Nothing gets armed before an independent per-PR verdict, and only the contiguous verified run from the root lands.