CtrlK
BlogDocsLog inGet started
Tessl Logo

comprehensive-review-full-review

Use when working with comprehensive review full review

60

1.13x
Quality

44%

Does it follow best practices?

Impact

85%

1.13x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/comprehensive-review-full-review/SKILL.md

The canonical home for this skill is comprehensive-review-full-review in sickn33/agentic-awesome-skills

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.

The body is a well-structured, actionable multi-phase review workflow with concrete agent prompts, but it carries some boilerplate padding and a broken reference to a non-existent playbook file.

Suggestions

Create the referenced resources/implementation-playbook.md or remove the dangling reference, and move the large per-phase prompts into a separate reference file to better follow progressive disclosure.

Trim the generic 'Use this skill when' / 'Do not use this skill when' boilerplate and the tautological intro to reduce token overhead.

Add an explicit validation/feedback step (e.g., verify findings are reproducible before promoting them to P0/P1) to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The phase content is mostly efficient and actionable, but the boilerplate 'Use this skill when' / 'Do not use this skill when' sections and the tautological intro line add padding that could be trimmed.

3 / 5

Actionability

Each phase supplies concrete Task-tool invocations with named subagent_type values and copy-paste-ready prompts plus expected outputs, with only minor gaps around whether the named agents actually exist.

4 / 5

Workflow Clarity

Phases 1-4 are clearly sequenced with parallel/parallel-into-serial dependencies and explicit context-passing variables, plus a success-criteria checkpoint; it falls short of 5 because there is no explicit validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

The body has good section headers and structure, but the only reference (resources/implementation-playbook.md) does not exist and no bundle directories are present, so content that could live in separate files is inlined.

3 / 5

Total

14

/

20

Passed

Description

25%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 a vague, tautological template artifact that states when to use the skill but never says what it does, leaving it indistinct from any other review skill.

Suggestions

Replace the description with a concrete statement of what the skill does (e.g., 'Orchestrates a multi-phase code review across quality, security, performance, testing, documentation, and CI/CD dimensions').

Add explicit natural trigger phrases users would say, such as 'comprehensive code review', 'multi-dimensional review', or 'review for security and performance issues'.

Ensure the description answers both 'what' and 'when' in third person without redundant wording like 'full review'.

DimensionReasoningScore

Specificity

The description only names a domain ('comprehensive review full review') with no concrete actions stated; it is below the midpoint because the domain itself is tautological and action coverage is effectively zero.

2 / 5

Completeness

Only a vague 'when' ('Use when working with...') is present with no 'what' describing what the skill does, matching the 'only when is present without what' anchor.

2 / 5

Trigger Term Quality

Phrases like 'comprehensive review full review' are generic and redundant; they miss the natural trigger terms a user would actually say, fitting the 'one or two generic keywords' anchor.

2 / 5

Distinctiveness Conflict Risk

The phrase is very broad and bounded only loosely to 'review', giving it high overlap risk with many similar review skills.

2 / 5

Total

8

/

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.

Validation15 / 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
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.