workflow-run-tag-resolution

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

87%

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

The body is concise and action-oriented with executable examples and clean section organization, so conciseness, actionability, and progressive disclosure score well. The main gap is workflow clarity, where the validation/retry steps are described but not presented as explicit checkpoints in the sequence.

Suggestions

Turn the numbered Patterns into an explicit sequence with a validation checkpoint, e.g. step '4. Verify a tag resolved; if empty, retry up to N times before treating it as a failure'.

Show the retry loop as concrete shell rather than prose so the error-recovery feedback is executable, not just described.

Add an explicit failure/abort condition so an empty tag lookup is handled with a clear next action instead of only being called out as an anti-pattern.

Dimension	Reasoning	Score
Conciseness	The body is lean at roughly 23 lines with no preamble explaining concepts Claude already knows; every section (Context, Patterns, Examples, Anti-Patterns) earns its place, matching the level-3 anchor.	3 / 3
Actionability	The Good example supplies concrete, executable commands (`actions/checkout@v4` with `fetch-depth: 0`, `git fetch --force --tags origin`, `git tag --points-at "$HEAD_SHA" --sort=-version:refname`) that are copy-paste ready, satisfying the level-3 anchor.	3 / 3
Workflow Clarity	The five Patterns are clearly sequenced and a retry loop is mentioned, but validation/verification checkpoints are only implicit (e.g. 'separately validated' is asserted, not spelled out as a step), fitting the level-2 anchor rather than the explicit-checkpoint level-3 anchor.	2 / 3
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is organized into clearly labeled sections, which per the judging guidelines lets progressive disclosure score 3 on well-organized sections alone.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 and occupies a clear, low-conflict niche, but it relies on a single named action and embeds its trigger condition rather than stating an explicit 'Use when…' clause. Adding explicit trigger guidance and a broader set of natural trigger terms would raise the weaker dimensions.

Suggestions

Add an explicit 'Use when…' clause naming the triggering situation (e.g. 'Use when a workflow_run-triggered workflow must recover the release tag from the completed source workflow').

Broaden trigger terms to include natural phrasings users would say, such as 'GitHub Actions', 'workflow_run', and 'release version'.

Mention the second concrete action (e.g. retrying on tag-visibility delay) so the capability list reads as multiple specific actions.

Dimension	Reasoning	Score
Specificity	The phrase 'Resolve release tags reliably in follow-on GitHub workflows' names a concrete action and its domain context, but it lists only a single action rather than multiple specific concrete actions, so it falls short of the level-3 anchor.	2 / 3
Completeness	It states what the skill does and embeds a 'when the source repo uses annotated tags' condition, but there is no explicit 'Use when…' trigger clause, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	It includes relevant terms like 'release tags', 'GitHub workflows', and 'annotated tags', but these lean technical and omit common natural variations a user would say (e.g. 'workflow_run', 'GitHub Actions', 'release version'), matching the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The narrow scope of 'follow-on GitHub workflows' triggered by annotated tags defines a clear niche with distinct triggers that is unlikely to conflict with other skills.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: sbroenne/mcp-server-excel
Commit: b268be5

Reviewed: 7 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.