install-architect-playbook-globally

Copies architect-playbook skill folders into ~/.claude/skills/ for machine-wide slash command availability.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Installing Claude Code skills project-by-project is repetitive when you audit many codebases. This Skill copies every architect-playbook skill into your home directory's ~/.claude/skills/ folder once, making all audit slash commands available in every Claude Code session on the machine. ## Core Features & Use Cases - Machine-wide installation: Copies every skill folder containing a SKILL.md into ~/.claude/skills/ with cp -R, excluding the installer skills themselves. - Overwrite protection: Lists existing destination skills, asks for confirmation before overwriting, and never touches skills the playbook does not own (such as graphify). - Dependency closure: When repository-quality-score is selected, reads its score-policy.json and automatically includes every audit named in the policy, refusing to install an incomplete scorer. - Use Case: You run security, performance, and architecture audits across a dozen client repositories. Run the installer once with --dry-run to preview the plan, then install globally so every new Claude Code chat in any project has the full audit suite. ## Quick Start Ask Claude to run /install-architect-playbook-globally --dry-run to preview which skills will be copied into ~/.claude/skills/ before confirming the installation.

Frequently Asked Questions about install-architect-playbook-globally

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

FAQPage Schema
How do I install Claude Code skills globally for all projects?

Run /install-architect-playbook-globally to copy every architect-playbook skill folder into ~/.claude/skills/. After installation, open a new Claude Code chat in any project and the slash commands are available.

What is the difference between global and local skill installation?

Global installation writes to ~/.claude/skills/ so skills work in every session on the machine, while local installation keeps skills inside a project for version pinning. Choose global when you audit many codebases and want one canonical version.

Will the installer overwrite my existing skills in ~/.claude/skills/?

It asks for confirmation before overwriting any existing skill and never touches skills the playbook does not own. Ownership is detected by matching the destination SKILL.md name field against the playbook source list; unmanaged skills like graphify are preserved.

Can I preview the installation before copying any files?

Yes, run the skill with --dry-run to print the full installation plan without copying anything. You can also use --include and --exclude to limit which named skills are installed.

Why does installing repository-quality-score add other skills automatically?

The scorer reads score-policy.json and depends on every audit listed in its audits array. The installer resolves this dependency closure and adds those audits to the plan, failing with a conflict message if you explicitly exclude a required audit.