Claude Code Plugin Scaffold

.cursor/skills/claude-code-plugin-scaffold

plugin.json, marketplace.json, and one command + one skill, wired correctly.

Where it installs

# .claude/skills/claude-code-plugin-scaffold/SKILL.md
---
name: claude-code-plugin-scaffold
description: ...
---
# identical content, skills are the same file in both editors

What it does

Claude Code Plugin Scaffold is a Cursor skill: a SKILL.md playbook that AgenticKit installs at .cursor/skills/claude-code-plugin-scaffold. Cursor's agent loads it when the task matches the skill description, instead of stuffing the same rules into every chat.

Teaches the agent the exact shape of a Claude Code plugin: the plugin.json manifest, a marketplace.json entry for distribution, and how commands/ and skills/ bundle together so `/plugin install` or a local marketplace add picks it up without errors.

plugin.json, marketplace.json, and one command + one skill, wired correctly. The file is domain knowledge, not a slash macro. You do not type it. The agent reads it when the job is claude code plugin scaffold.

Why it exists

Default Cursor has no memory of how your team ships code, schema, and tests. Founders paste the same conventions into chat, then watch the model drift on the next turn. This skill exists so those conventions live on disk and load only when relevant.

It ships in the Engineering Kit. It is wired to the DevOps & Deployment Pro (devops-engineer) and Technical Lead & System Architect (tech-lead) agents. It is wired to the /ci-pipeline: GitHub Actions CI/CD Pipeline Generator and /release: Release Notes & Changelog Generator commands. That graph is the point: the skill is the standard, the agent is the role, the command is the trigger.

When to use it

  • Use Claude Code Plugin Scaffold when the work is specifically about plugin.json, marketplace.json, and one command + one skill, wired correctly.
  • Load it before a long session that will touch this surface more than once. A one-line edit does not need the full playbook.
  • Use it on production SaaS work (multi-tenant apps, paid features, anything that will be reviewed) rather than a throwaway prototype.

When not to use it

  • Do not treat the skill as a replacement for a slash command. Skills teach. Commands run a pipeline.
  • Do not paste the whole SKILL.md into chat. If Cursor is not loading it, fix the description or invoke the matching command.
  • Do not use it as a generic 'write better code' rule. Scope is this domain only.

Example workflow

  1. Install the Engineering Kit so .cursor/skills/claude-code-plugin-scaffold lands in the repo.
  2. Open a new Cursor agent chat pointed at the files this skill governs.
  3. Ask the DevOps & Deployment Pro (devops-engineer) to read the skill, or run /ci-pipeline: GitHub Actions CI/CD Pipeline Generator.
  4. Review the first artifact against the practices below. If it violates one, stop and correct the file. Do not prompt 'just finish it'.
  5. Commit the skill-guided files with the rest of the slice so the next session inherits the same standard.

Example usage

Example prompt: "Read .cursor/skills/claude-code-plugin-scaffold and apply it to this change. Do not invent extra conventions."

Or trigger the pipeline: /ci-pipeline: GitHub Actions CI/CD Pipeline Generator. That command is written to load this skill.

Check the output against: Write plugin.json with name, version (semver), and description before anything else exists

Example output

  • The skill itself does not write a single output file. It changes what the agent is allowed to produce in code, schema, and tests.
  • When you run /ci-pipeline: GitHub Actions CI/CD Pipeline Generator, expect repo files plus notes under docs/, not a chat-only answer.

Best practices

  • Write plugin.json with name, version (semver), and description before anything else exists
  • Bundle one slash command under commands/ and one skill under skills/ so the plugin does something on first install
  • Register the plugin in marketplace.json with a unique name — collisions with reserved or existing marketplace names fail silently on install
  • Test locally by pointing Claude Code at the plugin directory before publishing to a marketplace repo
  • Bump plugin.json's version on every change; stale versions are the most common reason a published update doesn't show up

Common mistakes

  • Ignoring "Write plugin.json with name, version (semver), and description before anything else exists" and hoping a later prompt will clean it up.
  • Copying the skill into .cursor/rules as always-on. That burns context and fights Cursor's load-on-match design.
  • Running two overlapping skills that contradict each other in the same turn.
  • Letting the agent skip tests or types because 'the skill is about architecture'.

Frequently asked questions

  • What is the Claude Code Plugin Scaffold Cursor skill?
    Teaches the agent the exact shape of a Claude Code plugin: the plugin.json manifest, a marketplace.json entry for distribution, and how commands/ and skills/ bundle together so `/plugin install` or a local marketplace add picks it up without errors. It lives at .cursor/skills/claude-code-plugin-scaffold after you install the Engineering Kit.
  • When should I use claude-code-plugin-scaffold instead of a Cursor rule?
    Use a rule for always-on or glob-scoped constraints. Use this skill for the full playbook that should load only when the task matches.
  • Which agents read claude-code-plugin-scaffold?
    DevOps & Deployment Pro (devops-engineer); Technical Lead & System Architect (tech-lead). Those roles are told to open this file before they edit.
  • Which commands use claude-code-plugin-scaffold?
    /ci-pipeline: GitHub Actions CI/CD Pipeline Generator; /release: Release Notes & Changelog Generator.
  • Does this skill work outside AgenticKit?
    Yes. A SKILL.md in .cursor/skills/claude-code-plugin-scaffold is a normal Cursor skill. AgenticKit is the packaged version plus the agent and command graph.

Add claude-code-plugin-scaffold and the other 48 Cursor skills

AgenticKit installs 61 skills, 46 agents, and 47 slash commands into .cursor/. One license, lifetime updates.