Skills

Third-party skills

Of the 36 baseline skills, seven are shared globals. Six of those are vendored from external sources with their upstream licenses preserved; one (code-structure) is written for this baseline. Users adopt additional third-party skills by placing them in .claude/skills/ following the same vendoring discipline.

§ I

Why vendor instead of install

Skills are markdown plus optional scripts. They are read by Claude Code at session start. Vendoring means committing the skill files to your repository so the capability travels with the project.

The alternative (a global install) is fragile: a teammate clones the repo and the skill is missing.

The baseline ships skills as committed files. Third-party skills follow the same pattern. Place the skill folder under .claude/skills/<skill-name>/, preserve the original license file, and reference the original source in a top-of-file comment.

§ II

The seven shared globals

Per CLAUDE.md Appendix B, seven baseline skills are shared globals. One (code-structure) is written for this baseline. Six are vendored from external sources, each preserving its upstream license and behavior; the local vendoring change is limited to an attribution NOTICE file and a reference in the constitution's skill index.

One shared global (code-structure) is written by Friedbot Studio for this baseline. The other six are vendored from external sources, each preserving its upstream license and attribution. Sources span three publishers and two licenses.

Skill	Source	License	Role
claude-automation-recommender	Anthropic `claude-code-setup` plugin	Apache 2.0	Analyzes a codebase and recommends Claude Code automations; used by `/init-project`.
code-structure	Friedbot Studio (this project)	Repo license	Mandatory on every code-generation step. Enforces top-down composition and consistent abstraction layers.
humanizer	blader/humanizer	MIT	Removes signs of AI-generated writing; invoked unconditionally by `prose` as its final pass.
documentation	Anthropic `claude-code-setup` plugin	Apache 2.0	Reference-doc register (API docs, runbooks, architecture). Conditional invocation from `prose`.
technical-tutorials	jonathimer/devmarketing-skills	MIT	Tutorial / quickstart / step-by-step register. Conditional invocation from `prose`.
copywriting	coreyhaines31/marketingskills	MIT	Persuasive register (landing copy, value props, CTAs). Conditional invocation from `prose`.
impeccable	pbakaus/impeccable	Apache 2.0	Frontend design and iteration. Mandatorily invoked by `design-ui`.

Each vendored shared global ships with its LICENSE and NOTICE files at .claude/skills/<name>/. The NOTICE file records the upstream URL, the vendor date, and any local changes made during vendoring.

§ III

How to vendor a third-party skill

Six steps. The discipline keeps the audit-baseline drift check accurate and the upstream license honored.

Identify the skill source. Confirm the license permits vendoring (most permissive licenses do; copyleft licenses typically do, with conditions).
Copy the skill folder to .claude/skills/<skill-name>/. Preserve the directory structure.
Copy the license file alongside, named LICENSE or matching the original filename.
Add a short attribution header to the skill's main file referencing the source URL and license.
Do not edit the skill's behavior. If a fork is needed, fork upstream and vendor the fork; do not edit in place.
Reference the skill in your project's CLAUDE.md Appendix B (the skill index) so the audit-baseline drift check knows it should be present.

Vendoring is for skills, not for hooks or subagents.

Hooks and subagents have constitutional implications. Adopting a third-party hook or subagent requires an explicit amendment to seed.md. Skills are safer to vendor because they are conversational tools the user can ignore; hooks are structural and run regardless.

§ IV

Tracking updates

A vendored skill is a snapshot. To pick up upstream improvements, replace the vendored copy from upstream and re-run /audit-baseline to confirm no drift in the parts that interact with the rest of the constitution.

Keep a short VENDORED.md alongside skills you have vendored, recording the upstream URL and the commit you vendored from.