CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

named-persona-adversarial-review

Code review through the lens of real engineers' documented philosophies (Torvalds, Thompson, Carmack, Kent Beck, Jobs, Cagan). Complements abstract-role adversarial review with named, sourced perspectives. Use when automated review findings feel generic, when a PR has architectural or UX impact, or when the author wants pre-submit hardening beyond standard checks.

69

Quality

87%

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

The canonical home for this skill is named-persona-adversarial-review in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

An unusually actionable instruction-only skill: concrete persona selection rules, routing, severity semantics, an example output block, an explicit integrity checklist, and exit conditions with feedback loops. Its two weaknesses are redundancy (the anti-fabrication rule and several Rules/Anti-Patterns entries repeat) and the missing references/persona_principles.md file the entire workflow depends on.

Suggestions

Ship references/persona_principles.md with the bundle (or inline a minimal sourced-principles table): the body cites it 6+ times as mandatory grounding for Steps 1-2, but the file is absent, so the workflow's load-bearing step cannot be executed as packaged.

Consolidate the duplicated honesty rules: the anti-fabrication/no-quote-invention guidance appears in Attribution discipline, Rules, the Anti-Patterns table, and the Integrity check — state it once authoritatively and cross-reference it to save tokens.

Trim the 'Theory' cross-reference (de Bono, Kahneman) and fold the Anti-Patterns rows that restate Rules verbatim ('Fabricating a finding to hit ≥1 issue', 'Product person skipped') into the Rules section only.

DimensionReasoningScore

Conciseness

The body is dense and organized with no explanation of concepts Claude already knows, and the example output, routing, and severity tables each earn their tokens. However, the anti-fabrication rule is stated four times (Attribution discipline items 1 and 3, Rules, the Anti-Patterns table, and the Integrity check), several Anti-Patterns rows duplicate Rules verbatim, and the 'Theory' citation (de Bono, Kahneman) is padding — more than minor trimming available, so anchor 4 fits better than 3.

4 / 5

Actionability

Fully concrete instruction-only guidance: exact persona counts ('pick 2 per round' engineers plus 1 mandatory product persona), a routing table by problem type, severity definitions each with a required action, a copy-ready example output block, a quantified zero-finding burden ('3+ principles the code demonstrably satisfies'), and a default output destination ('.claude/review-[timestamp].md'). Covers the common cases completely — anchor 5.

5 / 5

Workflow Clarity

Clear sequence (Step 0 read twice → Step 1 ground principles → Step 2 review → Step 3 synthesize and post) with explicit validation checkpoints: the Integrity Check is a 4-item checklist run after each round, and the Exit Conditions define feedback loops (BLOCKER/CRITICAL → fix → 1 re-review round; CLEAN on 2 consecutive rounds → done). This is a review process, not a destructive/batch operation, so no cap applies — anchor 5.

5 / 5

Progressive Disclosure

References are well-signaled and one level deep ([references/persona_principles.md] linked from multiple sections, cross-references to sibling skills), and persona detail is appropriately split out of SKILL.md rather than inlined. However, that reference file — cited 6+ times as the load-bearing grounding resource required by Step 1 and Rule 1 — is not present in the bundle, leaving the skill's core dependency unshipped. Good structure with a real gap: anchor 4, not 5.

4 / 5

Total

18

/

20

Passed

Description

83%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 description: concrete what, explicit multi-scenario when, and clear self-positioning against the sibling adversarial-review skill. Its weaknesses are modest — a few natural trigger synonyms are absent, and one 'when' clause is broad enough to overlap generic code-review skills.

DimensionReasoningScore

Specificity

Names the domain (code review), the method (persona lenses), and specific personas ("Torvalds, Thompson, Carmack, Kent Beck, Jobs, Cagan"), plus a concrete complementary capability ("Complements abstract-role adversarial review with named, sourced perspectives"). Falls between anchor 3 and anchor 4: several specifics are present, but they describe one core action framed multiple ways rather than a list of distinct operations — noticeably above the midpoint, short of comprehensive.

4 / 5

Completeness

Explicitly answers both: what ("Code review through the lens of real engineers' documented philosophies") and when (an explicit 'Use when...' clause with three concrete trigger scenarios). This mirrors the anchor-5 good example's structure; the 'when' is fully explicit with concrete trigger phrases, so 4 (when only 'could be more explicit') does not fit.

5 / 5

Trigger Term Quality

"Use when automated review findings feel generic, when a PR has architectural or UX impact, or when the author wants pre-submit hardening beyond standard checks" supplies natural trigger scenarios plus keywords (code review, PR, UX, pre-submit hardening). A few natural terms are missing — 'pull request' spelled out, persona names, or 'senior-engineer review' as user phrasings — so anchor 4 fits better than 5.

4 / 5

Distinctiveness Conflict Risk

The named-persona niche is distinct and the description explicitly positions it against its sibling ("Complements abstract-role adversarial review"), giving minimal confusion risk there. Minor overlap remains: 'when a PR has architectural or UX impact' is broad enough to also match generic code-review skills — anchor 4, not 5.

4 / 5

Total

17

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing, 4 suspicious

Warning

referenced_paths_exist

Referenced path issues: 10 missing

Warning

Total

14

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/named-persona-adversarial-review/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.