Tons of Skills

Intent Solutions is a Claude Partner Network Select Services Partner.

A model-agnostic agent-skills platform. The canonical layer is harness-free by construction; Claude Code is currently the verified-native harness. Other harnesses remain engineering candidates until their native-path integration is verified; source research alone is never presented as public support.

Version semantics: the release badge is this marketplace’s display version. npm packages, including the ccpi CLI and publishable plugins, retain their own package versions; they are intentionally not expected to equal the display version. The version-surface checker governs the display surfaces without rewriting package semver.

Install

Inside Claude Code, one command installs the whole marketplace:

/plugin marketplace add jeremylongshore/claude-code-plugins

Or use the CLI:

pnpm add -g @intentsolutionsio/ccpi
ccpi install devops-automation-pack

Development prerequisites

Repository-level development and verification require Node.js >=22.12.0 and pnpm >=9.15.9. The tested Node version is recorded in .node-version. Run node scripts/check-node-version.mjs before installing dependencies when working on a fresh checkout. The independently consumable packages retain their own lower runtime declarations where applicable; see 000-docs/814-DR-STND-node-runtime-contract.md for the compatibility matrix.

Browse the marketplace · Explore plugins · Download bundles

Scale, labeled

Every number below names the cohort it counts and the command that reproduces it — an unlabeled count is how a corpus ends up with five contradictory answers to “how many skills.”

📦 Live npm Downloads

Across 379 published packages in the claude-code-plugins namespace. Updated daily by GitHub Actions.

“Established” excludes packages first published within the last 30 days, so a bulk-publish event doesn’t dominate the headline.

Top 10 by last 30 days:

Last refreshed 2026-10-30T06:22:52.519Z.

Ways in

Five real questions, five doors — each resolves to a live, generated surface, never a hand-maintained list:

• By category — the table below, regenerated from the catalog on every sync.
• By plugin — tonsofskills.com/explore, the full browsable catalog.
• By skill — tonsofskills.com/skills, searchable across the whole corpus.
• By job to be done — tonsofskills.com/cowork, curated bundles as one-click downloads.
• By certification tier — the Certification section below, rendered from the live report.

Browse by category

The 19 categories below link into the live marketplace. Plugin counts are the catalog-entry cohort — regenerated from marketplace.extended.json by this generator; the catalog itself lives on tonsofskills.com, never in this file (§ 6A of the platform blueprint).

What the classes mean

Four artifact classes live in this repository, distinguished on sight and never blurred — provenance is a truth requirement here, not a UX nicety:

Certification

Not yet certified. The certification program (tiers T0–T4 with retained, hash-matched evidence) is a later epic of the platform blueprint; until its report exists, no artifact on this surface claims a tier. This line is rendered from the absence of certification-report.json — honestly, not cosmetically.

Contribute

Start with the contribution guide, then the intake and review standards every submission passes through:

• Contribution requirements — including the AI-assistance disclosure expectation.
• Skill submission intake standard — the tiered document matrix new plugins ship with.
• External-PR review standard — how maintainers triage and what gets a submission merged.

Governance

• STANDARDS.md — the public spec posture and the canonical-documents index (one owner per fact class).
• The platform master blueprint — CI gates, release, docs governance, and this README’s own landing contract.
• GOVERNANCE.md · SECURITY.md · LICENSE

Provenance

External plugins are hosted mirror-by-default: the contributor’s repository stays the source of truth, every mirrored source is pinned in a content lockfile, and upstream credit — author, license, resolved commit — is recorded in the mirror itself. Improvements flow by upstreaming to the author’s repository, never by silently editing the mirror. The full decision record is the external-sync model.

License

MIT for the repository scaffolding and first-party tooling; each plugin carries its own license in its manifest, and mirrored plugins keep their upstream license verbatim.