workflow-run-tag-resolution

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

Quality

65%

Does it follow best practices?

Impact

Pending

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

Discovery

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 targets a clear and narrow niche (annotated tag resolution in GitHub workflows), which gives it strong distinctiveness. However, it lacks an explicit 'Use when...' clause and could benefit from listing more concrete actions and natural trigger terms that users might employ when encountering this problem.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when a GitHub Actions workflow fails to resolve an annotated tag, or when tag dereferencing is needed in CI pipelines.'

Include more natural trigger terms users might say, such as 'git tag', 'GitHub Actions', 'CI/CD', 'tag dereferencing', 'GITHUB_REF', or 'workflow_run'.

List additional concrete actions beyond 'resolve', e.g., 'dereferences annotated tags to their commit SHA, configures tag fetching in checkout steps, and ensures correct version resolution in downstream workflows.'

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 elaborate on what 'resolve' entails.	2 / 3
Completeness	It answers 'what' (resolve release tags in follow-on GitHub workflows) but lacks an explicit 'Use when...' clause. The 'when' is only implied by the conditional phrase 'when the source repo uses annotated tags'.	2 / 3
Trigger Term Quality	Includes relevant terms like 'release tags', 'GitHub workflows', and 'annotated tags', but misses common user variations such as 'git tag', 'tag resolution', 'CI/CD', 'actions', or 'workflow dispatch'. The phrasing is somewhat technical and may not match how users naturally describe the problem.	2 / 3
Distinctiveness Conflict Risk	This is a very specific niche — resolving annotated tags in follow-on GitHub workflows — which is unlikely to conflict with other skills. The combination of 'annotated tags', 'release tags', and 'follow-on GitHub workflows' creates a distinct trigger profile.	3 / 3
	Total	9 / 12 Passed

Implementation

72%

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

This is a concise, well-structured skill that addresses a genuinely non-obvious problem (annotated tags in workflow_run contexts). Its main weakness is the lack of a complete, executable workflow YAML example and explicit validation/retry steps, which would elevate it from good guidance to fully actionable instruction.

Suggestions

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

Make the retry loop concrete with an actual shell script example (e.g., a for loop with sleep and exit conditions) rather than just mentioning 'a short retry loop'.

Dimension	Reasoning	Score
Conciseness	Every line addresses a specific, non-obvious pitfall (annotated vs lightweight tags, REST API mismatch, retry loops). No filler or explanation of concepts Claude already knows.	3 / 3
Actionability	Provides specific git commands and action references inline (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 code block. The guidance is concrete but not fully executable.	2 / 3
Workflow Clarity	The numbered patterns imply a sequence (checkout → fetch tags → resolve → retry), but there are no explicit validation checkpoints or a clear feedback loop for the retry mechanism. The steps are listed but not structured as a validated workflow.	2 / 3
Progressive Disclosure	For a focused, single-purpose skill under 50 lines, the content is well-organized into clear sections (Context, Patterns, Examples, Anti-Patterns) with no need for external references or deeper nesting.	3 / 3
	Total	10 / 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: 468809e

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