CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prepare-providers-documentation

Replace the manual commit-by-commit classification step in `breeze release-management prepare-provider-documentation` with AI-driven classification. For each provider with pending changes, analyze every PR (batched into one sub-agent per provider, not one per PR), pay special attention to potentially breaking changes by inspecting the actual diff, scope multi-provider PRs to the current provider's slice, ask the release manager when uncertain, and apply version bumps + changelog entries. Use during the regular provider release cycle as an alternative to the interactive breeze prompts.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally actionable, well-sequenced workflow skill — every phase has executable commands, explicit checkpoints, and error-recovery loops appropriate to a batch release operation. Its weaknesses are size-related: at ~1,150 lines it repeats validation rules across phases and inlines materials (the sub-agent brief, changelog rules) that belong in one-level-deep reference files, which costs both conciseness and progressive disclosure.

Suggestions

Move the ~95-line sub-agent classification brief and the Phase 4b changelog-entry rules into reference files (e.g. references/subagent-brief.md, references/changelog-rules.md) and keep one-line pointers in the phases, cutting the main SKILL.md to a navigable overview.

Deduplicate the Phase 5 entry-defect scan: it restates the Phase 4b rules (capitalization, excluded-block, collapsed chains, abbreviations, dependency versions) — replace the restated list with a short cross-reference to the Phase 4b rules it verifies.

Collect the dated wave observations (2026-07-22, 2026-08-01 misses, specific PR numbers) into a single 'Observed failure modes' or old-patterns section so the time-sensitive evidence is clearly marked as historical and does not read as current state.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious domain knowledge, but it is ~1,150 lines with real tightening opportunities: Phase 5's defect scan restates the Phase 4b rules nearly verbatim ("a bullet whose text starts with a lowercase letter → capitalize it (Phase 4b)"...), "Things you must NOT do silently" repeats earlier phases, and dated worked examples ("Observed in the 2026-08-01 wave: cohere gained #69649...") are time-sensitive without a deprecated/old-patterns section. This fits anchor 3 ('mostly efficient but... could be tightened') better than 4, where over-explanation would be only minor.

3 / 5

Actionability

Fully executable throughout: exact bash and git commands with gotcha handling (the tag-sort pipeline excluding "/99.9[0-9]." and rc tags), a copy-paste sub-agent brief with an exact pipe-format output spec, the RST changelog skeleton, and a concrete validation script with a defect-code table (MISSING/UNKNOWN/SECTION/ORDER). Matches anchor 5 — copy-paste ready commands covering the common cases.

5 / 5

Workflow Clarity

Five numbered phases plus a parallel incremental flow, release shapes (wave/ad-hoc) established before branching logic, and explicit validation with feedback loops: "Re-run it after **any** rebase", "Re-run discovery after Phase 4a", the idempotent no-op diff check, and the check_changelog_entries.py gate. For a batch operation this is anchor 5's 'explicit validation steps; feedback loops; checklists'.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent) and everything lives in one ~60 KB SKILL.md; the ~95-line sub-agent prompt template and the ~100 lines of changelog-entry rewriting rules clearly belong in separate reference files. Internal structure is good (phases, alert blocks, a References section), which lifts it above anchor 2's 'minimal structure', but the volume of content inlined in the main file fits anchor 3 ('content that should be separate is inline') better than 4, where inlining would be a minor gap.

3 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states concrete replacement behavior, scopes the entry points (initial vs. the regular release cycle), and closes with an explicit 'Use during...' clause. The only weakness is trigger-term breadth — a couple of natural synonyms for the provider-release process are missing, which barely affects its already-low conflict risk.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "analyze every PR (batched into one sub-agent per provider...)", "inspecting the actual diff", "apply version bumps + changelog entries" — with comprehensive coverage of the skill's behavior. It exceeds the 4 anchor ('several specific actions, minor gaps') because nothing material is missing.

5 / 5

Completeness

It explicitly answers both: what ("Replace the manual commit-by-commit classification step... analyze every PR... apply version bumps + changelog entries") and when ("Use during the regular provider release cycle as an alternative to the interactive breeze prompts"). The explicit 'Use during...' clause with concrete context matches the 5 anchor; it is not 4 because the 'when' is already specific, not merely present.

5 / 5

Trigger Term Quality

Natural domain phrases are present ("provider release cycle", "version bumps", "changelog", "release manager", "prepare-provider-documentation") but a few natural variations users might say are absent ("release notes", "release wave", "incremental update"). This matches anchor 4 — good coverage with a few natural terms missing — rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Naming the exact breeze command ("breeze release-management prepare-provider-documentation") and the Airflow provider-release niche gives it a clear niche with distinct triggers and virtually no overlap risk with other skills. Matches anchor 5.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1172 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

apache/airflow

Path

.agents/skills/prepare-providers-documentation/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.