Apache Airflow is a platform for defining, scheduling, and monitoring workflows as code, with a scheduler assigning dependent tasks to workers. Teams use it to orchestrate automated data and software pipelines and inspect their progress through a user interface. Its catalogue skills and instructions help agents work with Airflow.
Borrowing it
Nothing to install: this file belongs to apache/airflow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/apache/airflow/main/.agents/skills/prepare-providers-documentation/SKILL.mdgit clone --depth 1 https://github.com/apache/airflowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/apache/airflow/prepare-providers-documentation)<a href="https://agentmods.dev/skills/apache/airflow/prepare-providers-documentation"><img src="https://agentmods.dev/badge/skills/apache/airflow/prepare-providers-documentation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/apache/airflow/prepare-providers-documentation"><img src="https://agentmods.dev/badge/skills/apache/airflow/prepare-providers-documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 1097 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium System Prompt Leakage · line 568 Skill contains patterns that could indirectly extract system prompts through rephrasing, translation, summarization, or side-channel techniques.Fix: Guard against indirect extraction by refusing to summarize, translate, or rephrase system instructions. Add explicit anti-extraction clauses.
- medium Excessive Agency · line 644 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00113 | $0.14416 |
| Opus 5.5 | $0.00045 | $0.05766 |
| Sonnet 5.5 | $0.00023 | $0.02883 |
| Haiku 4.5 | $0.00011 | $0.01442 |
Grade A, and why
prepare-providers-documentation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 19d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 1,171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Providers Documentation (AI-driven)
This skill replaces the manual commit-by-commit classification step that the
release manager normally performs when running
breeze release-management prepare-provider-documentation. Instead of asking
the release manager to type d/b/f/x/m/s/v for each commit, the
skill drives the classification itself — inspecting every PR (with extra care
for potentially breaking changes), scoping multi-provider PRs to the slice
that touched the current provider, and asking the release manager only when
genuinely uncertain.
The skill keeps the existing breeze tooling as the source of truth for
template generation. Claude only owns the classification + version bump +
changelog entries; everything else (__init__.py, README.rst,
pyproject.toml, conf.py, get_provider_info.py, index.rst) is still
regenerated by breeze release-management prepare-provider-documentation --reapply-templates-only.
[!IMPORTANT] This is a release-manager workflow. It mutates
provider.yamlandchangelog.rstfor many providers in one pass. Always run on a clean working tree (or in a dedicated branch) and let the release manager review the diff before committing.
When to Use This Skill
Use during the regular provider release cycle, in place of either of:
breeze release-management prepare-provider-documentation
breeze release-management prepare-provider-documentation --incremental-update
…when the release manager wants Claude to classify the changes instead of doing it by hand. The skill covers the same scope: classifying changes, bumping versions, generating changelog sections, reapplying templates, and folding new commits into an already-prepared release PR (incremental update).
Two entry points:
- Initial run — classify everything from scratch for a new release. Follow Phases 1–5 below.
- Incremental update — extend an existing release PR with commits that
landed on
mainsince the changelog was first generated (typical when rebasing a release PR before merging). Skip ahead to the Incremental Update section after Phase 5.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 19d ago Changed · +15 lines f335529327a0
- 1mo ago Changed · +4 lines 3d9f99a3cad9
- 1mo ago Changed · +22 lines f6340225ce88
- 2mo ago First seen · 1,130 lines · 113 tokens per session scan A 85f96e0699a4
prepare-providers-documentation is a skill published in the GitHub repository apache/airflow (47,377 stars, last pushed yesterday), licensed Apache-2.0. It adds 113 tokens to every session and 14,416 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
prepare-providers-documentation compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| prepare-providers-documentationapache/airflow | Skill | 47k | yesterday | Apache-2.0 | A | 113 | Claude Code, Codex |
| git-workflowvstorm-co/pydantic-deepagents | Skill | 1.1k | 7d ago | MIT | A | 17 | Claude Code, Codex |
| antigravity-maintainer-batch-releaseranbot-ai/awesome-skills | Skill | 8 | yesterday | none | A | 50 | Claude Code, Codex |
| create-releasecocoindex-io/cocoindex | Skill | 12k | yesterday | Apache-2.0 | A | 155 | Claude Code, Codex |
| xberg-releasexberg-io/xberg | Skill | 9.5k | today | MIT | A | 16 | Claude Code, Codex |
| flow-next-landgmickel/flow-next | Skill | 717 | yesterday | MIT | A | 35 | Claude Code, Codex |
| development-workflowathola/claude-night-market | Skill | 348 | yesterday | MIT | A | 20 | Claude Code |