setup SKILL.md skillA
setup from p2p2sp/p2p2.claude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add p2p2sp/p2p2.claude/setup@git:20261005.f70d443Pins git:20261005.f70d443 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- p2p2sp/p2p2.claude
- Path
viber/skills/setup/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261005.f70d443, committed Oct 5, 2026
- First version recorded
- Sep 28, 2026
- Size
- 3,442 bytes
- Repository stars
- 8
- License
- MIT
Prepares a project for viber - seeds .claude/viber.yml, .gitignore and the recommended .claude/settings.json permissions (asking whether to merge into or reset an existing one that differs from them), checks the gh CLI is installed, checks whether CLAUDE.md names the build and test commands, and opens the usage guide in the browser.
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
# setup
```!
"${CLAUDE_SKILL_DIR}/scripts/bootstrap.sh"
```
The lines above are the result. They are idempotent and self-verifying: report them as they stand, never re-check them.
The settings file is the one choice. On `settings.json: present`, ask with `AskUserQuestion` (a prose question ends the turn and the script's pre-approval with it) whether to:
- merge - fill in what is missing: the template's value wins a conflict, lists only gain entries, a template entry in `permissions.ask` leaves the host's `permissions.deny`, a key the template lacks is never touched.
- reset - replace the file with the template; the old one is kept in `.temp/viber/setup/`.
On `settings.json: absent` ask nothing and run the merge form, which creates the file.
On `settings.json: matches the template` ask nothing and run neither form: that preload line is the settings line.
Otherwise run the chosen form once. Its line is carried into the close literally, never re-verified, never retried; a non-zero exit is trusted the same way:
```
"${CLAUDE_PLUGIN_ROOT}/skills/setup/scripts/merge-settings.sh" "${CLAUDE_PLUGIN_ROOT}/skills/setup/templates/settings.json"
…Read the whole file at its exact version.
How to install
mdr add p2p2sp/p2p2.claude/setup@sha256:838262e6a063c7d6The line at the top of this page pins the label git:20261005.f70d443, 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_r4ipe2pziphujb26)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 28, 2026 and Oct 5, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.f70d443 latest | 2026-10-05 | f70d443 | 3,442 B | A | view · diff |
| git:20261001.fb7213b | 2026-10-01 | fb7213b | 3,425 B | A | view · diff |
| git:20260930.c3e75e3 | 2026-09-30 | c3e75e3 | 3,232 B | A | view · diff |
| git:20260928.5bbeffb | 2026-09-28 | 5bbeffb | 3,086 B | A | view · diff |
| git:20260928.797dfd4 | 2026-09-28 | 797dfd4 | 2,060 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 (3442 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
p2p2sp/p2p2.claude · 8 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_r4ipe2pziphujb26 GET https://markdownregistry.com/api/v1/resolve?ref=p2p2sp/p2p2.claude/setup GET https://markdownregistry.com/api/v1/blob/838262e6a063c7d6e6e83668e1cda623c3bc6ed3f89c5a3654290a47207a04c9
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.
More from p2p2sp/p2p2.claude
Every file in p2p2sp/p2p2.claude