CtrlK
BlogDocsLog inGet started
Tessl Logo

generate-conventions

Interactively fill a project's docs/conventions/ by proposing candidate rules from taste calls, from the codebase, and from past PR review comments, then writing what's confirmed.

66

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/generate-conventions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 written, well-sequenced workflow with concrete commands, explicit validation/feedback checkpoints, and appropriate one-level reference delegation; its only weakness is that the central taste-proposal task is inherently qualitative, slightly limiting copy-paste actionability.

DimensionReasoningScore

Conciseness

Lean, opinionated prose that assumes Claude's competence with no padding or explanation of basic concepts; every sentence (e.g., 'Skip anything a survey already answers… That's architecture.') earns its place as project-specific calibration.

5 / 5

Actionability

Gives concrete, executable guidance — 'Run `scripts/mine_review_comments.sh` (last 100 merged PRs by default)', 'Ask which they want (`AskUserQuestion`, multi-select)', 'an accurate `<!-- paths: -->` glob' — but the core taste/proposal work is qualitative rather than copy-paste-ready, leaving minor gaps.

4 / 5

Workflow Clarity

A clearly sequenced 6-step process with explicit validation (§6: 'Check that every path resolves, every glob matches something'), a feedback loop (§4 confirm-one-at-a-time: state, get a yes, write, show, next), and a checklist (§3 drop conditions); the destructive/batch cap does not apply since validation is present and batch-writing is explicitly forbidden.

5 / 5

Progressive Disclosure

Well-organized into six labeled sections with one clearly-signaled one-level-deep reference ('Run `scripts/mine_review_comments.sh`', which exists in the bundle); the script's detailed behavior is delegated rather than restated, and no inlined content clearly belongs in a separate file.

5 / 5

Total

19

/

20

Passed

Description

67%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, concrete, and occupies a distinct niche, but it omits any explicit 'Use when…' trigger guidance and relies on metadata.triggers for the natural user phrasings, capping completeness and trigger-term quality.

Suggestions

Add a 'Use when…' clause to the description naming concrete trigger phrases (e.g., 'Use when generating or updating project conventions, or mining past PR review feedback for recurring issues').

Surface a few natural user phrasings ('generate conventions', 'what reviewers keep flagging') inside the description itself rather than only in metadata.triggers.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'fill a project's docs/conventions/', 'proposing candidate rules from taste calls, from the codebase, and from past PR review comments', 'writing what's confirmed' — covering the full generation pipeline comprehensively.

5 / 5

Completeness

Clearly states the 'what' but has no 'Use when…' clause or equivalent trigger guidance; per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant domain keywords ('conventions', 'past PR review comments', 'taste calls', 'codebase') but is missing the natural user phrasings ('generate conventions', 'what do reviewers keep flagging'), which live in metadata.triggers rather than the description.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — generating conventions docs from taste, codebase evidence, and mined PR review comments — with distinct triggers and minimal overlap with other skills.

5 / 5

Total

16

/

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

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.