CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

next-rspack

Maintain @next/rspack-core and @next/rspack-binding packages. Use when editing rspack/package.json, rspack/crates/binding/Cargo.toml, rspack/rust-toolchain.toml, or packages/next-rspack/package.json. Covers upgrading @rspack/core npm version, rspack_* crate versions, Rust toolchain version, building and linking for local testing, and NEXT_RSPACK environment variable usage. Does NOT apply to root rust-toolchain.toml (that's for Turbopack).

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

A well-structured, actionable runbook with a clear multi-step upgrade workflow and validation checkpoints. Its main weaknesses are mild redundancy between the description, 'When to Use', and 'Pre-requisites' sections, and the absence of explicit error-recovery feedback loops.

Suggestions

Consolidate the 'When to Use' bullets and 'Pre-requisites for Local Testing' block to avoid re-stating steps 5–6 and the frontmatter description, tightening conciseness.

Add an explicit validate→fix→retry feedback loop for the 'Verify Build' step (e.g., 'if cargo check fails, address errors and re-run before proceeding') to strengthen workflow clarity.

Consider moving the version-mapping table and release-process details into a reference file referenced one level deep, so SKILL.md reads as a leaner overview.

DimensionReasoningScore

Conciseness

Mostly efficient with no over-explanation of concepts Claude already knows, but the 'When to Use' section duplicates the frontmatter description and the 'Pre-requisites for Local Testing' section re-walks steps 5–6, which could be tightened.

4 / 5

Actionability

Provides concrete, mostly copy-paste-ready guidance — package.json/Cargo.toml/rust-toolchain.toml edits, 'cargo check', 'pnpm build', 'pnpm link ../../rspack', and the test commands — with version placeholders that are appropriate templating rather than pseudocode.

4 / 5

Workflow Clarity

A clear 7-step upgrade sequence with validation checkpoints ('Verify Build' via cargo check/pnpm build and 'Run Tests') and a Key Files Checklist; minor gap is that build-failure feedback loops are only implicit ('re-run pnpm build') rather than a full validate→fix→retry loop.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and a one-level-deep external References section, but it is a monolithic single-file skill (~268 lines) with no content split into bundle files, which leaves minor organization headroom versus the 'appropriately split' anchor.

4 / 5

Total

16

/

20

Passed

Description

92%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.

A strong, specific description that clearly states what it does and when to use it, with an explicit scope boundary to avoid mis-triggering. Trigger terms are concrete file paths and package identifiers rather than natural-language phrases, which is the only minor weakness.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'upgrading @rspack/core npm version, rspack_* crate versions, Rust toolchain version, building and linking for local testing, and NEXT_RSPACK environment variable usage' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' ('Maintain @next/rspack-core and @next/rspack-binding packages ... Covers upgrading ...') and 'when' ('Use when editing ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Triggers are concrete file paths and package/crate/env-var names ('editing rspack/package.json, rspack/crates/binding/Cargo.toml, rspack/rust-toolchain.toml, or packages/next-rspack/package.json'); good coverage but the phrasing leans technical rather than the natural phrases a user would say.

4 / 5

Distinctiveness Conflict Risk

A tight, well-scoped niche with an explicit negative boundary — 'Does NOT apply to root rust-toolchain.toml (that's for Turbopack)' — that minimizes conflict risk with the related Turbopack toolchain skill.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

vercel/next.js

Path

.agents/skills/next-rspack/SKILL.md

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.