Cursor releases Team Kit with /verify-this, /loop-on-ci, and harness skills

• Cursor shipped Cursor Team Kit, a first-party plugin that packages internal workflows for CI, review, cleanup, and work summaries, according to ericzakariasson's launch post.
• The sharpest skill is ericzakariasson's /verify-this post, which makes an agent show baseline evidence, treatment evidence, commands run, and a verdict instead of hand-waving.
• ericzakariasson's CLI harness post and ericzakariasson's UI harness post show Cursor turning local automation into reusable agent skills for TUIs, web apps, and Electron flows.
• The shipping loop is explicit: ericzakariasson's /loop-on-ci post keeps an agent on a PR until checks pass, while ericzakariasson's PR cleanup post and ericzakariasson's merge conflict post focus on making the result reviewable and safe to merge.
• Installation is just /add-plugin cursor-team-kit, as ericzakariasson's install post and the official marketplace page both show.

You can browse the official plugin page, trace Team Kit back to Cursor's broader plugin system, and see how it fits the newer team marketplace controls. The interesting bit is that Cursor did not publish one monolithic "agent that ships code" feature. It exposed the smaller habits around evidence, harnesses, review hygiene, and CI persistence as separate commands.

The official Cursor Team Kit page describes it as internal workflows used by Cursor developers for CI, code review, shipping, control-cli, control-ui, verify-this, cleanup, and work summaries. Cursor's earlier plugins launch post says plugins can bundle skills, subagents, MCP servers, hooks, and rules into one install.

That framing matters because Team Kit looks less like a single feature and more like Cursor open-sourcing part of its internal agent harness.

/verify-this asks for four things:

• baseline evidence
• treatment evidence
• commands run
• a clear verdict

That is a small command with a strong opinion. It pushes the agent to produce something closer to a test report than a confident paragraph.

The automation skills split into a few concrete buckets:

• control-cli and /cli-automation-harness for PTYs, tmux, readiness checks, and disposable harnesses around interactive CLIs and TUIs, per ericzakariasson's CLI harness post and the official plugin page
• control-ui and /ui-automation-harness for browser automation, CDP inspection, screenshots, and local app flows, per ericzakariasson's UI harness post
• /make-pr-easy-to-review, /pr-review-canvas, and /deslop for reducing noisy diffs and AI-generated cruft, according to ericzakariasson's PR cleanup post, ericzakariasson's review canvas post, and ericzakariasson's deslop post
• /fix-merge-conflicts and /loop-on-ci for conflict resolution, post-merge validation, and repeated CI fixing until checks go green, per ericzakariasson's merge conflict post and ericzakariasson's /loop-on-ci post

A separate Cursor changelog from May 1 explains why this package shape matters. Team marketplaces can now distribute plugins as default-off, default-on, or required installs, which means the same skills bundle can move from a personal shortcut to an organization-wide default.

That changelog also says plugins can carry MCP servers, skills, subagents, rules, and hooks. Team Kit is the clearest example yet of Cursor using that bundle format to ship its own internal operating procedures.