CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

airflow-publish-changes

Prepare or carry out authorized publication of Apache Airflow changes, including remote checks, pre-push verification, PR creation, and tracking deferred work. Also use when planning these steps or managing contribution issues.

Quality

84%

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

88%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.

The body is a highly actionable, well-validated publication workflow: concrete commands, an explicit pre-push checklist with fix-and-retry loops, and a correctly placed one-level-deep reference for benchmarking. Its only real weakness is mild verbosity in the rationale-heavy passages and some content that could move to reference files.

DimensionReasoningScore

Conciseness

The body is dense with project-specific conventions and commands Claude would not know, with only minor over-explanation — the "Golden rule" rationale ("Airflow does not use issues as a changelog...", "Open issues attract drive-by submissions...") and the restatement of remote-verification in "Creating Pull Requests" could be trimmed. Not level 5 due to those passages; clearly above level 3 since padding is incidental.

4 / 5

Actionability

Fully executable copy-paste commands throughout: `git remote rename apache upstream`, `gh repo fork apache/airflow --remote --remote-name origin`, `prek run --from-ref <target_branch> --stage pre-commit`, `git push -u origin <branch-name>`, and a complete `gh pr create --web` invocation with the body template filled in — matching the level-5 anchor for copy-paste-ready guidance covering common cases.

5 / 5

Workflow Clarity

The publication workflow has explicit validation checkpoints and feedback loops for an outward-facing operation: "run `git remote -v` and verify", "re-run `git remote -v` to confirm", "fix any failures" at each pre-push stage, "Confirm the commands pass", rebase-conflict escalation, and a follow-up procedure for PRs missing tracking issues — matching the level-5 anchor with checklists and error recovery.

5 / 5

Progressive Disclosure

Sections are clearly headed, and performance-benchmarking methodology is properly offloaded to a real, one-level-deep reference cited as `references/performance-sensitive-components.md`, with external conventions deferred to AGENTS.md and contributing docs. Not level 5 because sizable sections (remote-naming rename examples, tracking-issue policy) remain inline in an already-long SKILL.md and could be split out.

4 / 5

Total

18

/

20

Passed

Description

75%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.

The description is specific, action-oriented, in third person, and includes an explicit "use when" clause — a solid, low-conflict description. Its main limitation is that the trigger language is somewhat self-referential and misses the natural phrases a user would most likely say.

Suggestions

Add concrete trigger phrases users would actually say, e.g. "Use when the user wants to open a PR, push a branch to their fork, or submit changes to apache/airflow".

Replace the self-referential "when planning these steps" with the concrete situations it covers (planning a contribution, preparing a PR, handling deferred work).

Name one or two more concrete capabilities — e.g. verifying git remote setup and creating a fork — to round out coverage in the capability list.

DimensionReasoningScore

Specificity

"remote checks, pre-push verification, PR creation, and tracking deferred work" lists several concrete actions with minor coverage gaps, matching the level-4 anchor; it is not level 5 because actions like fork setup, rebasing, and remote-naming fixes are absent and "remote checks" is generic.

4 / 5

Completeness

A clear "what" (publication of Apache Airflow changes including four named activities) is paired with an explicit "Also use when planning these steps or managing contribution issues" clause; not level 5 because the "when" is self-referential ("planning these steps") rather than giving concrete trigger phrases.

4 / 5

Trigger Term Quality

Terms like "publication", "PR creation", and "contribution issues" are relevant and natural, but common user phrasings such as "open a PR", "push my branch", or "submit a contribution" are missing — good coverage with a few natural terms absent (level 4), better than the sparse level-3 example.

4 / 5

Distinctiveness Conflict Risk

Scoping to "Apache Airflow changes" and contribution publication gives a clear niche with minimal conflict risk; not level 5 because "managing contribution issues" could still overlap with a generic issue-triage skill.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 suspicious

Warning

Total

15

/

16

Passed

Repository

apache/airflow

Path

.agents/skills/airflow-publish-changes/SKILL.md

Revision

1a50a18

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill