Cursor Launches Official Plugins Repository for Agent Skills and Rules
Cursor published its official plugins repository featuring structured directory manifests for developer tools, SaaS, and agent skills. Developers can now package repeatable agent rules, skills, and subagent orchestration flows directly into their IDE.
Impact: High
Why it matters
You can immediately standardize team coding rules and custom subagent workflows using official Cursor plugin manifests.
TL;DR
- 01Cursor established an official plugin marketplace format using .cursor-plugin/plugin.json manifests.
- 02Plugins support modular skills (SKILL.md) and IDE rules (.mdc) for team-wide sharing.
- 03Orchestration workflows like multi-agent branch review and self-referential loops are now standardized.
Key facts
- Manifest Format
- JSON (.cursor-plugin/plugin.json)
- Rules Extension
- .mdc
- Skills Definition
- SKILL.md with frontmatter
Standardized Directory Structure
The repository introduces a multi-plugin marketplace architecture. At the root, .cursor-plugin/marketplace.json defines all available plugins, while individual plugins contain their own .cursor-plugin/plugin.json manifest alongside skills/ and rules/ directories. Agent skills are authored as SKILL.md with frontmatter, and IDE behavior rules are stored as .mdc files.
Workflow and Orchestration Plugins
The hub includes specialized workflows for software delivery. Notable additions include automated memory updates for AGENTS.md via incremental transcripts, and deep branch reviews featuring parallel subagents, harsh quality rubrics, and automated pull request generation. Other workflows support iterative self-referential AI loops with the Ralph Wiggum technique and parallel cloud agent dispatch with planners, workers, and verifiers.
Developer Tooling and SaaS Integrations
Beyond engineering workflows, the marketplace includes integrations for SaaS platforms and developer infrastructure. Plugins provide capabilities to query and update pull requests, navigate and screenshot within real browsers, search internal documentation canvases, and manage third-party APIs across candidate tracking, analytics, and CRM systems.
Try it in 2 minutes
{
"name": "team-workflow",
"skills": ["skills/review.md"],
"rules": ["rules/code-style.mdc"]
}json
✓ When to use
- When packaging reusable .mdc rules, skills, and subagent review workflows across an engineering organization.
- When standardizing IDE prompts and project-level conventions inside Cursor.
✕ When NOT to use
- When writing quick one-off personal scripts where basic local .cursorrules suffice.
- If your team relies exclusively on other IDEs like VS Code or Zed without Cursor.
What to do today
- Inspect the cursor/plugins GitHub repository structure.
- Convert existing custom rules into structured .cursor-plugin/plugin.json manifests.
Sources