CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vibe-code-auditor

Audit rapidly generated or AI-produced code for structural flaws, fragility, and production risks.

Quality

69%

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 ./skills/vibe-code-auditor/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 dense, disciplined audit framework with genuinely executable heuristics, a mechanical scoring system, and strong anti-hallucination guardrails — no filler or concept lectures. Its weaknesses are structural: redundant detection hints repeated across sections and a fully inlined 325-line taxonomy that progressive disclosure would move into reference files.

Suggestions

Consolidate duplicated detection hints: keep the Pattern Recognition Shortcuts table as the single detection surface and remove the overlapping 'Quick checks' lines in dimensions 3, 4, and 5 (bare excepts, eval/exec, hardcoded credentials each appear 2-3 times).

Move the seven dimension issue catalogs and the full report template into one-level-deep reference files (e.g., references/dimensions.md, references/report-template.md), leaving SKILL.md a lean overview that links to them.

Fix the broken nested code fence in the Critical Issues template (the inner 'Code Fix' block prematurely closes the outer fence, lines 216-226) and move the 'Task-Specific Inputs' ask-first section before the Audit Dimensions so the execution order reads top-to-bottom.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and mostly earns its tokens, but it could be tightened: detection hints are duplicated between the 'Pattern Recognition Shortcuts' table and the per-dimension 'Quick checks' (bare excepts, eval/exec, hardcoded credentials each appear two to three times), and the 'Task-Specific Inputs' section overlaps the Pre-Audit Checklist's missing-context handling. This is anchor 3 (mostly efficient, could be tightened) rather than anchor 4's 'minor instances'.

3 / 5

Actionability

Highly executable guidance throughout: exact search strings ('f"SELECT', 'os.system()'), severity tags, a mechanical point-deduction scoring algorithm, effort scale (S/M/L), and a mandatory report template with 'Do not omit sections'. It stops short of anchor 5 only because no worked example of a filled-in finding or report is provided — the template is a skeleton, not a demonstrated output.

4 / 5

Workflow Clarity

A coherent pipeline is present: 60-second quick scan, then pattern-first dimension analysis, then a fixed report format, with calibration rules by code size and explicit checkpoints ('Do not invent findings', 'state what is absent and proceed', 'Skip dimensions that are not applicable'). This is a read-only audit so the destructive-operation validation cap does not apply; the gap keeping it from 5 is that the 'Before auditing, ask' inputs section appears at the end of the document, after the output spec, slightly blurring the execution sequence.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so all 325 lines — the pattern table, all seven dimension catalogs, the report template, and the scoring rubric — are inlined in a single file. Internal sectioning is good with clear headers, matching anchor 3's 'some structure but content that should be separate is inline': the dimension checklists and output template are strong candidates for one-level-deep reference files to keep SKILL.md a lean overview.

3 / 5

Total

14

/

20

Passed

Description

61%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 concise, third-person description with a clear domain and concrete risk categories, but it omits any 'Use when...' trigger clause and most of the skill's actual capabilities (scoring, prioritized fixes, report format). It reads as a competent one-liner that would benefit from an explicit trigger sentence.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user mentions vibe coding, AI-generated code, prototype-to-production hardening, or suspected technical debt in rapidly built systems.'

Enumerate 2-3 more concrete capabilities so specificity reaches anchor 4-5, e.g., '...rates production readiness 0-100 and lists prioritized fixes.'

Include natural synonyms users would say — 'vibe coding', 'technical debt', 'production-ready' — to strengthen trigger-term coverage beyond the current set.

DimensionReasoningScore

Specificity

The description names its domain ('rapidly generated or AI-produced code') and concrete evaluation targets ('structural flaws, fragility, and production risks'), but relies on a single action verb — capabilities like the production-readiness score, refactoring priorities, and report generation are never stated. This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than anchor 4's several specific actions.

3 / 5

Completeness

The 'what' is clear (audit AI-generated code for structural flaws, fragility, and production risks), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'when' is only weakly implied by 'rapidly generated or AI-produced'. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Phrases like 'Audit ... code', 'AI-produced', 'fragility', and 'production risks' are terms users naturally say when needing this skill. It falls short of anchor 5 because common synonyms such as 'vibe coding', 'technical debt', 'production-ready', and 'code review' are absent — notably 'vibe' never appears in the description despite being the skill's name.

4 / 5

Distinctiveness Conflict Risk

The qualifier 'rapidly generated or AI-produced code' carves out a distinct niche from general code review, giving minor overlap risk with closely related skills (code review, security audit). It is not anchor 5 because the description itself doesn't state what separates it from an ordinary code audit — the differentiation lives in the body, not the description.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

skills/vibe-code-auditor/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.