CtrlK
BlogDocsLog inGet started
Tessl Logo

repo-auditor

Skill de auditoria inicial e continua do repositorio. Use quando precisar mapear stack real, convencoes, assets, testes, docs, riscos e pontos de integracao antes de executar outras skills. O resultado deve ser persistido em markdown reutilizavel para reduzir releitura e economizar tokens. Trigger em: "repo audit", "auditar repositorio", "mapear stack do projeto", "harnessability score", "repo-audit", "auditoria de repo", "fotografia do repo", "current.md", "mapear convencoes do projeto", "inventariar o codebase".

64

Quality

77%

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/18-repo-auditor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

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

A detailed, highly actionable audit skill whose dense tables carry most of the value. It is let down by verbose conceptual asides, a missing validation loop for batch split generation, and inline material that would benefit from being split into reference files.

Suggestions

Trim conceptual/sourcing asides (Böckeler inspiration note, AGPL justification, 'modelo conceitual' caveat) to lift conciseness toward 3.

Add an explicit validation step after split generation (e.g. verify each split is non-empty and its pointers resolve) to give the batch output a feedback loop.

Move the harnessability scoring model and the recommend-automation mode into reference files referenced from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient thanks to dense signal-detection tables, but explanatory asides add padding ('Inspirado em Birgitta Böckeler...', the AGPL licensing justification, 'Este é um modelo conceitual...') that Claude does not need.

2 / 3

Actionability

Highly actionable: concrete detection patterns ('tsconfig.json strict:true', 'Cargo.toml', 'app.get/post/put/delete', 'schema.prisma'), explicit persistence paths, and a split catalog with 'Gerar quando detectar' conditions.

3 / 3

Workflow Clarity

Sequence (audit -> persist -> splits -> handoff) and a completion checklist exist, but generating multiple split files is a batch operation with no explicit validate/verify feedback loop, capping this dimension at 2.

2 / 3

Progressive Disclosure

External references are one level deep and signaled ('apenas quando necessario'), but no bundle files exist and the inline harnessability scoring model plus the full recommend-automation mode are content that could live in separate reference files.

2 / 3

Total

9

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 strong description: concrete actions, explicit 'Use when' and 'Trigger em' guidance, and broad natural trigger terms. Only weakness is the second-person imperative voice, which costs one specificity point per the rubric.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('mapear stack real, convencoes, assets, testes, docs, riscos e pontos de integracao', 'persistido em markdown reutilizavel'), but the second-person imperative voice 'Use quando precisar' is penalized by one level per the guidelines.

2 / 3

Completeness

Explicitly answers both what ('auditoria inicial e continua do repositorio') and when ('Use quando precisar mapear stack real...' plus the 'Trigger em:' list).

3 / 3

Trigger Term Quality

The 'Trigger em:' clause gives broad natural-term coverage ('repo audit', 'auditar repositorio', 'mapear stack do projeto', 'fotografia do repo', 'inventariar o codebase') that users would plausibly say.

3 / 3

Distinctiveness Conflict Risk

Clear niche (repository audit/photography) with distinct, specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
felvieira/claude-skills-fv
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.