agentleFS
Sign inStart free
Cogni-AI-OUCogni-AI-OU/cogni-ai-agent-skills/astronomer-docs/SKILL.md

astronomer-docs

Skill4 starsChanged 6 months agoMITView on GitHub

Read and navigate Astronomer documentation using llms.txt context. You MUST load this skill when asked to read Astronomer documentation or Airflow documentation hosted by Astronomer.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When needing to read or reference Astronomer or Airflow documentation.

    line 15
  2. Distinctive:

    When searching for Astronomer-specific Airflow deployment, orchestration, or DAG guidelines.

    line 16
  3. Very specific:

    When you are prompted to check astronomer.io/docs for information.

    line 17
  4. Very specific:

    When you are writing Airflow DAGs (use apache-airflow-dags instead).

    line 21
  5. Very specific:

    When interacting with Airflow APIs (use apache-airflow-api instead).

    line 22
  6. Very specific:

    Always prefer reading from llms.txt over scraping individual HTML pages, as llms.txt paths return markdown optimized for your context …

    line 34
  7. Very specific:

    When looking for specific DAG authoring techniques, use the references in the llms.txt to find the correct .md documentation page.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Skill: astronomer-docs

Astronomer Docs

<!-- markdownlint-disable MD013 MD023 MD031 MD032 -->

When to Use

  • When needing to read or reference Astronomer or Airflow documentation.
  • When searching for Astronomer-specific Airflow deployment, orchestration, or DAG guidelines.
  • When you are prompted to check astronomer.io/docs for information.

When Not to Use

  • When you are writing Airflow DAGs (use apache-airflow-dags instead).
  • When interacting with Airflow APIs (use apache-airflow-api instead).

Core Process

  1. Use llmstxt conventions: Astronomer provides an llms.txt file which is highly optimized for LLMs.
  2. Fetch the context: Utilize the webfetch tool to retrieve the context files.
  3. Primary References:
    • https://www.astronomer.io/llms.txt: The index of all LLM-friendly documentation.
    • https://www.astronomer.io/docs/llms.txt: The index specifically for Astronomer documentation.

Best Practices

  • Always prefer reading from llms.txt over scraping individual HTML pages, as llms.txt paths return markdown optimized for your context window.
  • When looking for specific DAG authoring techniques, use the references in the llms.txt to find the correct .md documentation page.

References

Related Skills

  • apache-airflow-dags: You MUST load this skill when asked to write, refactor, or structure Airflow DAGs.
  • llmstxt: You MUST load this skill when reading websites, llms.txt, or when creating/updating that file.

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.

Check your setup, free