configure SKILL.md skillA
configure from choiyounggi/dev-loop is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add choiyounggi/dev-loop/configure@git:20261103.dc08261Pins git:20261103.dc08261 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- choiyounggi/dev-loop
- Path
skills/configure/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261103.dc08261, committed Nov 3, 2026
- First version recorded
- Jul 12, 2026
- Size
- 4,685 bytes
- Repository stars
- 6
- License
- MIT
Set up dev-loop's capability-role tool profile — map `knowledge` (your domain wiki / MCP), `verify` (your project's test/build/lint/typecheck/QA command), `explore` (code search), `tacit` (past incidents), and `design` (Figma/visual spec) to the actual tools this environment has, then write ~/.claude/dev-loop/tools.json (global) or <repo>/.dev-loop/tools.json (per-repo). Use when asked to "configure dev-loop", "set up tools", "map my wiki/test command", or "/dev-loop:configure".
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
# configure — set up the dev-loop tool profile
dev-loop runs fully generic with **no** config (every role falls back to the
model's own behavior). Configuring the roles makes the loop use *your* real tools:
your domain wiki for facts, your actual test command for verification, etc. The
bundled best-practice `wiki/` (used by `wiki-plan`) needs no config — the
`knowledge` role is for a separate *external/domain* wiki.
The project's own `wiki-local/` layer (read by `wiki-plan` and `loop-implement`
when it exists) also needs no config; it is not the `knowledge` role.
> Note: the plan step is fixed to `wiki-plan` and is NOT configurable. There is no
> `plan` role.
## Steps
1. **Show the current profile.** Run and report what is already set vs. default:
```sh
sh "${CLAUDE_PLUGIN_ROOT}/scripts/resolve-tools.sh" --summary
```
2. **Decide scope.**
- **Global** (all your projects): `~/.claude/dev-loop/tools.json`
- **Per-repo** (committed, team-shared; overrides global per role/field):
`<repo>/.dev-loop/tools.json`
Ask the user which, if unclear. (Legacy `~/.claude/loop-orchestrator/tools.json`
…Read the whole file at its exact version.
How to install
mdr add choiyounggi/dev-loop/configure@sha256:6c7e9deebcc74648The line at the top of this page pins the label git:20261103.dc08261, 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_jm4lep77qv4m5mk6)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jul 12, 2026 and Nov 3, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261103.dc08261 latest | 2026-11-03 | dc08261 | 4,685 B | A | view · diff |
| git:20261015.6678cc8 | 2026-10-15 | 6678cc8 | 4,681 B | A | view · diff |
| git:20261006.87b3431 | 2026-10-06 | 87b3431 | 4,292 B | A | view · diff |
| git:20260917.5afddde | 2026-09-17 | 5afddde | 4,219 B | A | view · diff |
| git:20260712.0af9b6d | 2026-07-12 | 0af9b6d | 4,069 B | A | view · diff |
| git:20260712.218462c | 2026-07-12 | 218462c | 4,021 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 (4685 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
choiyounggi/dev-loop · 6 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jm4lep77qv4m5mk6 GET https://markdownregistry.com/api/v1/resolve?ref=choiyounggi/dev-loop/configure GET https://markdownregistry.com/api/v1/blob/6c7e9deebcc746484fd5731bddaa08102d561440131499255f7cb285d95111da
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 choiyounggi/dev-loop
Every file in choiyounggi/dev-loop