node24-action-upgrades
Upgrade checked-in GitHub Actions references off deprecated Node 20 runtimes with the smallest safe major bumps.
75
70%
Does it follow best practices?
Impact
Pending
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 limits completeness, and could benefit from more natural trigger terms that users would actually say when encountering this problem.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user needs to fix deprecated Node.js runtime warnings in GitHub Actions workflows or update action version pins.'
Include additional natural trigger terms like 'workflow YAML', 'CI/CD', 'actions/checkout', 'node16 deprecation', or 'deprecated action warnings' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists a concrete, specific action: upgrading GitHub Actions references off deprecated Node 20 runtimes with smallest safe major bumps. It names the domain (GitHub Actions), the problem (deprecated Node 20 runtimes), and the approach (smallest safe major bumps). | 3 / 3 |
Completeness | The 'what' is clearly stated (upgrade GitHub Actions references off deprecated Node 20 runtimes), but there is no explicit 'Use when...' clause or equivalent trigger guidance telling Claude when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'GitHub Actions', 'Node 20', 'deprecated', and 'runtimes', but misses common user variations like 'node16 deprecation', 'actions/checkout', 'workflow YAML', '.yml', or 'CI/CD'. Users might say 'update my GitHub Actions' or 'fix deprecated action warnings' which aren't well covered. | 2 / 3 |
Distinctiveness Conflict Risk | This is a very specific niche — upgrading GitHub Actions references specifically for Node 20 runtime deprecation. It is highly unlikely to conflict with other skills due to its narrow, well-defined scope. | 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 well-scoped, concise skill that clearly communicates the domain-specific knowledge Claude needs (runtime metadata checks, composite action pitfalls, smallest-safe-bump philosophy). Its main weakness is the lack of executable commands or concrete workflow steps—the patterns read more as guidelines than a step-by-step procedure, and for a batch modification task, explicit validation checkpoints would strengthen it.
Suggestions
Add a concrete numbered workflow (e.g., 1. grep warnings from logs, 2. fetch action.yml with a specific curl/gh command, 3. verify `runs.using: node24`, 4. update the workflow file, 5. validate by running the workflow) with explicit validation checkpoints.
Include at least one executable code snippet or command, such as how to inspect an action's `action.yml` for its runtime declaration (e.g., `gh api repos/actions/checkout/contents/action.yml?ref=v5 | yq '.runs.using'`).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No unnecessary explanations of what GitHub Actions are or how Node.js runtimes work. The content assumes Claude understands CI/CD concepts and gets straight to the specific, non-obvious guidance. | 3 / 3 |
Actionability | The example mapping table is concrete and useful, and the patterns provide specific guidance (e.g., check `action.yml` for `runs.using: node24`). However, there are no executable commands or code snippets—no grep/sed commands, no script to inspect action.yml files, no concrete workflow diff showing before/after YAML changes. | 2 / 3 |
Workflow Clarity | The patterns imply a sequence (start from warnings → inspect candidate → confirm node24 → change workflow), but it's not explicitly structured as ordered steps with validation checkpoints. For a task involving batch modifications to CI workflows (potentially destructive), explicit validation steps (e.g., 'run the workflow and confirm warnings are gone') are missing. | 2 / 3 |
Progressive Disclosure | This is a focused, single-purpose skill under 50 lines. The content is well-organized into clear sections (Context, Patterns, Example mapping, Anti-Patterns) with no need for external references. Navigation is straightforward. | 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
468809e
- 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.