CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

airflow-pr-draft-summary

Draft Apache Airflow commit messages, PR titles and descriptions, or GitHub comments and reviews. Also use for release-note decisions when preparing a contribution.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/airflow-pr-draft-summary/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable instruction skill whose rules are concrete and example-driven. Its main weakness is token efficiency: repeated prohibitions and padded explanations could be consolidated without losing clarity.

Suggestions

State the Conventional Commits prohibition once (in the good/bad examples) and drop the duplicate paragraph, keeping only the note that area tags like `UI:` are fine.

Compress the PR-number explanation to its decision rule — "no issue/PR number in titles; GitHub appends it on squash-merge; reference issues in the description only" — and integrate the dangling Co-Authored-By bullet into the commit-message checklist.

Optionally move the GitHub attribution-footer rules to a references file (e.g. `references/attribution.md`) and keep a two-line summary with the two footer templates in SKILL.md.

DimensionReasoningScore

Conciseness

The body states the Conventional Commits prohibition twice (in the good/bad examples and again in the imperative-mood paragraph), spends seven lines explaining why not to put PR numbers in titles, and ends the first section with a stray "NEVER add Co-Authored-By" bullet — mostly efficient but with clear tightening opportunities.

3 / 5

Actionability

Concrete good/bad commit-title examples, copy-paste-ready Drafted-by footer templates, and an exact newsfragment command (`echo "Brief description" > airflow-core/newsfragments/{PR_NUMBER}.significant.rst`) make the guidance mostly executable; the PR template and AGENTS.md rules are only referenced, leaving minor gaps.

4 / 5

Workflow Clarity

Guidance is clearly organized by artifact type with grounded directives ("keep titles under 70 characters", "Report only checks actually executed and their outcomes"), and nothing destructive or batch-like demands validation checkpoints; the drafting flow itself lacks an explicit sequence for requests spanning multiple artifacts.

4 / 5

Progressive Disclosure

Sections are well organized and all external pointers (`.github/PULL_REQUEST_TEMPLATE.md`, root `AGENTS.md`, sibling `airflow-publish-changes/SKILL.md`) are one level deep and clearly signaled; the ~40-line GitHub-attribution section is borderline inline content and the misplaced Co-Authored-By bullet is a minor gap.

4 / 5

Total

15

/

20

Passed

Description

71%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 specific, well-scoped description that names concrete contribution-text artifacts, held back by the absence of a general 'Use when…' trigger clause and a few missing natural synonyms. Adding explicit trigger guidance would raise completeness and trigger-term quality simultaneously.

Suggestions

Add a general trigger clause, e.g. "Use when the user asks to write or review commit messages, PR titles/descriptions, comments, reviews, or release notes for an Apache Airflow contribution."

Include common user phrasings and synonyms such as "pull request", "changelog", and "newsfragment" so natural requests match the description.

Briefly distinguish this drafting skill from the sibling publish/posting skill (e.g. "drafts only; does not post") to reduce overlap risk.

DimensionReasoningScore

Specificity

The description lists multiple concrete drafting actions — "commit messages, PR titles and descriptions, or GitHub comments and reviews" plus "release-note decisions" — which comprehensively covers the contribution-text domain it claims.

5 / 5

Completeness

The "what" is clear, but the only explicit "when" is scoped to one sub-case ("release-note decisions when preparing a contribution"); the primary drafting capability has no trigger clause, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Natural terms users would say are present ("commit messages", "PR titles", "release notes", "GitHub comments and reviews"), but common variations like "pull request", "changelog", "newsfragments", or "contribution" are missing.

4 / 5

Distinctiveness Conflict Risk

Scoping to "Apache Airflow" gives it a clear niche distinct from generic drafting skills, but it retains minor overlap risk with closely related skills such as generic commit-message writers and the sibling publish-changes skill whose boundary is not drawn here.

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: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

apache/airflow

Path

.agents/skills/airflow-pr-draft-summary/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.