CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-pkg-upgrade-review

Reviews package version upgrades — diffs source between versions, traces call sites, and generates compatibility reports.

61

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.skillshare/skills/1k-pkg-upgrade-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

The body is well-structured and highly actionable, with concrete commands, a clear sequenced workflow, and excellent progressive disclosure via a reference table. The only real gaps are a slightly redundant opening line and a missing validation checkpoint before posting the PR comment.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the opening sentence 'Evaluates npm/yarn package version upgrades by performing source-level diff analysis, tracing all call sites, and producing a structured compatibility report.' nearly duplicates the frontmatter description and could be trimmed.

4 / 5

Actionability

The Key Commands block provides fully executable, copy-paste-ready bash covering download/extract, file-list diff, source diff, direct and indirect usage search, and metadata checks, with the common cases specifically addressed.

5 / 5

Workflow Clarity

A clear 10-step sequenced workflow with built-in verification ('Trace each call site to verify argument usage and compatibility', 'Assess compatibility risks'), but there is no explicit validation checkpoint before the outward-facing 'gh pr comment' post, leaving a minor validation gap.

4 / 5

Progressive Disclosure

A Quick Reference table links to three real one-level-deep bundle files (review-workflow.md, report-template.md, example-report.md) with descriptions, giving a clear overview with well-signaled, easy navigation.

5 / 5

Total

18

/

20

Passed

Description

62%Weight 40%Scale 1-5

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 states a clear, specific purpose with concrete actions and a distinct niche, but it omits any explicit 'when to use' trigger guidance and lacks common dependency-bump synonyms. Adding a 'Use when…' clause would lift both completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when…' clause naming concrete triggers (e.g., 'Use when reviewing Dependabot/Renovate PRs, manual yarn/npm upgrades, or changes to lockfiles').

Include natural synonyms users say — 'dependency', 'bump', 'lockfile' — alongside 'package version upgrades' to improve trigger-term coverage.

Optionally note the output artifact (compatibility report) is posted as a PR comment so the trigger and outcome are unambiguous.

DimensionReasoningScore

Specificity

Lists three concrete actions — 'diffs source between versions', 'traces call sites', 'generates compatibility reports' — which is several specific actions with only minor coverage gaps, fitting the anchor-4 example better than the four-action anchor-5 example.

4 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when…' clause or equivalent explicit trigger guidance, which the judging guidelines explicitly cap at 3.

3 / 5

Trigger Term Quality

'package version upgrades' is a natural keyword, but common trigger synonyms users actually say — 'dependency', 'bump', 'Dependabot', 'Renovate' — are absent, matching the anchor-3 case of relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

'Reviews package version upgrades' with compatibility reports carves a clear, narrow niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 2 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository
OneKeyHQ/app-monorepo
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.