node24-action-upgrades
Upgrade checked-in GitHub Actions references off deprecated Node 20 runtimes with the smallest safe major bumps.
60
70%
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/node24-action-upgrades/SKILL.mdQuality
Discovery
67%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 highly specific about what it does and occupies a clear niche, making it distinctive. However, it lacks an explicit 'Use when...' clause, which caps completeness, and could benefit from more natural trigger terms that users might actually say when encountering this problem (e.g., 'CI deprecation warnings', 'workflow YAML').
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to fix GitHub Actions deprecation warnings, update action versions in workflow YAML files, or migrate off Node 16/20 runtimes.'
Include additional natural trigger terms users might say, such as 'CI', 'workflow files', '.yml', 'actions/checkout', 'node16 deprecation', or 'set-output deprecation warning'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists concrete actions: upgrading GitHub Actions references, moving off deprecated Node 20 runtimes, and applying smallest safe major bumps. These are specific, actionable capabilities. | 3 / 3 |
Completeness | The 'what' is clearly stated (upgrade GitHub Actions off deprecated Node 20 runtimes with smallest safe major bumps), but there is no explicit 'Use when...' clause or trigger guidance telling Claude when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'GitHub Actions', 'Node 20', 'deprecated', and 'runtimes', but misses common user phrasings like 'CI', 'workflow files', '.yml', 'node16 deprecation warning', or 'actions/checkout'. Users might describe the problem differently than 'deprecated Node 20 runtimes'. | 2 / 3 |
Distinctiveness Conflict Risk | This is a very specific niche — upgrading GitHub Actions references for Node 20 deprecation — that is unlikely to conflict with other skills. The combination of GitHub Actions, Node 20, and version bumping creates a distinct trigger profile. | 3 / 3 |
Total | 10 / 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 communicates the decision logic and version mappings for upgrading GitHub Actions off Node 20. Its main weakness is the lack of executable commands or scripts for inspecting action.yml metadata and validating changes, and the workflow could benefit from explicit sequential steps with a verification checkpoint after applying changes.
Suggestions
Add a concrete workflow section with explicit steps: 1) extract warnings from CI logs, 2) inspect each action's action.yml (e.g., `gh api repos/actions/checkout/contents/action.yml?ref=v5 | ...`), 3) update refs, 4) push and verify warnings are resolved.
Include a validation checkpoint such as 'After updating, trigger a CI run and confirm no Node.js deprecation warnings remain' to close the feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what GitHub Actions are or how Node.js runtimes work. The example mapping is a compact lookup table, and anti-patterns are terse but informative. | 3 / 3 |
Actionability | The example mapping provides concrete before/after version pairs, and the patterns give clear decision criteria. However, there are no executable commands (e.g., grep/sed one-liners, gh CLI commands to fetch action.yml, or a script to automate the inspection). The guidance is specific but not copy-paste ready. | 2 / 3 |
Workflow Clarity | The patterns section implies a sequence (start from warnings → inspect action.yml → confirm node24 → change workflow), but it's presented as a numbered list of principles rather than an explicit step-by-step workflow. There are no validation checkpoints (e.g., 'run the workflow after changes to confirm warnings are gone') or feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | For a focused, single-purpose skill under 50 lines with no bundle files, the content is well-organized into clear sections (Context, Patterns, Example mapping, Anti-Patterns) that are easy to scan. No external references are needed for this scope. | 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.