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. Part of the skills-for-java project

Quality

53%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/200-agents-md/SKILL.md

Quality

Discovery

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted description that clearly defines its purpose and when to use it. The specificity around AGENTS.md generation for Java repositories with detailed coverage areas is excellent. Minor improvement could be made by including more natural trigger terms users might actually say when needing this functionality.

Suggestions

Add natural trigger term variations like 'agent file', 'project documentation', 'contributor guide', or 'repository setup docs' to improve discoverability

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'generate an AGENTS.md file', 'covering project conventions, tech stack, file structure, commands, Git workflow, and contributor boundaries', and describes the process as 'modular, step-based interactive'.	3 / 3
Completeness	Clearly answers both what ('generate an AGENTS.md file covering project conventions, tech stack, file structure, commands, Git workflow, and contributor boundaries') and when ('Use when you need to generate an AGENTS.md file for a Java repository') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes relevant terms like 'AGENTS.md', 'Java repository', 'project conventions', 'tech stack', but misses common variations users might say like 'agent file', 'project documentation', 'onboarding doc', or 'contributor guide'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche targeting AGENTS.md files specifically for Java repositories with a defined interactive process. The combination of 'AGENTS.md' + 'Java' + 'skills-for-java project' creates clear distinctiveness unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

22%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill content functions more as a table of contents than actionable guidance. While it correctly identifies what AGENTS.md should cover and references detailed documentation, it provides no concrete steps, templates, or examples that would enable Claude to actually generate the file. The 'interactive SKILL' claim is unsupported by any defined interaction flow.

Suggestions

Add a concrete step-by-step workflow showing the interactive process (e.g., Step 1: Gather project info, Step 2: Define roles, etc.) with specific questions to ask at each step

Include a minimal AGENTS.md template or example output showing the expected format and structure

Add at least one concrete example of each section type (role definition, tech stack entry, contributor boundary) so Claude knows the exact output format

Define validation checkpoints - how does Claude verify the generated AGENTS.md is complete and accurate before presenting it?

Dimension	Reasoning	Score
Conciseness	The skill is relatively brief but includes some redundant phrasing (e.g., repeating 'modular, step-based interactive process' in both the title area and body). The bullet list of coverage areas is useful but could be tighter.	2 / 3
Actionability	The skill provides no concrete steps, commands, or examples for generating AGENTS.md. It describes what will be covered but doesn't show how to do it - no templates, no sample output, no executable guidance.	1 / 3
Workflow Clarity	Despite mentioning 'step-based interactive process,' no actual steps are defined. The workflow is entirely absent - there's no sequence, no checkpoints, and no validation steps for the generation process.	1 / 3
Progressive Disclosure	The skill appropriately references an external file for detailed guidance (references/200-agents-md.md), but the main content is too sparse to serve as a useful overview. The reference is one level deep, which is good.	2 / 3
	Total	6 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Commit: 7772a1b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.