coding-agent-rollout

Use when rolling Claude Code out to a team or organization, or auditing a rollout already under way — writing or reviewing shared and managed settings.json permissions, deciding which MCP servers, plugins and marketplaces to approve, cleaning up layered CLAUDE.md files, or measuring whether the team actually uses it. Lints settings across scopes, inventories every MCP server and plugin against an approved list, resolves CLAUDE.md layers and imports, and turns local session data into privacy-safe adoption counts.

跳到安装查看文件

仓库: alirezarezvani/claude-skills
最近来源活动: 2026年10月22日 07:50
检测到的 SKILL.md 语言: 英语
星标: 28,933
Forks: 4,016

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 AI 助手安装

复制这段 Prompt，发给你正在使用的 AI 助手。

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/alirezarezvani/claude-skills/tree/main/engineering/coding-agent-rollout/skills/coding-agent-rollout.

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/alirezarezvani/claude-skills --skill coding-agent-rollout

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

11 个文件

SKILL.md

来源说明 · 只读预览

name: coding-agent-rollout
description: Use when rolling Claude Code out to a team or organization, or auditing a rollout already under way — writing or reviewing shared and managed settings.json permissions, deciding which MCP servers, plugins and marketplaces to approve, cleaning up layered CLAUDE.md files, or measuring whether the team actually uses it. Lints settings across scopes, inventories every MCP server and plugin against an approved list, resolves CLAUDE.md layers and imports, and turns local session data into privacy-safe adoption counts.
argument-hint: [repo path | managed-settings.json | 'measure adoption']
license: MIT
metadata: {"version":"1.0.0","build_pattern":"Four-phase rollout (guardrails, inventory, instructions, adoption) with 4 deterministic stdlib scripts and blocking exit codes; every settings key and path verified against code.claude.com/docs","distinct_from":"claude-coach (coaches one person's usage); skill-doctor (grades sessions to improve installed skills); security-guidance (a hook that warns on risky code patterns); prompt-governance (prompts in production apps, not the coding agent's configuration)"}

# 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 ```bash # 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`](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 - [`references/settings_and_permissions.md`](references/settings_and_permissions.md) — scopes, precedence, rule syntax, managed-only keys (7 sources) - [`references/mcp_and_plugin_governance.md`](references/mcp_and_plugin_governance.md) — MCP scopes, allowlists, marketplaces, pinning (6 sources) - [`references/memory_and_adoption.md`](references/memory_and_adoption.md) — CLAUDE.md layering, transcripts, OpenTelemetry, adoption stages (6 sources) - [`assets/managed-settings.example.json`](assets/managed-settings.example.json) — baseline team policy - [`assets/approved-components.example.json`](assets/approved-components.example.json) — allowlist format for step 2 - [`assets/rollout_plan.md`](assets/rollout_plan.md) — four-phase plan with exit criteria per phase

在 GitHub 查看

返回搜索返回安装

commercial-policy

Use when designing or revising a company's commercial policy — the rules of engagement governing discounts off list price, approver thresholds, exception flows, and the deal framework that Deal Desk and AEs operate under. Covers discount matrix design (ARR band x term length x payment terms x strategic value), commercial policy design, exception policy, discount governance, approval thresholds, deal framework structure, and policy linting (contradictions, gaps, cliff edges, gaming surfaces). For Head of Commercial, Head of Deal Desk, VP Sales, or RevOps at the policy-design moment — NOT per-deal application (that is deal-desk) and NOT pricing model selection (that is pricing-strategist).

2026-10-26

agent-harness

Turn any domain folder of skills into a bounded agentic loop: compile a goal into a verifiable task plan, execute tasks with the domain's own tools, verify every task with machine-run checks, retry with caps, escalate to a human when budgets exhaust, and refuse to close until everything is verified or explicitly waived. Use when you want an agent or subagent to pick up a goal and drive it to a verified close across one of this repo's 20 domains ('run this goal through the engineering harness', 'set up an agentic loop for marketing work', 'make the finance domain self-verifying'). NOT for authoring Claude Code Workflow-tool .js scripts (workflow-builder), N-agent tournaments on one task (agenthub), single-file metric optimization (autoresearch-agent), or discovering published loop recipes (loop-library).

2026-10-26

feature-flags-architect

Use when adding, retiring, or auditing feature flags. Triggers on "add a flag", "ship behind a flag", "rollout plan", "kill switch", "stale flags", "flag debt", "LaunchDarkly", "GrowthBook", "Statsig", "Unleash", "Flipt", or any progressive-delivery question. Ships flag debt scanner, rollout planner, and kill-switch auditor (all stdlib Python), 4 references on flag taxonomy + provider trade-offs + rollout strategies + lifecycle, plus a /flag-cleanup slash command.

2026-10-26

查看这个仓库的全部 Skills

coding-agent-rollout

来源信息

安装方式

用 AI 助手安装

检查来源文件

同仓库更多 Skills

用 AI 助手安装

同仓库更多 Skills