CtrlK
BlogDocsLog inGet started
Tessl Logo

vanity-engineering-review

Reviews codebases, architectures, PRs, and technical plans for vanity engineering — code and systems built for the developer's ego, resume, or intellectual pleasure rather than delivering user or business value. Triggers on: "review this code", "is this over-engineered", "code review", "architecture review", "complexity audit", "vanity check", "is this necessary", "simplify this", "tech debt review", or any request to evaluate whether code or architecture is justified by actual requirements. Also trigger when the user shares a codebase and asks for feedback, when discussing framework/library choices, when reviewing PRs, or when someone is debating whether to refactor or rebuild. Nudge activation when you detect patterns of unnecessary abstraction, premature optimization, or resume-driven technology choices in code the user shares — even if they haven't asked for a vanity review.

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-structured, actionable review skill with a clear phased workflow and good progressive disclosure into two real reference files. The main weakness is conciseness: several philosophical asides could be trimmed to respect the context budget.

Suggestions

Trim philosophical elaboration (e.g., the sunk-cost/addition-bias paragraph and lines like 'It may feel productive. It is not.') to tighten the body without losing the diagnostic frame.

Consider moving the full Kill Criteria Philosophy tiers into the existing kill-criteria reference file to keep SKILL.md focused on the review process.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence, but padded with philosophical prose ('entropy disguised as craftsmanship', the sunk-cost/addition-bias explanation) that could be tightened without losing diagnostic value.

2 / 3

Actionability

Provides concrete, actionable guidance: a 4-phase process, a V0–V3 severity scale, an RCR scoring scale, a structured output template with explicit fields, and diagnostic lenses with specific test questions.

3 / 3

Workflow Clarity

Clear sequenced 4-phase workflow (Establish Requirement Anchor → Detection Scan → Vanity Score → Kill Criteria Generation) with a Phase 1 checklist of five questions and a Phase 3 output template that functions as a checklist.

3 / 3

Progressive Disclosure

Body is an overview that inline-signals two one-level-deep references ('references/detection-patterns.md', 'references/kill-criteria-template.md'), both verified to exist, with detail appropriately split out.

3 / 3

Total

11

/

12

Passed

Description

92%

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, specific description with explicit trigger guidance and good natural-language keyword coverage. Its main weakness is overlap risk: several trigger terms are generic enough to compete with ordinary code-review and simplification skills.

Suggestions

Tighten generic triggers like 'code review' and 'simplify this' by qualifying them toward vanity/over-engineering (e.g., 'code review focused on over-engineering') to reduce conflict with general review skills.

Consider leading with the distinctive vanity-engineering framing before the trigger list so the niche is unmistakable on first read.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Reviews codebases, architectures, PRs, and technical plans for vanity engineering' — naming both the artifacts reviewed and the specific failure mode detected, rather than vague language.

3 / 3

Completeness

Clearly answers both what (reviews for vanity engineering) and when, with an explicit 'Triggers on:' clause and additional 'Also trigger when...' and 'Nudge activation when...' guidance.

3 / 3

Trigger Term Quality

Provides broad coverage of natural phrases users would say ('review this code', 'is this over-engineered', 'simplify this', 'tech debt review', 'vanity check'), plus situational triggers like sharing a codebase for feedback.

3 / 3

Distinctiveness Conflict Risk

The vanity-engineering niche is distinct, but several triggers ('code review', 'tech debt review', 'simplify this') are generic and would overlap with general code-review and refactoring skills, risking activation for the wrong skill.

2 / 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
bencium/bencium-marketplace
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.