distro-router-configuration SKILL.md skillA
distro-router-configuration from chili-piper/mcp-assets is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chili-piper/mcp-assets/distro-router-configuration@v0.2.3Pins v0.2.3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chili-piper/mcp-assets
- Path
skills/distro-router-configuration/SKILL.md- Versions recorded
- 6
- Latest version
- v0.2.3, committed Oct 14, 2026
- First version recorded
- Jul 20, 2026
- Size
- 10,950 bytes
- Repository stars
- 8
- License
- a license file GitHub does not identify
Creates, updates, activates/deactivates, and deletes Chili Piper Distro (lead-routing) routers — full lifecycle with dry-run diffs, async status polling, overlay-aware updates, and delete safety gates. Use when a RevOps admin manages which distribution CRM records route to.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Distro Router Configuration You are a Chili Piper RevOps admin assistant. Manage Distro (lead-routing) routers — the configurations that decide which distribution a CRM record is routed to — through their full lifecycle: create, activate, update, deactivate, delete. Always plan first; write only after explicit confirmation. > **This is a destructive, write skill.** It defaults to `dry_run=true` and must never > mutate data before the human confirms the plan. See **Checkpoint** below. > **Lifecycle rules that surprise people:** a router **created via the API starts > `Inactive` and routes nothing** until `distro-router-activate` is called. Updates > require the `routing` object (400 `RouterRoutingRequired` without it) and apply it > as an **overlay**: routes are matched by `ruleId` and only their distribution + > actions change — app-only config on matched rows is preserved — but the **trigger > and `routingSteps` are replaced** from what you send (an empty/absent `routingSteps` > **clears** them). `name` and `description` have PATCH semantics: omitting either > preserves the existing value (CEH-11002, 2026-07-21). Never send a name-only or …
Read the whole file at its exact version.
How to install
mdr add chili-piper/mcp-assets/distro-router-configuration@sha256:12b1bb6509f55c6eThe line at the top of this page pins the label v0.2.3, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ce4nrcuafsnanrne)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jul 20, 2026 and Oct 14, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.2.3 latest | 2026-10-14 | c1ae613 | 10,950 B | A | view · diff |
| v0.2.2 | 2026-09-16 | f1f8e19 | 10,950 B | A | view · diff |
| v0.2.1 | 2026-09-04 | 3e48653 | 10,286 B | A | view · diff |
| v0.2.0 | 2026-07-30 | 7df21e1 | 10,020 B | A | view · diff |
| v0.1.1 | 2026-07-22 | bd6b952 | 8,707 B | A | view · diff |
| v0.1.0 | 2026-07-20 | c41e16c | 8,119 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10950 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
chili-piper/mcp-assets · 8 stars · license a license file GitHub does not identify · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ce4nrcuafsnanrne GET https://markdownregistry.com/api/v1/resolve?ref=chili-piper/mcp-assets/distro-router-configuration GET https://markdownregistry.com/api/v1/blob/12b1bb6509f55c6e67306474c77ec5431b987d2a23609507fcd2b9995a1964b0
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.