CtrlK
BlogDocsLog inGet started
Tessl Logo

node24-action-upgrades

Upgrade checked-in GitHub Actions references off deprecated Node 20 runtimes with the smallest safe major bumps.

60

Quality

70%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.squad/skills/node24-action-upgrades/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A well-structured, concise skill that clearly communicates the intent and decision criteria for upgrading GitHub Actions off deprecated Node 20 runtimes. Its main weakness is the lack of executable commands or scripts for inspecting action.yml metadata and validating changes, and the absence of an explicit step-by-step workflow with verification checkpoints after applying updates.

Suggestions

Add a concrete command or code snippet for inspecting an action's `action.yml` to confirm `runs.using: node24` (e.g., fetching the raw file from GitHub or using `gh api`).

Restructure the Patterns section into an explicit numbered workflow with a validation step at the end (e.g., 'Run the workflow and confirm no deprecation warnings remain').

DimensionReasoningScore

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 references, and the patterns give clear decision criteria. However, there are no executable commands (e.g., grep/sed commands, or a script to inspect action.yml for `runs.using: node24`), and the workflow relies on Claude inferring the exact steps to check upstream tags and composite action internals.

2 / 3

Workflow Clarity

The patterns imply a sequence (start from warnings → inspect candidate → confirm node24 → change workflow → check composites → report unresolved), but it's not presented as an explicit ordered workflow with validation checkpoints. There's no feedback loop for verifying the updated workflows actually pass after changes.

2 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, and well-organized into four clearly labeled sections (Context, Patterns, Example mapping, Anti-Patterns). No bundle files are needed, and the structure is easy to scan.

3 / 3

Total

10

/

12

Passed

Description

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 and distinctive, clearly identifying a narrow task around GitHub Actions Node 20 deprecation upgrades. However, it lacks an explicit 'Use when...' clause and could benefit from additional natural trigger terms that users might employ 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 versions in .yml files.'

Include additional natural trigger terms like 'workflow YAML', 'CI/CD', 'action version bump', 'node16/node20 deprecation warning', or '.github/workflows' to improve keyword coverage.

DimensionReasoningScore

Specificity

The description lists a concrete, specific action: upgrading GitHub Actions references from 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, which per the rubric caps completeness at 2.

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 for Node 20 deprecation — that is unlikely to conflict with other skills. The combination of 'GitHub Actions', 'Node 20', 'deprecated', and 'major bumps' creates a distinct trigger profile.

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
sbroenne/mcp-server-excel
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.