agent-integrator
Use this skill to create or update the root AGENTS.md file to register AgenticDev skills for AI agent discovery. Triggers include "register AgenticDev", "update AGENTS.md", "setup agent guide", or initializing a new project.
Best use case
agent-integrator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use this skill to create or update the root AGENTS.md file to register AgenticDev skills for AI agent discovery. Triggers include "register AgenticDev", "update AGENTS.md", "setup agent guide", or initializing a new project.
Teams using agent-integrator 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/agent-integrator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agent-integrator Compares
| Feature / Agent | agent-integrator | 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?
Use this skill to create or update the root AGENTS.md file to register AgenticDev skills for AI agent discovery. Triggers include "register AgenticDev", "update AGENTS.md", "setup agent guide", or initializing a new project.
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
# Agent Integrator Skill ## Purpose Idempotently create or update the AGENTS.md file in a project to register AgenticDev skills for discovery by AI agents. This skill ensures that any compatible AI agent working in the repository can discover and use the AgenticDev methodology and available skills. ## When to Use Use this skill in the following situations: - After running project-init to initialize AgenticDev in a new project - When installing AgenticDev skills in an existing project - After adding new skills to the `.claude/skills/` directory - Updating the agent guide with new workflow information - Ensuring AI agents can discover available AgenticDev capabilities ## Prerequisites - Project has `.claude/skills/` directory with AgenticDev skills installed - Write permissions to project root directory - Optional: Existing AGENTS.md file (script creates if missing) ## AGENTS.md Purpose The AGENTS.md file serves as a discovery mechanism for AI agents: - **Agent Discovery**: AI agents read this file to learn about available workflows - **Methodology Documentation**: Explains AgenticDev philosophy and core principles - **Skill Catalog**: Lists all available skills and their purposes - **Getting Started**: Provides entry point for new agents working in the project ## Workflow ### Step 1: Determine If Update Is Needed Check if AGENTS.md needs to be created or updated: ```bash # Check if file exists ls -la AGENTS.md # Check if AgenticDev section exists grep "SYNTHESIS_FLOW" AGENTS.md ``` ### Step 2: Run the Helper Script Execute the script to update AGENTS.md: ```bash # Use default location (AGENTS.md in project root) bash scripts/update-agents-file.sh # Or specify custom location bash scripts/update-agents-file.sh -f path/to/custom-agents.md ``` ### Step 3: Understand What the Script Does The helper script uses an idempotent update strategy: 1. **Creates file if missing**: - Uses `touch` to ensure target file exists - Safe to run even if file doesn't exist yet 2. **Checks for existing content**: - Looks for `<!-- SYNTHESIS_FLOW_START -->` marker - Determines if this is an update or initial creation 3. **Updates existing content**: - If markers found, replaces content between markers - Preserves any other content in the file - Uses awk to safely replace marked section 4. **Adds new content**: - If markers not found, appends AgenticDev guide to end of file - Adds both start and end markers for future updates 5. **Preserves other content**: - Only modifies content between markers - Safe to run multiple times (idempotent) - Won't overwrite other project documentation ### Step 4: Verify the Update Check that AGENTS.md was updated correctly: ```bash # View the file cat AGENTS.md # Verify markers are present grep -A 5 "SYNTHESIS_FLOW_START" AGENTS.md ``` ### Step 5: Commit the Changes If the update looks correct, commit to the repository: ```bash git add AGENTS.md git commit -m "docs: Update AGENTS.md with AgenticDev guide" git push ``` ## Error Handling ### Permission Denied **Symptom**: Script cannot write to AGENTS.md **Solution**: - Check file permissions: `ls -la AGENTS.md` - Ensure you have write access to project root - Run with appropriate permissions ### Marker Corruption **Symptom**: Content between markers is malformed **Solution**: - Manually edit AGENTS.md to fix markers - Ensure both `<!-- SYNTHESIS_FLOW_START -->` and `<!-- SYNTHESIS_FLOW_END -->` are present - Re-run script to regenerate content ### Custom File Path Issues **Symptom**: Script creates file in wrong location **Solution**: - Use `-f` flag with full path: `bash scripts/update-agents-file.sh -f /full/path/to/file.md` - Verify path exists: `mkdir -p /path/to/directory` - Check current working directory ## Notes - **Idempotent design**: Safe to run multiple times without side effects - **Preserves other content**: Only updates content between markers - **Marker-based**: Uses HTML comments as markers (invisible in rendered markdown) - **Default location**: AGENTS.md in project root (standard convention) - **Custom locations**: Use `-f` flag for alternative file paths - **Run after setup**: Typically run once after project-init, then rarely - **Update when skills change**: Re-run if new skills are added or removed - **AI agent discovery**: Helps agents understand available AgenticDev capabilities - **Version control**: Commit AGENTS.md so all contributors see the guide
Related Skills
beads-integrator
Merge Beads task branches into main/master safely (serialized), verify, push to remote, record merge SHAs back into tasks, and clean worktrees. Use when merging branches, integrating code to base branch, or finalizing reviewed task branches.
api-integrator
Integrate external REST and GraphQL APIs with proper authentication (Bearer, Basic, OAuth), error handling, retry logic, and JSON schema validation. Use when making API calls, database queries, or integrating external services like Stripe, Twilio, AWS. Achieves 10-30x cost savings through direct execution vs LLM-based calls. Triggers on "API call", "REST API", "GraphQL", "external service", "API integration", "HTTP request".
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
obsidian-daily
Manage Obsidian Daily Notes via obsidian-cli. Create and open daily notes, append entries (journals, logs, tasks, links), read past notes by date, and search vault content. Handles relative dates like "yesterday", "last Friday", "3 days ago".
obsidian-additions
Create supplementary materials attached to existing notes: experiments, meetings, reports, logs, conspectuses, practice sessions, annotations, AI outputs, links collections. Two-step process: (1) create aggregator space, (2) create concrete addition in base/additions/. INVOKE when user wants to attach any supplementary material to an existing note. Triggers: "addition", "create addition", "experiment", "meeting notes", "report", "conspectus", "log", "practice", "annotations", "links", "link collection", "аддишн", "конспект", "встреча", "отчёт", "эксперимент", "практика", "аннотации", "ссылки", "добавь к заметке".
observe
Query and manage Observe using the Observe CLI. Use when the user wants to run OPAL queries, list datasets, manage objects, or interact with their Observe tenant from the command line.
observability-review
AI agent that analyzes operational signals (metrics, logs, traces, alerts, SLO/SLI reports) from observability platforms (Prometheus, Datadog, New Relic, CloudWatch, Grafana, Elastic) and produces practical, risk-aware triage and recommendations. Use when reviewing system health, investigating performance issues, analyzing monitoring data, evaluating service reliability, or providing SRE analysis of operational metrics. Distinguishes between critical issues requiring action, items needing investigation, and informational observations requiring no action.
nvidia-nim
NVIDIA NIM inference microservices for deploying AI models with OpenAI-compatible APIs, self-hosted or cloud
numpy-string-ops
Vectorized string manipulation using the char module and modern string alternatives, including cleaning and search operations. Triggers: string operations, numpy.char, text cleaning, substring search.
nova-act-usability
AI-orchestrated usability testing using Amazon Nova Act. The agent generates personas, runs tests to collect raw data, interprets responses to determine goal achievement, and generates HTML reports. Tests real user workflows (booking, checkout, posting) with safety guardrails. Use when asked to "test website usability", "run usability test", "generate usability report", "evaluate user experience", "test checkout flow", "test booking process", or "analyze website UX".
notebook-writer
Create and document Jupyter notebooks for reproducible analyses
nomistakes
Error prevention and best practices enforcement for agent-assisted coding. Use when writing code to catch common mistakes, enforce patterns, prevent bugs, validate inputs, handle errors, follow coding standards, avoid anti-patterns, and ensure code quality through proactive checks and guardrails.