CtrlK
BlogDocsLog inGet started
Tessl Logo

rendered-pack-3252bc08

Use BEFORE changing deps in publishable MoltNet packages: public in-repo @themoltnet/* deps use workspace:* for pnpm publish rewrite; private @moltnet/* bundled by Vite SSR stay in devDependencies; check release-please lockfile drift.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

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.

The body is an efficient, actionable ruleset with a concrete verification workflow and clear sectioning. It stays just below top marks because of the non-essential Provenance token cost and incompletely specified error-recovery loops.

Suggestions

Trim or collapse the Provenance UUID list (or move it to a reference file) to recover tokens that do not aid execution.

Add an explicit fix-and-retry loop for the failure patterns (e.g., when check:pack flags a private dep leak or lockfile drift, state the corrective next step) to push workflow clarity higher.

Move the Failure Patterns detail into a separate reference file and link to it from the rules, keeping SKILL.md as a tighter overview.

DimensionReasoningScore

Conciseness

Lean rule statements with brief rationale assume Claude's competence and avoid explaining basics, though the Provenance UUID list and the dense rule 5 add some non-essential tokens.

4 / 5

Actionability

Concrete commands and config keys ('pnpm install --frozen-lockfile', 'check:pack', 'build.rolldownOptions.external', 'externalizeInstallableDependencies') give mostly executable guidance with minor gaps.

4 / 5

Workflow Clarity

Rule 6 sequences verification (check:pack, frozen-lockfile, lockfile-drift inspection, clean packed install) with most validation checkpoints present, but error-recovery feedback loops are only partly spelled out.

4 / 5

Progressive Disclosure

Well-organized into Rules / Failure Patterns / Provenance with no nested references and no bundle files, though the single-file layout keeps some content inline that could be split out.

4 / 5

Total

16

/

20

Passed

Description

87%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 is specific, complete, and well-triggered for a narrow niche, clearly stating both the when and the what with concrete technical actions. It is slightly jargon-heavy, which keeps trigger-term quality and specificity just below the top anchor.

DimensionReasoningScore

Specificity

Lists several concrete actions ('public in-repo @themoltnet/* deps use workspace:* for pnpm publish rewrite', 'private @moltnet/* bundled by Vite SSR stay in devDependencies', 'check release-please lockfile drift') with minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (the three dependency rules) and when ('Use BEFORE changing deps in publishable MoltNet packages') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Good keyword coverage of the niche ('changing deps', 'publishable MoltNet packages', 'workspace:*', 'Vite SSR', 'release-please', 'lockfile drift'), though jargon-heavy and missing common synonyms.

4 / 5

Distinctiveness Conflict Risk

Highly specific niche (publishable MoltNet packages, release-please, Vite SSR) gives a clear trigger with minimal conflict risk against unrelated skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
getlarge/themoltnet
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.