install-architect-playbook-locally

Copies architect-playbook skill folders into the current project's .claude/skills directory.

3|5|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill install-architect-playbook-locally-bensheridanedwards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: install-architect-playbook-locally
Source: https://github.com/BenSheridanEdwards/ArchitectPlaybook/tree/main/install-architect-playbook-locally
Command: npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill install-architect-playbook-locally-bensheridanedwards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams using the architect-playbook audit skills need those slash commands available inside a specific project without affecting other projects on the machine. Manually copying each skill folder into .claude/skills/ is error-prone and tedious, especially when the repository-quality-score skill depends on a set of audit catalogs that must be installed together. ## Core Features & Use Cases - Project-scoped installation: Copies every skill folder containing a SKILL.md from the playbook root into the current working directory's .claude/skills/ folder, leaving other projects and the global ~/.claude/skills/ untouched. - Selective install with dependency closure: Supports --include and --exclude filters, and automatically adds every audit catalog required by repository-quality-score from its score-policy.json, failing early on conflicting excludes. - Safe, idempotent updates: Skips destinations that are newer than the source unless --force is set, supports --dry-run to preview the plan, detects stub skills, and refuses to write outside the project's .claude/skills/ directory. - Use Case: After cloning architect-playbook, run the command inside your application repository to install all audit slash commands locally, then open a new Claude Code session in that project to use them. ## Quick Start Run /install-architect-playbook-locally from inside your project to copy all architect-playbook skills into this project's .claude/skills directory.

Frequently Asked Questions about install-architect-playbook-locally

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install Claude Code skills into a single project only?

Run /install-architect-playbook-locally from the project's working directory. It copies every skill folder from the playbook root into ./.claude/skills/, so the slash commands work only in that project and leave other projects untouched.

How do I install only one specific skill from the playbook?

Use the --include=name flag, which is repeatable, to install only the named skills. You can also use --exclude=name to skip specific skills while installing the rest.

Does this skill affect the global ~/.claude/skills directory?

No. It writes only to the current working directory's .claude/skills/ folder and refuses to write anywhere else. For machine-wide installation, use the separate /install-architect-playbook-globally skill instead.

What happens if I install repository-quality-score without its audit skills?

The installer reads repository-quality-score/score-policy.json and automatically adds every audit named in audits[].name to the install plan. If an --exclude flag conflicts with a required audit, it fails before copying anything.

Is it safe to re-run the local install command?

Yes. Re-running is idempotent: destinations newer than the source are skipped unless --force is set, and it never deletes destination skills that no longer exist in the source. Use --dry-run to preview the plan first.