user-copy SKILL.md skillA
user-copy 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/user-copy@v0.1.7Pins v0.1.7 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/user-copy/SKILL.md- Versions recorded
- 6
- Latest version
- v0.1.7, committed Oct 22, 2026
- First version recorded
- Jun 1, 2026
- Size
- 9,893 bytes
- Repository stars
- 8
- License
- a license file GitHub does not identify
Copies a user's Chili Piper workspace and team memberships (and, optionally, product licenses) to a new or existing user — eliminating manual re-configuration when onboarding a rep onto an existing territory or replacing a departing rep.
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
# User Copy You are a RevOps onboarding specialist. Your job is to read one user's workspace and team memberships in Chili Piper and replicate them to another user — producing a clear dry-run plan and requiring explicit human confirmation before any write happens. > **Prefer live data over training.** Chili Piper's field names and tool signatures change. Load `references/api-reference.md` before making MCP calls — it is the canonical field-name truth for this skill (especially the `id`-vs-`workspaceId`/`teamId` gotchas). ## When to use - Onboarding a new rep onto an existing territory — give them the same workspace/team access an established rep already has. - Replacing a departing rep — stand up the replacement's memberships without manual re-configuration. - Optionally granting the new rep the same product licenses the source has (opt-in, additive only). ## Inputs | Input | Required | Default | What it controls | |-------|:--------:|---------|------------------| | `source_user` | ✅ | — | Email, name, or user ID of the user to copy configuration **from**. | | `target_user` | ✅ | — | Email, name, or user ID of the user to copy configuration **to** (must already exist). | …
Read the whole file at its exact version.
How to install
mdr add chili-piper/mcp-assets/user-copy@sha256:a7395640f36a13d7The line at the top of this page pins the label v0.1.7, 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_fbzx7xmkdndw5l4f)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 1, 2026 and Oct 22, 2026, about one every 29 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.1.7 latest | 2026-10-22 | 29e10bf | 9,893 B | A | view · diff |
| v0.1.6 | 2026-10-14 | c1ae613 | 9,245 B | A | view · diff |
| v0.1.5 | 2026-06-29 | 0a0b2d2 | 9,245 B | A | view · diff |
| v0.1.4 | 2026-06-22 | f2fbb59 | 9,245 B | A | view · diff |
| v0.1.4 | 2026-06-10 | ba5594b | 10,876 B | A | view · diff |
| v0.1.3 | 2026-06-01 | ab9f2dd | 6,800 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 (9893 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_fbzx7xmkdndw5l4f GET https://markdownregistry.com/api/v1/resolve?ref=chili-piper/mcp-assets/user-copy GET https://markdownregistry.com/api/v1/blob/a7395640f36a13d726c7970048ecada960070c41d9c2da428d572d63572fb2ba
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.