linehaulai-claude-marketplace
AGENTS.md4 starsChanged 51 days agoMITView on GitHub
This document provides guidelines for AI agents working on the linehaul.ai Claude Marketplace repository. Before submitting changes, perform the following verifications:
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- skill-gap-analyzerSkill
The file
Show its rules and text
We split this AGENTS.md into the rules it gives an agent
20 rules. About 0 are common, 7 are distinctive, and 13 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
13
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Plugin Directory: All plugin code is located in .claude-plugin/.
- Distinctive: line 14
When creating or modifying plugins, adhere to the following structure based on the plugin type:
- Very specific: line 17
Must have a .claude-plugin/plugin.json manifest.
- Very specific: line 19
Should have their own README.md, INSTALL.md, and PLUGIN_OVERVIEW.md.
- Very specific: line 22
Must contain a SKILL.md file.
- Very specific: line 24
Do not strictly require a plugin.json if they are pure skill definitions, but it is good practice if they are to be installed independently.
- Distinctive: line 27
Must be valid JSON.
- Very specific: line 28
Must contain name, version, description, and author fields.
- Distinctive: line 29
Ensure version numbers follow semantic versioning.
- Very specific: line 32
Registration: If adding a new plugin, you must register it in .claude-plugin/marketplace.json.
- Very specific: line 34
Metadata: Ensure the name and description in marketplace.json match the plugin's purpose.
- Distinctive: line 39
Update README.md if high-level changes are made (e.g., adding a new key plugin).
- Distinctive: line 40
Update individual plugin documentation when modifying plugin behavior.
- Very specific: line 41
Use AUTO-MANAGED blocks in CLAUDE.md if present (or respect existing ones) to keep documentation synchronized.
- Very specific: line 44
Directories: Use kebab-case for plugin directory names (e.g., my-plugin-name).
- Distinctive: line 52
Before submitting changes, perform the following verifications:
- Very specific: line 54
JSON Validity: Ensure marketplace.json and any plugin.json files are valid JSON.
- Very specific: line 55
Path Validity: Verify that any paths referenced in marketplace.json actually exist in the file system.
- Distinctive: line 56
Markdown Formatting: Ensure all markdown files are well-formatted and links are valid.
- Very specific: line 57
Consistency: Check that the plugin name in the directory matches the name in plugin.json and marketplace.json.
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Instructions for Agents
This document provides guidelines for AI agents working on the linehaul.ai Claude Marketplace repository.
Project Structure
- Root Directory: Contains project-level documentation (
README.md,CLAUDE.md,LICENSE) and configuration. - Plugin Directory: All plugin code is located in
.claude-plugin/. - Registry:
marketplace.jsonin.claude-plugin/is the central registry for all plugins.
Development Guidelines
1. Plugin Structure
When creating or modifying plugins, adhere to the following structure based on the plugin type:
- Full Plugins (e.g.,
golang-orchestrator):- Must have a
.claude-plugin/plugin.jsonmanifest. - typically contain
commands/,skills/,agents/, anddocs/directories. - Should have their own
README.md,INSTALL.md, andPLUGIN_OVERVIEW.md.
- Must have a
- Skill Plugins (e.g.,
sequential-thinking):- Must contain a
SKILL.mdfile. - May contain a
references/directory for specialized documentation. - Do not strictly require a
plugin.jsonif they are pure skill definitions, but it is good practice if they are to be installed independently.
- Must contain a
- Manifest (
plugin.json):- Must be valid JSON.
- Must contain
name,version,description, andauthorfields. - Ensure version numbers follow semantic versioning.
2. Marketplace Registry
- Registration: If adding a new plugin, you must register it in
.claude-plugin/marketplace.json. - Paths: The
sourcepath inmarketplace.jsonmust be relative to the.claude-plugindirectory (e.g.,./.claude-plugin/my-new-plugin). - Metadata: Ensure the name and description in
marketplace.jsonmatch the plugin's purpose.
3. Documentation
- Source of Truth: Maintain
CLAUDE.mdas the single source of truth for architecture and detailed descriptions. - Updates:
- Update
README.mdif high-level changes are made (e.g., adding a new key plugin). - Update individual plugin documentation when modifying plugin behavior.
- Use
AUTO-MANAGEDblocks inCLAUDE.mdif present (or respect existing ones) to keep documentation synchronized.
- Update
4. Naming Conventions
- Directories: Use
kebab-casefor plugin directory names (e.g.,my-plugin-name). - Files:
- Skill definitions:
SKILL.mdorskills/my-skill.md. - Slash commands:
commands/my-command.md. - Agents:
agents/my-expert.md.
- Skill definitions:
Verification Steps
Before submitting changes, perform the following verifications:
- JSON Validity: Ensure
marketplace.jsonand anyplugin.jsonfiles are valid JSON. - Path Validity: Verify that any paths referenced in
marketplace.jsonactually exist in the file system. - Markdown Formatting: Ensure all markdown files are well-formatted and links are valid.
- Consistency: Check that the plugin name in the directory matches the name in
plugin.jsonandmarketplace.json.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

