CtrlK
BlogDocsLog inGet started
Tessl Logo

index-refresh

Use when an LLM Wiki operation issue requests an index refresh. Rebuild `wiki/index.md` from the actual wiki tree, reconcile missing/deleted entries, and log counts without editing page bodies.

75

Quality

92%

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

100%

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

The body is a well-structured, executable index-refresh procedure with concrete templates, clear sequencing, and a verification checklist. It stays lean and appropriately self-contained for a single-task skill.

DimensionReasoningScore

Conciseness

Lean body that never explains concepts Claude already knows; the one framing sentence about the index being the navigation first stop is brief and earns its place.

3 / 3

Actionability

Provides copy-paste-ready templates ("- [[<path>]] — <one-line summary>", log entry blocks) and concrete grouping rules; for an instruction-only skill the guidance is specific and actionable.

3 / 3

Workflow Clarity

A clearly sequenced 9-step workflow with a dedicated Verification checklist and explicit guardrails — validation checkpoints are present for this batch index-rebuild operation.

3 / 3

Progressive Disclosure

A single well-organized SKILL.md with labeled sections (Inputs, Workflow, What this skill does NOT do, Voice, Verification, Tools) and no need for external references; nothing is nested or misfiled.

3 / 3

Total

12

/

12

Passed

Description

85%

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 tight, well-scoped description that states concrete actions and an explicit activation trigger, with low conflict risk. Its only gap is limited variation in natural trigger terms.

Suggestions

Add common phrasings users might say (e.g. "refresh the index", "rebuild the wiki index") alongside "index refresh" to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Rebuild `wiki/index.md` from the actual wiki tree", "reconcile missing/deleted entries", and "log counts" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Rebuild ... reconcile ... log counts without editing page bodies") and when ("Use when an LLM Wiki operation issue requests an index refresh").

3 / 3

Trigger Term Quality

Contains relevant natural terms ("index refresh", "index.md") and an explicit trigger, but offers limited variation coverage compared to the multi-term anchor at level 3.

2 / 3

Distinctiveness Conflict Risk

The narrow LLM-Wiki index-refresh niche with operationType: "index" routing is clearly distinguishable and unlikely to trigger competing skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
paperclipai/paperclip
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.