CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

comprehensive-review-full-review

Coordinate code quality, architecture, security, performance, testing, and documentation reviews. Use when a change or codebase needs a consolidated assessment across these areas.

Quality

68%

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

Quality

Content

50%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 skill presents a well-sequenced four-phase review workflow with concrete per-agent prompts, configuration flags, and a prioritized reporting taxonomy. Its weaknesses are uniform: boilerplate padding, undefined context placeholders with no executable mechanics, absent inter-phase validation checkpoints, and a monolithic single-file layout with no reference files.

Suggestions

Trim the circular "Use this skill when / Do not use" boilerplate, the generic Instructions bullets, and the bracketed "[Extended thinking: ...]" paragraph — they add tokens without guidance.

Define the context placeholders concretely (e.g., specify that {phase1_architecture_context} is the architecture findings summary from 1B) and add per-phase validation checkpoints such as "confirm each phase's expected output exists before proceeding".

Move the six full agent prompts and the P0–P3 report taxonomy into one-level-deep reference files (e.g., references/prompts.md, references/report-format.md), keeping SKILL.md as a compact overview with clearly signaled links.

DimensionReasoningScore

Conciseness

The phase structure and agent prompts are dense and mostly workable, but there is clear padding: the circular boilerplate "Working on comprehensive review full review tasks", the generic Instructions bullets ("Clarify goals, constraints, and required inputs"), and the 80-word bracketed "[Extended thinking: ...]" meta-commentary block. It is tighter than anchor 2's concept-explaining verbosity, but more than minor over-explanation, so it sits at the midpoint.

3 / 5

Actionability

Each phase gives a named Role, a specific prompt (e.g., "Analyze code complexity, maintainability index, technical debt, code duplication..."), and expected output, which is concrete direction for an orchestration skill. However, the context placeholders ({phase1_architecture_context}, {all_previous_contexts}) are never defined, no commands or tool invocations are given, and how to actually dispatch the agents is left implicit — key details are missing, matching the incomplete-guidance anchor.

3 / 5

Workflow Clarity

The four phases are clearly sequenced with explicit parallelism ("Run the quality and architecture reviews below, in parallel") and explicit cross-phase dependencies ("Incorporates architectural vulnerabilities identified in Phase 1B"). But there are no validation checkpoints between phases — no instruction to verify a phase's output before feeding it forward — and the success criteria are end-state goals rather than per-step gates, matching the "sequence present but checkpoints missing or implicit" anchor.

3 / 5

Progressive Disclosure

The body has clear section headers and a logical layout, but at ~145 lines everything is inline: the six long copy-paste agent prompts and the P0–P3 report taxonomy are content that could live in one-level-deep reference files. No references/ files exist in the bundle, so there is no progressive disclosure at all — better organized than anchor 2's unstructured wall, but short of anchor 4's appropriately split content.

3 / 5

Total

12

/

20

Passed

Description

71%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 solid description with an explicit what-and-when structure and good domain coverage across six review dimensions. Its main weaknesses are the generic action verb, an abstract "when" clause lacking concrete trigger phrases, and meaningful overlap risk with single-dimension review skills.

Suggestions

Replace the generic verb with concrete actions, e.g., "Run coordinated code-quality, architecture, security, performance, testing, and documentation reviews and consolidate findings into a prioritized report".

Make the "when" clause use natural trigger phrases, e.g., "Use when the user asks for a full, comprehensive, or multi-dimensional review of a change or codebase rather than a single-dimension review".

Sharpen distinctiveness by signaling it should trigger only when a consolidated/multi-area assessment is wanted, not for focused security or code review requests.

DimensionReasoningScore

Specificity

The description lists six concrete review dimensions ("code quality, architecture, security, performance, testing, and documentation reviews"), giving broad coverage of the domain. It falls short of a 5 because the single action verb "Coordinate" is generic — it names review types rather than multiple distinct concrete actions.

4 / 5

Completeness

Both parts are present: the "what" is "Coordinate code quality, architecture, security, performance, testing, and documentation reviews" and the "when" is the explicit clause "Use when a change or codebase needs a consolidated assessment across these areas". The "when" is abstract and self-referential rather than using concrete trigger phrases, so it does not reach a 5.

4 / 5

Trigger Term Quality

Terms like "security", "performance", "testing", and "reviews" are phrases users would naturally say when requesting this skill, and "a change or codebase" covers the input side. A few natural variants are missing (e.g., "audit", "PR/pull request review", "refactor"), keeping it below a 5.

4 / 5

Distinctiveness Conflict Risk

The multi-dimensional consolidation angle ("consolidated assessment across these areas") is somewhat distinctive, but keywords like "code quality" reviews and "security" reviews overlap heavily with dedicated code-review and security-review skills. It is more prone to overlap than a clear niche, yet not so broad as to conflict with virtually any skill.

3 / 5

Total

15

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

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.