CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

comprehensive-review-full-review

Use when working with comprehensive review full review

Quality

51%

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 ./.agents/skills/comprehensive-review-full-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-sequenced, honest multi-phase review workflow with concrete delegation prompts, expected outputs, authority/safety boundaries, and a verification-oriented success criteria section. Its main weaknesses are verbatim boilerplate repeated across all eight roles and pseudo-CLI flags plus unsubstituted context placeholders that leave execution details incomplete.

Suggestions

State the delegation fallback once at the top of the phases ("Perform each role directly, or assign it via an available permitted agent tool") and delete the eight verbatim repetitions.

Replace the pseudo-CLI flags with plain English configuration options (e.g. "if the user requested a security focus..." instead of "if --tdd-review flag is set"), and define how the {phase1_architecture_context}-style placeholders are filled in practice.

Consider moving the eight role prompts to a references/ file (one section per role) so SKILL.md stays a lean overview, keeping the phase map, configuration options, success criteria, and limitations inline.

DimensionReasoningScore

Conciseness

The phase structure is mostly efficient, but "Perform this role directly, or assign it through an available permitted agent tool using the role prompt below" is repeated verbatim in all eight roles, and the generic priority lists (e.g. "Compliance violations (GDPR, PCI DSS, SOC2)") plus the long bracketed meta-paragraph add padding that could be tightened. Fits anchor 3 (mostly efficient with some unnecessary repetition) rather than anchor 4's "minor instances".

3 / 5

Actionability

The eight role prompts are concrete, near-copy-paste prompt text with expected outputs, but the --security-focus/--tdd-review/--framework flags are pseudo-CLI options (disclaimed as "workflow preferences rather than a bundled CLI") yet still referenced inside prompts as if settable ("if --tdd-review flag is set", "based on --framework flag"), and the {phase1_architecture_context} placeholders have no substitution mechanics. This lands on anchor 3 (concrete guidance but incomplete, missing key details) rather than 4.

3 / 5

Workflow Clarity

Phases 1–4 are clearly sequenced with explicit inter-phase dependencies ("Incorporates architectural vulnerabilities identified in Phase 1B", "Runs parallel with code quality analysis"), and the Success Criteria section acts as a verification gate ("each finding has source evidence", "record unavailable evidence"). Review work is read-only, so the destructive/batch validation cap does not apply; the absence of explicit validate-fix-retry feedback loops keeps it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The body explicitly states "no additional playbook is bundled" (confirmed: no references/, scripts/, or assets/ exist) and is well-sectioned with clear per-phase headers and consistent role/prompt/output/context structure. Anchor 4 (good structure, content appropriately placed, minor organization gaps) fits — the ~40 lines of role prompts could arguably move to a reference file, but inline is defensible for a single-file orchestration skill.

4 / 5

Total

14

/

20

Passed

Description

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

The description is critically weak: it states only a vague "when" with a garbled, self-repeating domain phrase, gives no indication of what the skill actually does (orchestrating multi-phase code review), and omits every natural trigger term a user would plausibly say. It would rarely be selected correctly and would conflict with other review-related skills.

Suggestions

State the 'what' explicitly, e.g. "Orchestrates a multi-phase code review covering quality, architecture, security, performance, testing, documentation, and CI/CD practices, and consolidates findings into a prioritized report."

Replace the doubled phrase "comprehensive review full review" with natural trigger terms users would actually say: "code review", "review my code", "review this PR/diff", "comprehensive review", "security and performance review".

Keep a concrete "Use when..." clause tied to those triggers, e.g. "Use when the user asks for a thorough or multi-dimension code review of a codebase, PR, or diff."

DimensionReasoningScore

Specificity

The description "Use when working with comprehensive review full review" contains no concrete actions at all — "working with" names no capability, and the doubled domain phrase is itself garbled. It matches anchor 1 (pure abstract language, no concrete actions) rather than anchor 2, which at least names a coherent domain with minimal actions.

1 / 5

Completeness

A "when" clause is present ("Use when working with...") but the "what" is entirely missing — the description never states what the skill does. This is exactly anchor 2 (only "when" present without "what"); anchor 3 requires a clear "what", which is absent.

2 / 5

Trigger Term Quality

Only the two near-duplicate generic keywords "comprehensive review" and "full review" appear; the natural phrases a user would say for this code-review skill ("code review", "review my PR", "review the diff") are absent — the word "code" never appears. Fits anchor 2 (one or two generic keywords, missing natural phrases), not anchor 1 since "comprehensive review" is at least a plausible search phrase.

2 / 5

Distinctiveness Conflict Risk

The generic "review" wording would overlap with virtually any review skill (code review, security review, PR review); only the doubled phrasing hints at a niche, and it does so incoherently. Fits anchor 2 (very broad, high overlap risk with many similar skills) rather than anchor 3's "somewhat specific".

2 / 5

Total

7

/

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

BigSimmo/Communication

Path

.agents/skills/comprehensive-review-full-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.