workflow-run-tag-resolution

Resolve release tags reliably in follow-on GitHub workflows when the source repo uses annotated tags.

Quality

56%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.squad/skills/workflow-run-tag-resolution/SKILL.md

Quality

Content

72%

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

A concise, well-structured skill that clearly identifies the core problem (annotated tags vs lightweight tags in workflow_run contexts) and provides useful guidance. Its main weakness is the lack of a complete, executable workflow YAML example and an explicit step-by-step sequence with validation checkpoints, which would make it significantly more actionable.

Suggestions

Add a complete, copy-paste-ready GitHub Actions workflow YAML snippet showing the checkout, tag fetch, tag resolution, and retry loop steps together.

Convert the Patterns list into an explicit numbered workflow sequence with validation checkpoints (e.g., 'If tag list is empty after retries, fail with a clear error message explaining annotated tag resolution').

Dimension	Reasoning	Score
Conciseness	Every line adds value. No unnecessary explanations of what GitHub Actions or annotated tags are—assumes Claude knows these concepts. The patterns, examples, and anti-patterns are all tightly written.	3 / 3
Actionability	Provides specific commands (e.g., `git tag --points-at "$HEAD_SHA" --sort=-version:refname`, `actions/checkout@v4` with `fetch-depth: 0`) but lacks a complete, copy-paste-ready workflow YAML snippet or executable script. The 'retry loop' is mentioned but not shown.	2 / 3
Workflow Clarity	The patterns are listed in a logical order (checkout → fetch tags → resolve → retry → manual replay), but they are presented as a flat list of principles rather than a clearly sequenced workflow with explicit validation checkpoints or error recovery steps.	2 / 3
Progressive Disclosure	This is a short, focused skill under 50 lines with no need for external references. The content is well-organized into clear sections (Context, Patterns, Examples, Anti-Patterns) that are easy to navigate.	3 / 3
	Total	10 / 12 Passed

Description

40%

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 identifies a clear, narrow niche (resolving annotated tags in GitHub CI workflows), which gives it strong distinctiveness. However, it lacks an explicit 'Use when...' clause, provides only a single vague action ('resolve'), and misses common trigger terms users would naturally use when encountering this problem.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when a workflow_run or reusable workflow cannot find the correct tag SHA, or when GITHUB_REF points to the wrong commit for annotated tags.'

List concrete actions the skill performs, e.g., 'Dereferences annotated tags to their commit SHA, configures tag fetching in checkout steps, and passes resolved refs to downstream workflow jobs.'

Include additional natural trigger terms users might search for: 'git tag', 'GITHUB_REF', 'workflow_run', 'tag dereference', 'reusable workflow', 'checkout action'.

Dimension	Reasoning	Score
Specificity	It names a specific domain (GitHub workflows, release tags, annotated tags) and describes one action (resolve release tags), but doesn't list multiple concrete actions or detail what 'resolve' entails (e.g., dereference, fetch, pass to downstream jobs).	2 / 3
Completeness	It describes what the skill does (resolve release tags in follow-on workflows) but has no explicit 'Use when...' clause or trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also somewhat thin, placing this at 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'release tags', 'GitHub workflows', 'annotated tags', but misses common user variations such as 'git tag', 'tag resolution', 'workflow_run', 'dereference tag', 'GITHUB_REF', or '.yml' that users might naturally use when encountering this problem.	2 / 3
Distinctiveness Conflict Risk	The description targets a very specific niche — annotated tags in follow-on GitHub workflows — which is unlikely to conflict with other skills. The combination of 'annotated tags', 'follow-on workflows', and 'release tags' creates a distinct trigger profile.	3 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: sbroenne/mcp-server-excel
Commit: 3b31cfb

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.