agentleFS
freightCognitionfreightCognition/linehaulai-claude-marketplace/AGENTS.md

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.

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
  1. Very specific:

    Plugin Directory: All plugin code is located in .claude-plugin/.

    line 8
  2. Distinctive:

    When creating or modifying plugins, adhere to the following structure based on the plugin type:

    line 14
  3. Very specific:

    Must have a .claude-plugin/plugin.json manifest.

    line 17
  4. Very specific:

    Should have their own README.md, INSTALL.md, and PLUGIN_OVERVIEW.md.

    line 19
  5. Very specific:

    Must contain a SKILL.md file.

    line 22
  6. Very specific:

    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.

    line 24
  7. Distinctive:

    Must be valid JSON.

    line 27
  8. Very specific:

    Must contain name, version, description, and author fields.

    line 28
  9. Distinctive:

    Ensure version numbers follow semantic versioning.

    line 29
  10. Very specific:

    Registration: If adding a new plugin, you must register it in .claude-plugin/marketplace.json.

    line 32
  11. Very specific:

    Metadata: Ensure the name and description in marketplace.json match the plugin's purpose.

    line 34
  12. Distinctive:

    Update README.md if high-level changes are made (e.g., adding a new key plugin).

    line 39
  13. Distinctive:

    Update individual plugin documentation when modifying plugin behavior.

    line 40
  14. Very specific:

    Use AUTO-MANAGED blocks in CLAUDE.md if present (or respect existing ones) to keep documentation synchronized.

    line 41
  15. Very specific:

    Directories: Use kebab-case for plugin directory names (e.g., my-plugin-name).

    line 44
  16. Distinctive:

    Before submitting changes, perform the following verifications:

    line 52
  17. Very specific:

    JSON Validity: Ensure marketplace.json and any plugin.json files are valid JSON.

    line 54
  18. Very specific:

    Path Validity: Verify that any paths referenced in marketplace.json actually exist in the file system.

    line 55
  19. Distinctive:

    Markdown Formatting: Ensure all markdown files are well-formatted and links are valid.

    line 56
  20. Very specific:

    Consistency: Check that the plugin name in the directory matches the name in plugin.json and marketplace.json.

    line 57

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

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.json in .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.json manifest.
    • typically contain commands/, skills/, agents/, and docs/ directories.
    • Should have their own README.md, INSTALL.md, and PLUGIN_OVERVIEW.md.
  • Skill Plugins (e.g., sequential-thinking):
    • Must contain a SKILL.md file.
    • May contain a references/ directory for specialized documentation.
    • 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.
  • Manifest (plugin.json):
    • Must be valid JSON.
    • Must contain name, version, description, and author fields.
    • 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 source path in marketplace.json must be relative to the .claude-plugin directory (e.g., ./.claude-plugin/my-new-plugin).
  • Metadata: Ensure the name and description in marketplace.json match the plugin's purpose.

3. Documentation

  • Source of Truth: Maintain CLAUDE.md as the single source of truth for architecture and detailed descriptions.
  • Updates:
    • Update README.md if high-level changes are made (e.g., adding a new key plugin).
    • Update individual plugin documentation when modifying plugin behavior.
    • Use AUTO-MANAGED blocks in CLAUDE.md if present (or respect existing ones) to keep documentation synchronized.

4. Naming Conventions

  • Directories: Use kebab-case for plugin directory names (e.g., my-plugin-name).
  • Files:
    • Skill definitions: SKILL.md or skills/my-skill.md.
    • Slash commands: commands/my-command.md.
    • Agents: agents/my-expert.md.

Verification Steps

Before submitting changes, perform the following verifications:

  1. JSON Validity: Ensure marketplace.json and any plugin.json files are valid JSON.
  2. Path Validity: Verify that any paths referenced in marketplace.json actually exist in the file system.
  3. Markdown Formatting: Ensure all markdown files are well-formatted and links are valid.
  4. Consistency: Check that the plugin name in the directory matches the name in plugin.json and marketplace.json.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.