agents-bootstrap
Generate a project-specific AGENTS.md from a user goal, then confirm before overwriting.
Best use case
agents-bootstrap is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate a project-specific AGENTS.md from a user goal, then confirm before overwriting.
Teams using agents-bootstrap should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agents-bootstrap/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agents-bootstrap Compares
| Feature / Agent | agents-bootstrap | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate a project-specific AGENTS.md from a user goal, then confirm before overwriting.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# AGENTS Bootstrap Generate a concise, project-specific `AGENTS.md` tailored to the user's goal. ## Core rules - Use `assets/agents-template.md` as the base structure. - No placeholders in the final `AGENTS.md`. - Keep the file concise and enforceable. - Draft in chat first; ask for confirmation before writing. - Before overwriting, create a backup: `AGENTS.md.bak.<timestamp>`. - If MCP tools are in scope and `docs/mcp-tools.md` is missing or stale, instruct to use the `mcp-tools-catalog` skill before finalizing `AGENTS.md`. ## Required inputs Collect these if not provided: - Role and objective - Non-negotiable constraints - Stack and data sources - Testing toolchain (unit/integration/e2e commands, frameworks, MCP tools) - Whether Issue CSV workflow is in scope Ask at most 2 clarification questions, then proceed with stated assumptions. If the task continues across turns, re-invoke this skill to keep the rules active. ## Output requirements The final `AGENTS.md` must include (when applicable): - Role & objective - Constraints - Tech & data sources - Project testing strategy (tools + commands) - E2E loop (plan → issues → implement → test → review → commit → regression) - Plan & issue generation reference (use `plan` skill) - Issue CSV policy (if Issue CSV workflow is in scope) - Tool usage (MCP usage guidance) - Testing policy reference (`docs/testing-policy.md`) - Safety and output style ## Write flow 1) Draft the tailored `AGENTS.md` in chat. 2) Ask: "Reply CONFIRM to overwrite AGENTS.md." 3) On confirmation: - Backup current file to `AGENTS.md.bak.<timestamp>` if it exists. - Write the new `AGENTS.md`. Do not edit other files.
Related Skills
manage-agents
Create, modify, and manage Claude Code subagents with specialized expertise. Use when you need to "work with agents", "create an agent", "modify an agent", "set up a specialist", "I need an agent for [task]", or "agent to handle [domain]". Covers agent file format, YAML frontmatter, system prompts, tool restrictions, MCP integration, model selection, and testing.
langchain-agents
Expert guidance for building LangChain agents with proper tool binding, memory, and configuration. Use when creating agents, configuring models, or setting up tool integrations in LangConfig.
kramme:agents-md
This skill should be used when the user asks to "update AGENTS.md", "add to AGENTS.md", "maintain agent docs", or needs to add guidelines to agent instructions. Guides discovery of local skills and enforces structured, keyword-based documentation style.
git-commit-for-ai-agents
Commit changes to a git repository. Use whenever a git commit is to be executed.
dispatching-parallel-agents
Use when facing 3+ independent failures that can be investigated without shared state or dependencies. Dispatches multiple Claude agents to investigate and fix independent problems concurrently.
custom-sub-agents
Guidance for creating and organizing custom sub-agents in local repos, including folder conventions, per-agent structure, and AGENTS.md indexing. Use when asked where to store sub-agents or how to document them.
custom-agents
GitHub Custom Agent File Format
creating-agents
Create and review agent definition files (agents.md) that give AI coding agents a clear persona, project knowledge, executable commands, code style examples, and explicit boundaries. Use when a user asks to create an agent, define an agent persona, write an agents.md file, set up a custom Copilot agent, review an existing agent definition, or improve agent quality. Covers the six core areas: commands, testing, project structure, code style, git workflow, and boundaries.
create-agents-md
Create or rewrite AGENTS.md files for Open Mercato packages and modules. Use this skill when adding a new package, creating a new module, or when an existing AGENTS.md needs to be created or refactored. Ensures prescriptive tone, MUST rules, checklists, and consistent structure across all agent guidelines.
building-agents
Expert at creating and modifying Claude Code agents (subagents). Auto-invokes when the user wants to create, update, modify, enhance, validate, or standardize agents, or when modifying agent YAML frontmatter fields (especially 'model', 'tools', 'description'), needs help designing agent architecture, or wants to understand agent capabilities. Also auto-invokes proactively when Claude is about to write agent files (*/agents/*.md), create modular agent architectures, or implement tasks that involve creating agent components.
bootstrap
Wake up, orient, and warm the context with foundational MOOLLM knowledge
audit-agents-md
Audit AGENTS.md files for token efficiency, completeness, scope hygiene, and actionability. Also considers skills and Cursor rules for redundancy. Use when the user wants to review, optimize, or restructure project agent instructions.