workflow-run-tag-resolution
Resolve release tags reliably in follow-on GitHub workflows when the source repo uses annotated tags.
51
56%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.squad/skills/workflow-run-tag-resolution/SKILL.mdQuality
Discovery
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 and narrow niche (annotated tag resolution in GitHub workflows), which gives it strong distinctiveness. However, it lacks an explicit 'Use when...' clause and doesn't enumerate specific concrete actions beyond 'resolve release tags reliably,' making it incomplete and somewhat vague for skill selection purposes.
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/CD pipelines.'
List specific concrete actions the skill performs, such as 'dereference annotated tags to commit SHAs, configure checkout steps for tag-triggered workflows, fix tag resolution errors in reusable workflows.'
Include natural user trigger terms like 'git tag', 'GitHub Actions', 'CI/CD', 'tag not found', 'checkout tag' to improve discoverability.
| 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 describes what the skill does (resolve release tags in follow-on GitHub workflows) but has no explicit 'Use when...' clause or trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is also somewhat vague about the specific steps involved, pushing this toward 1. | 1 / 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 'dereferenced tag'. The phrasing is somewhat technical and may not match how users naturally describe the problem. | 2 / 3 |
Distinctiveness Conflict Risk | The description targets 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 | 8 / 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.
A concise, well-structured skill that clearly identifies the core problem (annotated tags vs lightweight tags in workflow_run contexts) and provides useful patterns and anti-patterns. Its main weakness is the lack of a complete, executable workflow YAML example and an explicit retry loop implementation, which would significantly improve actionability and workflow clarity.
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 snippet (e.g., a for loop with sleep and exit conditions) rather than just mentioning it as a pattern.
| 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' pattern is mentioned but not shown concretely. | 2 / 3 |
Workflow Clarity | The numbered patterns imply a sequence (checkout → fetch tags → resolve → retry → validate manual paths), but there are no explicit validation checkpoints or a clear feedback loop for the retry mechanism. The steps read more like guidelines than a sequenced workflow with error recovery. | 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 |
Validation
90%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
e8764a6
- 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.