Set up or check a BlueStep One component workspace on Claude Code — checks the machine (bluestep-tools and its platform token, Node 20+, git access to the BlueStep One git host, the Claude desktop app's built-in browser pane and a sign-in on the BlueStep One host), then writes what the folder lacks: .claude/bluestep-one.json (the BlueStep One host and git host, the components, the test-data prefix), AGENTS.md, the CLAUDE.md bridge and .claude/settings.json. Asks only for BlueStep One values.…
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
# /bluestep-one:setup — this machine and this folder, ready to build components
**Decide what you can, ask only what is the user's.** A missing file that conflicts with nothing is
written and reported. A key that already holds a different value is asked about, never changed
silently. Something only a person can do (install a program, type a credential, ask for access) is
handed over as the exact command or click, and the run goes on with everything else. Never ask for
a credential in chat and never write one into a file. Never commit and never stage. Never overwrite
an existing file.
`--check` runs step 1 and reports what step 2 would write, writing nothing.
## Step 1 — the machine
Each check is read-only. Report each as ok / missing, with the fix for each missing one.
1. **bluestep-tools.** Its skills are in this session (`b6p-setup`, `bluestep-reference`). This
plugin declares it as a dependency, so it is normally installed with it; if it is missing or
fails to load, name the install line from this plugin's README and stop: the build's GraphQL
reference and the platform token come from it.
…
The line at the top of this page pins the label git:20261105.de929a8, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_gvg24m4cjxcvgkve
GET https://markdownregistry.com/api/v1/resolve?ref=bluestep-systems/bluestep-ai/setup
GET https://markdownregistry.com/api/v1/blob/abdb7c42977dd1fa290f336015d3c917ed72c9fd1a810acf89d50270472fdbbf
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.
bluestep-systems/bluestep-ai · .claude/skills/quick-task/SKILL.md · Short workflow for small tasks and bug fixes that don't warrant a full 3-phase spec. Use for clearly-scoped changes and…
bluestep-systems/bluestep-ai · .claude/skills/release-email/SKILL.md · Draft and queue a BlueStep-branded release-update email across three products (the bluestep-tools plugin, the b6p CLI…
bluestep-systems/bluestep-ai · .claude/skills/spec-create/SKILL.md · Start a new spec-driven feature. Creates requirements.md, then design.md, then tasks.md with explicit user approval…
bluestep-systems/bluestep-ai · .claude/skills/spec-execute/SKILL.md · Execute one task from a feature spec. By default delegates implementation to the spec-task-implementer subagent…
bluestep-systems/bluestep-ai · .claude/skills/spec-status/SKILL.md · Show progress of all feature specs in `.claude/specs/`. Use when the user wants a summary of what's in flight.
bluestep-systems/bluestep-ai · plugins/bluestep-one/skills/reference/SKILL.md · On-demand reference for building BlueStep One custom components — the type files and a component repo's setup, the…
bluestep-systems/bluestep-ai · plugins/bluestep-tools/skills/b6p-audit/SKILL.md · Compare a local component's state against what lives on the BlueStep platform, listing files that differ. Use when the…
bluestep-systems/bluestep-ai · plugins/bluestep-tools/skills/b6p-pull/SKILL.md · Pull a B6P component from the BlueStep platform into the local workspace using its DAV URL, and scaffold…
bluestep-systems/bluestep-ai · plugins/bluestep-tools/skills/b6p-push/SKILL.md · Publish a BlueStep (B6P) component's local changes to the platform with the b6p CLI — make it live, deploy it, upload…
bluestep-systems/bluestep-ai · plugins/bluestep-tools/skills/b6p-setup/SKILL.md · Set up, check or bring up to date the BlueStep (B6P) tooling for this machine and this folder in one run — the b6p CLI…
garrytan/gbrain · plugin/skills/setup/SKILL.md · Add keyless GBrain memory to an existing agent, or connect a hosted brain while preserving identity and configuration
garrytan/gbrain · skills/setup/SKILL.md · Add keyless GBrain memory to an existing agent, or connect a hosted brain while preserving identity and configuration
nanocoai/nanoclaw · .claude/skills/setup/SKILL.md · Run initial NanoClaw setup. Use when user wants to install NanoClaw, configure it, or go through first-time setup…
tencent/teamai-cli · skill-data/setup/SKILL.md · TeamAI day 0 and repo lifecycle: create a team repo as admin, join an existing team as a member, manage members, roles…
fcakyon/claude-codex-settings · plugins/overleaf-skills/skills/setup/SKILL.md · This skill should be used when user asks to "set up overleaf", "configure overleaf cookie", "overleaf auth failed"…
fcakyon/claude-codex-settings · plugins/github-dev/skills/setup/SKILL.md · This skill should be used when the user asks "how to setup GitHub CLI", "configure gh", "gh auth not working", "GitHub…
fcakyon/claude-codex-settings · plugins/paper-search-tools/skills/setup/SKILL.md · This skill should be used when the user asks to "set up paper search", reports "paper-search command not found", wants…
