CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rendered-pack-5bf21e8c

Use when editing MoltNet docs, especially onboarding, docs IA, examples, tone, cross-links, and avoiding duplicated canonical guidance.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/rendered-pack-5bf21e8c/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 genuinely actionable, well-sequenced docs-review workflow with explicit validation checkpoints and a fallback path, undermined by a large inlined context-pack appendix of historical commit entries and provenance metadata. The pack material dilutes token efficiency and bypasses progressive disclosure entirely.

Suggestions

Move the 9 context-pack entries into a single references file (e.g. references/context-pack.md) and keep a one-line pointer in SKILL.md, restoring progressive disclosure.

Trim provenance metadata (CIDs, token counts, timestamps, branches, signers) and reframe the three 'Accountable commit' entries as concise guidance rules rather than dated commit narratives.

Add a short section explaining when to consult each pack entry type (tone rule, IA rule, commit pattern) so the appendix has a clear navigation path from the workflow.

DimensionReasoningScore

Conciseness

The workflow section is mostly efficient, but the appended 9-entry context pack carries substantial non-actionable payload — entry IDs, CIDs, token counts, timestamps, branches, signers, and dated commit narratives ('Accountable commit: Restructure docs/use/tasks', 'PR #1137'). It is above the 2 anchor because the pack entries do contain the actual guidance payload rather than pure padding, but well below 5 given the provenance metadata and historical commit logs that could be trimmed.

3 / 5

Actionability

As an instruction-only skill the guidance is concrete and directive: 'Start the subagent without inherited conversation history (fork_turns: "none" when supported)', 'record its first-read questions before inspecting code', 'prefer one canonical flow over a parallel page', plus real validation commands ('nx docs lint, typecheck, and build', 'pnpm --filter @moltnet/docs build'). It misses 5 because several pack entries are descriptive commit history rather than instructions, and referenced artifacts like the 'copy-pasteable prompt template' are not actually included.

4 / 5

Workflow Clarity

The fresh-reader pass is a clear 5-step numbered sequence with explicit checkpoints — read-before-research (step 2), verify-against-source before publishing (step 5) — and an explicit fallback loop ('If fresh subagents are unavailable, perform the reader-focused pass directly and state that it was not an independent review'). It does not reach 5 because the document as a whole offers no guidance on when or how to apply the appended context-pack entries relative to the workflow.

4 / 5

Progressive Disclosure

The body does signal its two-part structure ('This is repository-maintained workflow guidance, separate from the bundled context-pack entries below') and each pack entry has a header, giving some structure. However, there are no bundle files or one-level-deep references at all — the entire 9-entry context pack is inlined in SKILL.md, which is content that clearly belongs in a separate reference file, matching the 3 anchor ('content that should be separate is inline') rather than the 4 anchor's 'most content appropriately placed'.

3 / 5

Total

14

/

20

Passed

Description

66%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 tightly scoped, in-niche description with a strong explicit 'Use when' trigger clause and specific focus areas, but it never states what the skill actually does when invoked. Adding a leading capability statement and a few common synonyms ('documentation', 'README', 'restructure') would lift it substantially.

Suggestions

Prepend a concrete 'what' clause, e.g. 'Applies MoltNet docs conventions and a fresh-reader review pass when editing MoltNet docs…', so both what and when are explicit.

Add natural trigger variations users would actually say — 'documentation', 'README', 'docs restructure', 'docs cleanup' — to broaden keyword coverage.

Clarify the action taken (review/rewrite guidance vs. tone/dedup rules) so it is distinguishable from a generic docs-editing skill.

DimensionReasoningScore

Specificity

The description names the domain ("editing MoltNet docs") and enumerates several concrete focus areas — "onboarding, docs IA, examples, tone, cross-links, and avoiding duplicated canonical guidance" — which is well above the 3 anchor's '1-2 concrete actions'. It falls short of 5 because the only stated action is 'editing'; the enumerated items are topic areas rather than a comprehensive set of concrete actions the skill performs.

4 / 5

Completeness

The 'when' is explicit and strong ("Use when editing MoltNet docs, especially..."), but the 'what' — what the skill actually does — is never stated; it is only weakly implied by the list of concern areas. This mirrors the 3 anchor (one half clear, the other only implied) rather than the 4 anchor, which requires both 'what' and 'when' to be present.

3 / 5

Trigger Term Quality

Natural terms a docs editor would say are present — "onboarding", "tone", "cross-links", "docs IA" — giving good in-niche coverage. It misses common variations a user might naturally say, such as 'documentation', 'README', 'restructure', or 'docs cleanup', so it does not reach the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The product-specific "MoltNet docs" qualifier carves out a clear niche with distinct triggers (onboarding, tone, cross-links, canonical-guidance dedup), making wrong-skill triggering unlikely. It stays at 4 rather than 5 because the description would still overlap with a generic documentation-editing skill covering the same docs areas.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

getlarge/themoltnet

Path

.agents/skills/rendered-pack-5bf21e8c/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.