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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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 well-structured, highly actionable diagnostic skill with a clear four-phase workflow and clean progressive disclosure via two real reference files. The main weakness is philosophical prose that re-explains concepts Claude already knows.

Suggestions

Tighten or remove the 'Core Premise' and 'Kill Criteria Philosophy' explanatory prose (sunk cost, addition bias, effort justification) since Claude already knows these concepts; keep only the operational framing.

Condense the 'Integration with Negentropy Lens' section to a brief pointer rather than re-explaining the negentropy concepts, or move it to a reference file.

Add an explicit validation/checkpoint between Phase 2 (Detection Scan) and Phase 3 (scoring) so findings are sanity-checked before the structured assessment is produced.

Dimension	Reasoning	Score
Conciseness	The diagnostic guidance is mostly purposeful, but philosophical prose sections ('Core Premise', 'Kill criteria exist because humans are bad at stopping things... sunk cost, addition bias, effort justification') explain concepts Claude already knows and could be trimmed.	3 / 5
Actionability	Provides concrete executable guidance throughout: a 5-question requirement anchor, a V0-V3 severity scale, a fully specified output template, kill-criteria tiers with concrete examples, and 7 diagnostic lenses each with a decision rule.	5 / 5
Workflow Clarity	The review is sequenced into four clear phases (Requirement Anchor, Detection Scan, Vanity Score, Kill Criteria Generation) with concrete steps and an embedded signal check, though no explicit validate-and-retry feedback loop is specified.	4 / 5
Progressive Disclosure	The body is an overview that clearly signals two real, one-level-deep references ('Read references/detection-patterns.md', 'Read references/kill-criteria-template.md'), both of which exist, while keeping core framing inline.	5 / 5
	Total	17 / 20 Passed

Description

91%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 strong, third-person description that clearly states the skill's purpose and supplies an extensive, natural set of trigger phrases. Its only weakness is mild overlap risk from broadly applicable trigger terms.

Dimension	Reasoning	Score
Specificity	Names multiple concrete review targets ('codebases, architectures, PRs, and technical plans') and a precise diagnostic action, but the single verb 'Reviews' applied across targets leaves minor coverage gaps versus a list of distinct actions.	4 / 5
Completeness	Explicitly answers both what ('Reviews codebases... for vanity engineering') and when ('Triggers on: ...' with concrete phrases and nudge-activation conditions), using third person throughout.	5 / 5
Trigger Term Quality	Provides comprehensive natural trigger phrases including synonyms ('review this code', 'code review', 'complexity audit', 'vanity check', 'is this over-engineered', 'simplify this', 'tech debt review') plus situational triggers, covering how users actually phrase the need.	5 / 5
Distinctiveness Conflict Risk	The 'vanity engineering' niche is distinctive, but broad triggers like 'code review', 'review this code', and 'simplify this' create minor overlap risk with general code-review or refactoring skills.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: bencium/bencium-marketplace
Path: vanity-engineering-review/skills/vanity-engineering-review/SKILL.md
Commit: bda4647

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.