Distribution
Owns where plugin and marketplace content comes from and how it is fetched, under src/contexts/distribution/ — marketplace registration, catalog parsing, and the ports/adapters that reach git and HTTP. Use when adding a new marketplace source kind, a catalog parser for a foreign format, or a fetch/cache/trust-store adapter. Do NOT use for what a tool does with fetched content — use `tools` or `translate`. Do NOT use for recording what got installed on a project — use `framework`.
Install
/plugin marketplace add ai-driven-dev/frameworkThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add ai-driven-dev/framework --skill distributiongit clone --depth 1 https://github.com/ai-driven-dev/framework.git /tmp/framework
mkdir -p ~/.claude/skills
cp -r /tmp/framework/cli/.claude/skills/distribution ~/.claude/skills/distributionPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Distribution `distribution` is a leaf: it depends on `kernel` only, and knows no tool and no manifest. It answers exactly one question — where does content come from, and how is it fetched — for whoever asks. `framework` is the only context that reaches it (`framework → distribution`); a plugin's own content and how it gets translated are someone else's job once it has arrived here. ## What goes in | Concept | Location | |---|---| | A marketplace registration (name, source, scope, staleness) | `domain/marketplace.ts`, `domain/marketplace-source-mode.ts` | | A cached catalog fetch | `domain/ports/marketplace-cache.ts` | | The plugin catalog shape | `domain/catalog.ts` (the Claude-shaped parser lives here too) | | A reader for a non-Claude catalog shape | `domain/catalog-parsers/` | | A port this context's callers hold | `domain/ports/` — registry, cache, trust-store, catalog-repository, fetcher, raw-catalog-fetcher | | Add / list / refresh / register / resolve / fetch a marketplace source | `application/` | | The concrete adapter behind one of the six ports | `infrastructure/` | ## How - This context is a leaf by construction: it must never gain an edge to `tools`, `translate`, or `framework` — `tests/architecture/context-graph.arch.test.ts` enforces the chain (`framework → distribution`, plus everything to `kernel`) and fails the build the moment a new edge appears. If a change seems to need one, the orchestration belongs to the caller
Details
- Skill name
distribution- Repository
- ai-driven-dev/framework
- Path
cli/.claude/skills/distribution/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Distribution skill do?
Owns where plugin and marketplace content comes from and how it is fetched, under src/contexts/distribution/ — marketplace registration, catalog parsing, and the ports/adapters that reach git and HTTP. Use when adding a new marketplace source kind, a catalog parser for a foreign format, or a fetch/cache/trust-store adapter. Do NOT use for what a tool does with fetched content — use `tools` or `translate`. Do NOT use for recording what got installed on a project — use `framework`.
How do I install the Distribution skill?
Claude Code plugin: /plugin marketplace add ai-driven-dev/framework. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Distribution popular?
It lives in ai-driven-dev/framework, which has 564 GitHub stars and 65 forks.
Related skills
00 Async Dev
564ai-driven-dev/framework
Drive the async-dev pipeline from one entry point, whether setup, run, or review. Use when the user wants to install async dev, run a ready issue, or address PR review comments, or on a webhook trigger. Not for plain status checks.
00 Init
564ai-driven-dev/framework
Turn AIDD measurement on for a project after explicit consent, stop it, choose to be named on your own measurement, or delete what was measured. Use when the user wants to start or stop measuring what their work consumes, add or remove their name, or forget measured data. Not for answering what a period consumed.
00 Onboard
564ai-driven-dev/framework
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Knowledge Layers
593haowjy/creative-writing-skills
Use when deciding where knowledge goes or reading/writing durable docs: AGENTS.md and .context/ beside what they describe, the KB, and work directories.
Creative Writing Muse
593haowjy/creative-writing-skills
Turn on to work with a creative partner who talks through your story, plans and drafts it in your voice, critiques and revises it, and keeps the project's memory, in one conversation.
LLM Writing
593haowjy/creative-writing-skills
Load before you write a commit message, PR body, changelog entry, issue, report to the user, doc, README, AGENTS.md or .context/ page, KB page, or prompt: choose plain words, write for the reader's context, and strip default LLM phrasing.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.