repo-setup SKILL.md skillA
repo-setup from bluestep-systems/bluestep-ai is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bluestep-systems/bluestep-ai/repo-setup@git:20261103.5c82982Pins git:20261103.5c82982 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bluestep-systems/bluestep-ai
- Path
plugins/core-tools/skills/repo-setup/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261103.5c82982, committed Nov 3, 2026
- Size
- 8,591 bytes
- Repository stars
- 3
- License
- none declared
Audit or create a repo's agent setup — the AGENTS.md rules file, the CLAUDE.md bridge, and a skill per repo workflow. Use this whenever the question is whether a repo's rules still match what it actually builds, tests and deploys: a command CI runs that the rules never mention, a command in the rules that no longer exists, rules that live only in CLAUDE.md so Cursor and Codex see nothing, or a repo with no AGENTS.md at all. Reach for it after a repo gains a test framework, a CI check, a deploy…
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
# /repo-setup — audit or write this repo's agent setup ## When to run this - **The repo has no `AGENTS.md`.** Nothing tells an agent how to build, test or ship it, so every session works it out again from scratch. - **The repo has one, and you want to know if it is still true.** Run `--check`. Drift is normal and invisible: CI gains a step, a script gets renamed, and the rules file says what used to be right. - **The repo just gained something** — a test framework, a CI check, a deploy path, a package in a monorepo. `--check` names what the setup does not mention yet. Shared rules can only say what is true of every repo. The build command, the test command and the release path are true of *this* one, so they have to live in a file the repo keeps. ## Two modes | | Writes | Use it for | | --- | --- | --- | | `/repo-setup` | Creates missing files. **Never touches a file that exists** — there is no `--force`. | A repo with no setup, or one that has gained something the setup lacks. | | `/repo-setup --check` | Nothing at all. | Finding out whether the setup still matches the repo. This is the mode you will use most. | …
Read the whole file at its exact version.
How to install
mdr add bluestep-systems/bluestep-ai/repo-setup@sha256:c107171f3cc16fb4The line at the top of this page pins the label git:20261103.5c82982, 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_5nzju7vyccv2ns6j)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 3, 2026.
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 (8591 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
bluestep-systems/bluestep-ai · 3 stars · license none declared · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5nzju7vyccv2ns6j GET https://markdownregistry.com/api/v1/resolve?ref=bluestep-systems/bluestep-ai/repo-setup GET https://markdownregistry.com/api/v1/blob/c107171f3cc16fb4780cdd195252b6ae2557ae328d80eca7e4c22ab74a673fac
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 bluestep-systems/bluestep-ai
Every file in bluestep-systems/bluestep-ai