agents
AGENTS.md459 starsChanged 36 days agoApache-2.0View on GitHub
After adding skills or making changes, reinstall the plugin: Skills are markdown files with YAML frontmatter in skills/<name>/SKILL.md: Plugin configuration is split across two files: Use ${CLAUDE_PLUGIN_ROOT} to reference files within the plugin (required because plugins are copied to a cache location when installed). Important: Hooks in SKILL.md frontmatter can use relative paths from the skill's directory (e.g., ./scripts/bar.py). Use ${CLAUDE_PLUGIN_ROOT} in plugin.json to reference the plugin root. This plugin uses ~/.astro/agents/ for user configuration (warehouse credentials, etc.).
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 31,774 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 repository35 other files it gives its agents.
- astro-airflow-mcp/AGENTS.mdAGENTS.md
- airflow-hitlSkill
- airflow-pluginsSkill
- airflowSkill
- airflow-state-storeSkill
- analyzing-dataSkill
- annotating-task-lineageSkill
- authoring-dagsSkill
- authoring-go-sdk-tasksSkill
- authoring-java-sdk-tasksSkill
- authoring-language-sdk-tasksSkill
- blueprintSkill
- checking-freshnessSkill
- configuring-airflow-language-sdksSkill
- cosmos-dbt-coreSkill
- cosmos-dbt-fusionSkill
- creating-openlineage-extractorsSkill
- dag-factorySkill
- debugging-dagsSkill
- delegating-to-ottoSkill
- deploying-airflowSkill
- deploying-go-sdk-bundlesSkill
- deploying-java-sdk-bundlesSkill
- managing-astro-deploymentsSkill
- managing-astro-local-envSkill
- migrating-airflow-2-to-3Skill
- migrating-ai-sdk-to-common-aiSkill
- migrating-dagster-to-airflowSkill
- profiling-tablesSkill
- setting-up-astro-projectSkill
- testing-dagsSkill
- tracing-downstream-lineageSkill
- tracing-upstream-lineageSkill
- troubleshooting-astro-deploymentsSkill
- warehouse-initSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
After adding skills or making changes, reinstall the plugin:
- Very specific: line 75
Use ${CLAUDE_PLUGIN_ROOT} to reference files within the plugin (required because plugins are copied to a cache location when installed).
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 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
<!-- START doctoc generated TOC please keep comment here to allow auto update --><!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->Table of Contents generated with DocToc
- Claude Code Plugin Development
- Plugin Structure
- Installing the Plugin
- Skills
- Configuration
- Key Files
- Config Location
<!-- END doctoc generated TOC please keep comment here to allow auto update -->Claude Code Plugin Development
Plugin Structure
project-root/
├── .claude-plugin/
│ ├── marketplace.json # Marketplace catalog (strict: false)
│ └── plugin.json # Plugin manifest with hooks
└── skills/ # Skills (auto-discovered)
└── skill-name/
├── SKILL.md # Skill with YAML frontmatter
└── hooks/ # Hook scripts (co-located with skill)
└── *.shInstalling the Plugin
# Add the marketplace (from repo root)
claude plugin marketplace add astronomer/agents
# Install the plugin
claude plugin install astronomer-data@astronomer
# Or test locally (session only)
claude --plugin-dir .After adding skills or making changes, reinstall the plugin:
claude plugin uninstall astronomer-data@astronomer && claude plugin marketplace update && claude plugin install astronomer-data@astronomerSkills
Skills are markdown files with YAML frontmatter in skills/<name>/SKILL.md:
---
name: skill-name
description: When to use this skill (Claude uses this to decide when to invoke it)
---
# Skill content here...- Skills are auto-discovered from the
skills/directory - Claude invokes skills automatically based on the description matching user requests
- Users can also invoke directly with
/plugin-name:skill-name(e.g.,/astronomer-data:authoring-dags)
Configuration
Plugin configuration is split across two files:
- hooks: Inlined in
.claude-plugin/plugin.json, scripts co-located inskills/<name>/hooks/ - mcpServers: Inlined in
.claude-plugin/plugin.json - skills: Auto-discovered from
skills/directory - marketplace metadata: Defined in
.claude-plugin/marketplace.json(strict: false)
Use ${CLAUDE_PLUGIN_ROOT} to reference files within the plugin (required because plugins are copied to a cache location when installed).
Important: Hooks in SKILL.md frontmatter can use relative paths from the skill's directory (e.g., ./scripts/bar.py). Use ${CLAUDE_PLUGIN_ROOT} in plugin.json to reference the plugin root.
Key Files
.claude-plugin/plugin.json- Plugin manifest with hooks and mcpServers.claude-plugin/marketplace.json- Marketplace catalog (metadata only,strict: false)skills/*/SKILL.md- Individual skills (auto-discovered)skills/*/hooks/*.sh- Hook scripts (co-located with skills, referenced via relative paths from SKILL.md or${CLAUDE_PLUGIN_ROOT}/skills/<name>/hooks/...from plugin.json)
Config Location
This plugin uses ~/.astro/agents/ for user configuration (warehouse credentials, etc.).
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.

