Run any Skill in Manus with one click

bootstrap-agent-config

Stars15

Forks0

UpdatedMay 25, 2026 at 02:17

Generate a high-quality project CLAUDE.md and AGENTS.md by inspecting the current repository. Use when a repo has no agent config, when onboarding a new project, or when the user asks to "set up Claude/Codex for this repo" or "write a CLAUDE.md". Detects languages, build/test commands, and structure, then drafts config grounded in what's actually there.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

dshakes

dshakes/compass

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	bootstrap-agent-config
description	Generate a high-quality project CLAUDE.md and AGENTS.md by inspecting the current repository. Use when a repo has no agent config, when onboarding a new project, or when the user asks to "set up Claude/Codex for this repo" or "write a CLAUDE.md". Detects languages, build/test commands, and structure, then drafts config grounded in what's actually there.
argument-hint	[optional path, default: current repo]
allowed-tools	Read, Write, Edit, Grep, Glob, Bash

Bootstrap agent config for a repository

Produce a CLAUDE.md and a symlinked/parallel AGENTS.md that are grounded in the real repo, not generic boilerplate. A good config is the single highest-ROI thing for agent productivity in a codebase — it pays for itself on the first task.

Steps

Detect the stack. Run the helper to get a fast inventory:
```
bash "${CLAUDE_SKILL_DIR}/detect-stack.sh" .
```
It reports languages, package managers, build/test/lint commands, monorepo layout, and whether ADRs/CI exist.
Verify, don't trust. Confirm the detected build/test commands actually exist (read the Makefile / package.json / justfile). Read 2–3 representative source files to learn the real conventions (error handling, test style, naming).
Find the invariants. The most valuable part of a CLAUDE.md is the load-bearing rules — the things that cause incidents if violated. Look for them in: existing ADRs, ARCHITECTURE.md, SECURITY.md, README "gotchas", and patterns the code enforces (e.g. tenant scoping, a trust boundary, a generated file you must not hand-edit). Ask the user if the architecture isn't legible.
Draft CLAUDE.md using the structure in ${CLAUDE_SKILL_DIR}/../../../templates/CLAUDE.md.tmpl as a skeleton. Fill every placeholder with real, verified content. Sections that matter most:
- One-sentence "what this is"
- Languages and exact build/test/lint commands (copy-pasteable)
- Repo layout (only the parts an agent needs)
- Load-bearing invariants — the "what NOT to do" list
- How to run/verify locally Cut anything you can't ground in the actual repo. Short and true beats long and aspirational.
Make AGENTS.md track it. Most non-Claude tools (Codex, etc.) read AGENTS.md. Either symlink it (ln -s CLAUDE.md AGENTS.md) so there's one source of truth, or write a thin AGENTS.md that says "see CLAUDE.md". Prefer the symlink unless the repo already has a divergent AGENTS.md.
Report the files written and the top 3 invariants you encoded, so the user can correct anything you inferred.

Quality bar

Every command in the file runs. Every path exists. Every invariant is real.
No "best practices" filler that isn't specific to this repo.
If you had to guess at an invariant, mark it (verify) so the user checks it.

More from this repository

same repository

using-compass

dshakes/compass

Use at the START of any task in a compass-enabled repo, or whenever you're unsure which capability fits. Indexes compass's guardrails, red-team, router, commands, subagents, and skills so you reach for the right tool instead of working ad-hoc. Read this before hand-writing config, reviewing a diff, adding a dependency, picking a model, or running untrusted code.

2026-07-2715

pr-shepherd

dshakes/compass

Take every open PR end-to-end — diagnose failing checks, classify them (real defect vs mechanical vs environmental), fix the mechanical ones on the PR branch, re-verify, and stop at the merge gate. Use on demand ("handle the open PRs") or on an interval via /loop (e.g. "/loop 15m /pr-shepherd"). Merges only when the human has granted merge authority in the current session; otherwise reports ready-to-merge.

2026-07-2615

morning-triage

dshakes/compass

Discovery for an autonomous loop — find this turn's work instead of being handed it. Reads what changed since the last run (failed CI, new issues, merged commits), judges what's actually worth acting on, writes findings to a durable state file, and hands each off to the SDLC loop with a stop-condition. Use as the first move of a scheduled loop, or by hand to plan a session. Read-only on code; never edits, opens PRs, or merges.

2026-06-2915

systematic-debugging

dshakes/compass

Use when something is broken — a failing test, panic, stack trace, error log, or wrong behavior whose cause isn't obvious. Reproduce it, form a hypothesis, PROVE the cause before changing code, then make the minimal root-cause fix and guard it with a test. For deep cases, hand off to the debugger subagent.

2026-06-0515

verification-before-completion

dshakes/compass

Use before claiming ANY task done, fix verified, check passing, or PR ready. Establish how the change is checked and actually run it — tests, typecheck, lint, the local gate, or the app itself — and observe it pass. Never report "should work" or pass along a subagent's unproven claim.

2026-06-0515

harden

dshakes/compass

Run the toolkit's security commands in order to surface secrets, MCP supply-chain issues, install drift, release provenance gaps, and untrusted-code risks before shipping. Use before opening a PR, after adding a dependency, or whenever the security posture needs a fresh check.

2026-06-0115

name	bootstrap-agent-config
description	Generate a high-quality project CLAUDE.md and AGENTS.md by inspecting the current repository. Use when a repo has no agent config, when onboarding a new project, or when the user asks to "set up Claude/Codex for this repo" or "write a CLAUDE.md". Detects languages, build/test commands, and structure, then drafts config grounded in what's actually there.
argument-hint	[optional path, default: current repo]
allowed-tools	Read, Write, Edit, Grep, Glob, Bash

Bootstrap agent config for a repository

Steps

Detect the stack. Run the helper to get a fast inventory:
```
bash "${CLAUDE_SKILL_DIR}/detect-stack.sh" .
```
It reports languages, package managers, build/test/lint commands, monorepo layout, and whether ADRs/CI exist.
Verify, don't trust. Confirm the detected build/test commands actually exist (read the Makefile / package.json / justfile). Read 2–3 representative source files to learn the real conventions (error handling, test style, naming).
Find the invariants. The most valuable part of a CLAUDE.md is the load-bearing rules — the things that cause incidents if violated. Look for them in: existing ADRs, ARCHITECTURE.md, SECURITY.md, README "gotchas", and patterns the code enforces (e.g. tenant scoping, a trust boundary, a generated file you must not hand-edit). Ask the user if the architecture isn't legible.
Draft CLAUDE.md using the structure in ${CLAUDE_SKILL_DIR}/../../../templates/CLAUDE.md.tmpl as a skeleton. Fill every placeholder with real, verified content. Sections that matter most:
- One-sentence "what this is"
- Languages and exact build/test/lint commands (copy-pasteable)
- Repo layout (only the parts an agent needs)
- Load-bearing invariants — the "what NOT to do" list
- How to run/verify locally Cut anything you can't ground in the actual repo. Short and true beats long and aspirational.
Make AGENTS.md track it. Most non-Claude tools (Codex, etc.) read AGENTS.md. Either symlink it (ln -s CLAUDE.md AGENTS.md) so there's one source of truth, or write a thin AGENTS.md that says "see CLAUDE.md". Prefer the symlink unless the repo already has a divergent AGENTS.md.
Report the files written and the top 3 invariants you encoded, so the user can correct anything you inferred.

Quality bar

Every command in the file runs. Every path exists. Every invariant is real.
No "best practices" filler that isn't specific to this repo.
If you had to guess at an invariant, mark it (verify) so the user checks it.