What are the three plugins included in cc-plugins?

The three plugins are: `claudecraft` (for creating, auditing, and publishing skills and plugins), `projects` (for auditing project standards compliance or scaffolding new projects from profiles), and `triage` (for turning a scope into a structured findings list and iterating through findings with approval).

How do I install cc-plugins into Claude Code?

Run `/plugin marketplace add bkudria/cc-plugins`, then `/plugin install @bkudria-cc-plugins`, then `/reload-plugins`. Replace ` ` with the specific plugin you want (claudecraft, projects, or triage).

How does the cc-plugins marketplace manifest stay up to date?

The manifest is auto-generated from each plugin's `plugin.json` file by a GitHub Actions workflow that runs on PRs and pushes, automatically regenerating and committing the manifest back to the branch if there's any drift.

What does the `projects` plugin do?

It audits an existing project against standards defined in a `project.yaml` file, or scaffolds a new project from declarative YAML profiles. It inspects the actual project rather than reading declarations, making it language- and tool-agnostic.

How does the `triage` plugin work?

It supports a two-step workflow: `/triage:assess` investigates a scope and produces a structured, numbered findings list, then `/triage:iterate` processes those findings one by one with explicit approval at each step.

Prompt Chain

Build and publish Claude Code plugins with guided workflows

Name: Cc Plugins
Availability: OnlineOnly
Author: github

Claude Code plugin marketplace bundling skill/plugin authoring, project-standards auditing, and assess-then-iterate triage.

Copy chain

Works with githubclaude

github

Own this? Claim it

Spark score

out of 100

Updated 2 months ago

Source checked Sep 17, 2026

Version 1.0.0

Add to Favorites

Why it matters

Developers hire this marketplace to extend Claude Code with reusable plugins that automate skill authoring, project standards compliance, and triage workflows-each plugin bundles discipline-specific skills with auto-triggering and slash commands.

Outcomes

What it gets done

Create, audit, and publish Claude Code skills and plugins using the claudecraft bundle

Audit project standards compliance or scaffold new projects from declarative YAML profiles

Assess a codebase to produce numbered findings and iterate through fixes one-by-one

Install marketplace plugins via slash commands and reload them into Claude Code

Install

Add it to your toolbox

Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/bkudria-cc-plugins | bash

After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.

Reports

Agent outcome reports

No reports yet

Overview

Cc Plugins

A Claude Code plugin marketplace bundling skill and plugin authoring tooling, project-standards auditing from declarative profiles, and an assess-then-iterate triage workflow. Use it to install ready-made Claude Code plugins for authoring skills/plugins, auditing or scaffolding a project against standards profiles, or triaging an open-ended scope.

What it does

A Claude Code plugin marketplace bundling three plugins: claudecraft, which bundles skillcraft (discipline and tooling for creating, auditing, improving, and updating skills), claude-code-evals (a reference manual for an eval pipeline), and plugincraft (discipline and tooling for creating, auditing, and publishing whole Claude Code plugins, including managing marketplace entries); projects, a single standards skill that audits an existing project against the standards its own project.yaml selects, or scaffolds a new project from those profiles - profiles are self-contained YAML files, and the model inspects the actual project rather than reading declarations, so it is language- and tool-agnostic; and triage, two skills supporting an assess-then-iterate workflow - assess investigates a scope and produces a structured, numbered findings list, and iterate processes those findings one by one with per-item approval, invoked via dedicated slash commands. The marketplace manifest itself is auto-generated from each plugin's own plugin.json, the source of truth for name and description, by a script that preserves hand-edited per-entry fields such as source, category, homepage, and keywords; a GitHub Actions workflow runs on PRs and pushes touching any plugin.json or the manifest, and auto-regenerates and commits the manifest back to the PR branch on drift.

When to use - and when NOT to

Use it to install any of the three plugins into Claude Code: claudecraft for creating, auditing, or publishing skills and plugins; projects for auditing a project's standards compliance or scaffolding a new project from declarative profiles, auto-triggering on phrases like "audit this project," "check compliance," or "new project"; and triage for turning an open-ended scope into a structured findings list and then working through those findings one at a time with explicit approval at each step.

Inputs and outputs

Input is a Claude Code plugin-install invocation for the desired plugin, plus, for projects, a project.yaml selecting which standards profiles apply. Output is the installed plugin's skills becoming available as slash commands - /triage:assess and /triage:iterate for the triage plugin, an audit report or a scaffolded project structure for projects, and skill or plugin-authoring tooling and references for claudecraft. Install:

/plugin marketplace add bkudria/cc-plugins
/plugin install <name>@bkudria-cc-plugins
/reload-plugins

Integrations

Distributed entirely through the Claude Code plugin marketplace mechanism, with its manifest auto-synced by a GitHub Actions workflow from each plugin's own plugin.json; claudecraft specifically documents a separate eval pipeline as a reference rather than shipping it itself. The repository is MIT licensed, and each plugin also carries its own license file.

Who it's for

Claude Code users who want ready-made plugins for authoring and publishing their own skills and plugins, enforcing project standards from declarative profiles, or running a structured assess-then-iterate review of an open-ended scope.

Source README

bkudria/cc-plugins

A Claude Code plugin marketplace by Benjamin Kudria.

What this is

A marketplace for Claude Code plugins. See the catalog below for current entries. Plugins live under plugins/; the marketplace manifest lives at .claude-plugin/marketplace.json.

Installation

In Claude Code:

/plugin marketplace add bkudria/cc-plugins
/plugin install <name>@bkudria-cc-plugins
/reload-plugins

Replace <name> with a plugin name from the catalog below. See per-plugin sections below for the exact commands.

Plugin catalog

Plugin	Description	README
`claudecraft`	Create, audit, and publish Claude Code skills and plugins. Bundles skillcraft (skill authoring discipline), claude-code-evals (eval pipeline reference), and plugincraft (plugin authoring + marketplace lifecycle).	plugins/claudecraft/README.md
`projects`	Audit a project's standards compliance or scaffold a new one, driven by declarative project.yaml profiles.	plugins/projects/README.md
`triage`	Assess a scope to produce findings, then address them one-by-one.	plugins/triage/README.md

claudecraft

/plugin install claudecraft@bkudria-cc-plugins

Bundles three skills:

skillcraft - discipline and tooling for creating, auditing, improving, and updating skills
claude-code-evals - reference manual for the scuttlerun / pincenez / craboodle eval pipeline
plugincraft - discipline and tooling for creating, auditing, and publishing whole Claude Code plugins; manages marketplace entries

See plugins/claudecraft/README.md for the full breakdown of how the three skills relate.

projects

/plugin install projects@bkudria-cc-plugins

One skill for project standards compliance:

standards - audit an existing project against the standards its project.yaml selects, or scaffold a new project from those profiles. Standards are self-contained YAML files under profiles/; the model is language- and tool-agnostic, inspecting the project itself rather than reading declarations.

Auto-triggers on "audit this project", "check compliance", "new project", and similar. See plugins/projects/README.md for the audit/scaffold workflows and the project.yaml schema.

triage

/plugin install triage@bkudria-cc-plugins

Two skills supporting an assess-then-iterate workflow:

assess - investigate a scope and produce a structured, numbered findings assessment
iterate - process the findings one-by-one with per-item approval

Invoke via the /triage:assess and /triage:iterate slash commands.

Repository layout

cc-plugins/
├── .claude-plugin/
│   └── marketplace.json          # marketplace manifest (auto-regenerated)
├── .github/
│   └── workflows/
│       └── marketplace-sync.yml  # CI auto-sync
└── plugins/
    ├── claudecraft/
    │   ├── .claude-plugin/plugin.json
    │   ├── README.md
    │   └── skills/
    │       ├── claude-code-evals/
    │       ├── plugincraft/
    │       └── skillcraft/
    ├── projects/
    │   ├── .claude-plugin/plugin.json
    │   ├── README.md
    │   └── skills/
    │       └── standards/
    └── triage/
        ├── .claude-plugin/plugin.json
        └── skills/
            ├── assess/
            └── iterate/

How the marketplace stays in sync

Each plugin's plugin.json is the source of truth for name and description. The script plugins/claudecraft/skills/plugincraft/scripts/marketplace-generate.sh regenerates .claude-plugin/marketplace.json from constituent plugin.json files, preserving hand-edited per-entry fields (source, category, homepage, keywords) and all top-level marketplace fields.

The .github/workflows/marketplace-sync.yml workflow runs on PRs and pushes to main that touch any plugin.json or marketplace.json. On drift it auto-regenerates and commits the result back to the PR branch. See plugins/claudecraft/skills/plugincraft/references/marketplace-spec.md for what the generator rewrites vs preserves.

FAQ

Common questions

Discussion