AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

coding-agent-rollout

Use when rolling Claude Code out to a team or reviewing a rollout: shared or managed settings, MCP and plugin approval, layered CLAUDE.md, adoption. Lints settings with settings_linter.py, inventories MCP servers and plugins, and audits CLAUDE.md layering.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--coding-agent-rollout at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 5

SKILL.md

Claude Code Team Rollout

Portability: 4 stdlib scripts, no network, no LLM calls. They read config and counts; they change nothing.

One engineer's Claude Code setup is a preference. A team's is a policy. Settings merge from five scopes, permissions.allow arrays combine across files, and deny beats ask beats allow wherever it is written, so nobody can read the effective policy from a single file. This skill makes it readable, then checks it.

Workflow

# 1 - Guardrails: lint shared, local and managed settings together.
python scripts/settings_linter.py --repo . --managed /etc/claude-code/managed-settings.json
# 2 - Inventory: every MCP server, plugin and marketplace, against your approved list.
python scripts/mcp_plugin_inventory.py --repo . --allowlist approved.json
# 3 - Instructions: what CLAUDE.md actually loads, layer by layer.
python scripts/claude_md_layering_audit.py --repo .
# 4 - Adoption: each member runs this locally and shares only the JSON counts.
python scripts/adoption_tracker.py --member alice --output json > alice.json
python scripts/adoption_tracker.py --merge *.json --seats 12 --weeks-since-launch 6

Start from assets/managed-settings.example.json: bypass mode disabled, secrets denied, risky commands on ask, managed hooks only, an MCP and marketplace allowlist. Ship it through MDM before the first seat; policy added after habits form becomes a negotiation.

What blocks (exit 4)

  • Blanket shell allows (Bash, Bash(*)) and pre-approved destructive commands (force push, rm -rf, sudo, pipe-to-shell, publish, infra apply).
  • A literal credential in a shared settings env block, a committed .mcp.json, or a committed CLAUDE.md.
  • .claude/settings.local.json committed to git.
  • An MCP server, plugin or marketplace missing from the approved list.

Warnings cover dead rules (an allow that a deny shadows, mcp__* in allow), enableAllProjectMcpServers, unpinned npx servers, plain-http remotes, network-calling hooks, broken or too-deep @imports, duplicated or contradictory instructions, and resident CLAUDE.md size.

Hard rules

  1. Policy lives in managed settings. Project files cannot enable bypass mode or telemetry, and a team guardrail in a file anyone can edit is a suggestion.
  2. Approve MCP servers by name, URL or command, never by enableAllProjectMcpServers.
  3. Pin what runs. Unpinned npx/uvx servers and unpinned marketplaces change under you.
  4. Never collect transcripts. Share the adoption JSON (counts only); transcripts are plaintext and can hold secrets.
  5. Report findings, not verdicts on people. Adoption is a team metric; inactive seats are a rollout question, not a performance one.
  6. Settings keys change fast. An unknown key is INFO; check the settings reference before calling it a typo.

Scripts

| Script | Role | Exit codes | |---|---|---| | scripts/settings_linter.py | S1-S13 across shared, local, user and managed scopes | 0 · 2 warn · 3 bad input · 4 blocker | | scripts/mcp_plugin_inventory.py | One table of servers, plugins, marketplaces; M1-M6 | 0 · 2 · 3 · 4 | | scripts/claude_md_layering_audit.py | Resident vs on-demand layers, imports (4 hops), L1-L11 | 0 · 2 · 3 · 4 | | scripts/adoption_tracker.py | Member counts; team stage PILOT / SPREADING / EMBEDDED / STALLED | 0 · 2 stalled · 3 |

All support --sample and --output json.

References and assets