CtrlK
BlogDocsLog inGet started
Tessl Logo

scaffold-docs

Install the RoleModel agent-documentation structure in a project: a minimal AGENTS.md, a docs/ tree with CONVENTIONS.md and INDEX.md, a path-scoped Copilot instructions file, the surface_conventions PreToolUse hook, and the wrap-up skill.

68

Quality

86%

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

88%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 a tightly sequenced, highly executable scaffold workflow with strong validation and feedback loops; its only weaknesses are a few prose passages that could be leaner and template references that do not resolve within the bundle.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence with mostly earned tokens, but a few edge-case prose passages (the check-ignore rationale and the locale-unsetting explanation) could be tightened without losing the gotcha.

4 / 5

Actionability

Fully executable guidance throughout — concrete shell ('mkdir -p .agents/skills', 'ln -s ...', 'git submodule add ...', 'git check-ignore ...'), a complete JSON hook block, and a copy-paste verify invocation with a real printf payload.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit validation in step 7, a real hook-run feedback loop ('run the hook once for real, because every check above is static'), and a merge-don't-clobber guard repeated across destructive file writes.

5 / 5

Progressive Disclosure

Well-signaled one-level-deep references to real bundle files ('follow references/trimming.md', 'Copy assets/surface_conventions.rb'), but the heavily-referenced templates/ directory is not present in the bundle, a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

78%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 precisely names a structured set of installable artifacts and is clearly distinct, but the explicit 'when' trigger guidance lives in a separate metadata.triggers field rather than inline in the description, keeping completeness and trigger_term_quality at 4.

Suggestions

Append an inline 'Use when...' clause to the description field (e.g., 'Use when scaffolding agent docs, bootstrapping an AGENTS.md, or pointing Copilot at repo conventions') so the when-guidance does not depend on the metadata.triggers field.

Lead the description with a couple of active verbs beyond 'Install' (e.g., 'Scaffolds... fills... bridges...') to reach the multi-action specificity anchor.

DimensionReasoningScore

Specificity

Enumerates concrete named artifacts — 'a minimal AGENTS.md, a docs/ tree with CONVENTIONS.md and INDEX.md, a path-scoped Copilot instructions file, the surface_conventions PreToolUse hook, and the wrap-up skill' — under a single install action; falls short of 5 because it uses one verb rather than multiple distinct concrete actions.

4 / 5

Completeness

A clear 'what' is stated inline ('Install the RoleModel agent-documentation structure...') and equivalent explicit 'when' guidance exists via metadata.triggers, but the when-clause is not embedded in the description field, so it is not a 5.

4 / 5

Trigger Term Quality

The sibling metadata.triggers field supplies good natural-term coverage with synonyms — 'scaffold docs, set up AGENTS.md, bootstrap agent docs, trim AGENTS.md, standardize agent instructions' — though a few natural variations are absent and the triggers live outside the description field itself.

4 / 5

Distinctiveness Conflict Risk

A clear niche is named — RoleModel agent-documentation structure, surface_conventions PreToolUse hook, path-scoped Copilot instructions — with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

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

allowed_tools_field

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

Warning

Total

15

/

16

Passed

Repository
RoleModel/rolemodel-skills
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.