How do I install the 200 Agents Md skill?

Run npx skillmds add majiayu000/200-agents-md in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is 200 Agents Md safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 200 Agents Md?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 200 Agents Md free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published 200 Agents Md?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

200 Agents Md by majiayu000 — Agent Skill

Name: 200 Agents Md
Rating: 4.2 (5 reviews)
Author: majiayu000

200 Agents Md

Use when you need to generate an AGENTS.md file for a Java repository — covering project conventions, tech stack, file structure, commands, Git workflow, and contributor boundaries — through a modular, step-based interactive process that adapts to your specific project needs. This should trigger for requests such as Create AGENTS.md; Update AGENTS.md file; Add agent instructions. Part of cursor-rules-java project

majiayu000 604a315 2 files · 3.8 KB Updated Sep 9, 2026 567 repo stars

File contents

AGENTS.md Generator for Java repositories

Generate a comprehensive AGENTS.md file for Java repositories through a modular, step-based interactive process that covers role definition, tech stack, file structure, commands, Git workflow, and contributor boundaries. This is an interactive SKILL.

What is covered in this Skill?

AGENTS.md generation for Java repositories of any complexity
Role and expertise definition for AI agents and contributors
Tech stack documentation: language, build tool, frameworks, pipelines
File structure mapping with read/write boundaries
Command catalogue for build/test/deploy/run workflows
Git workflow conventions: branching strategy, commit message format
Contributor boundaries using ✅ Always do / ⚠️ Ask first / 🚫 Never do formatting

Constraints

No Maven validation is required before generating AGENTS.md. Review the project structure and existing documentation before starting to provide accurate answers during Step 1.

BEFORE STARTING: Review the project structure and existing documentation to provide accurate answers during Step 1
BEFORE APPLYING: Read the reference for detailed good/bad examples, constraints, and safeguards for each AGENTS.md generation pattern
EDGE CASE: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands
EDGE CASE: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance
EDGE CASE: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off

When to use this skill

Create AGENTS.md
Update AGENTS.md file
Add agent instructions

Workflow

Review repository context before drafting

Inspect project structure and existing documentation to prepare accurate responses for the AGENTS.md discovery phase.

Read AGENTS generation reference

Read references/200-agents-md.md and follow its generation patterns and safeguards.

Run interactive requirements capture

Gather role, tech stack, commands, workflow, and boundaries in a modular step-based conversation.

Generate AGENTS.md artifact

Create AGENTS.md with ✅ Always do / ⚠️ Ask first / 🚫 Never do boundaries and repository-specific conventions.

Reference

For detailed guidance, examples, and constraints, see references/200-agents-md.md.

---name: 200-agents-mddescription: Use when you need to generate an AGENTS.md file for a Java repository — covering project conventions, tech stack, file structure, commands, Git workflow, and contributor boundaries — through a modular, step-based interactive process that adapts to your specific project needs. This should trigger for requests such as Create AGENTS.md; Update AGENTS.md file; Add agent instructions. Part of cursor-rules-java projectlicense: Apache-2.0---# AGENTS.md Generator for Java repositories Generate a comprehensive AGENTS.md file for Java repositories through a modular, step-based interactive process that covers role definition, tech stack, file structure, commands, Git workflow, and contributor boundaries. **This is an interactive SKILL**. **What is covered in this Skill?** - AGENTS.md generation for Java repositories of any complexity - Role and expertise definition for AI agents and contributors - Tech stack documentation: language, build tool, frameworks, pipelines - File structure mapping with read/write boundaries - Command catalogue for build/test/deploy/run workflows - Git workflow conventions: branching strategy, commit message format - Contributor boundaries using ✅ Always do / ⚠️ Ask first / 🚫 Never do formatting ## Constraints No Maven validation is required before generating AGENTS.md. Review the project structure and existing documentation before starting to provide accurate answers during Step 1. - **BEFORE STARTING**: Review the project structure and existing documentation to provide accurate answers during Step 1 - **BEFORE APPLYING**: Read the reference for detailed good/bad examples, constraints, and safeguards for each AGENTS.md generation pattern - **EDGE CASE**: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands - **EDGE CASE**: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance - **EDGE CASE**: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off ## When to use this skill - Create AGENTS.md - Update AGENTS.md file - Add agent instructions ## Workflow 1. **Review repository context before drafting** Inspect project structure and existing documentation to prepare accurate responses for the AGENTS.md discovery phase. 2. **Read AGENTS generation reference** Read `references/200-agents-md.md` and follow its generation patterns and safeguards. 3. **Run interactive requirements capture** Gather role, tech stack, commands, workflow, and boundaries in a modular step-based conversation. 4. **Generate AGENTS.md artifact** Create AGENTS.md with ✅ Always do / ⚠️ Ask first / 🚫 Never do boundaries and repository-specific conventions. ## Reference For detailed guidance, examples, and constraints, see [references/200-agents-md.md](references/200-agents-md.md).

Frequently asked questions