CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-review-ai-ai-review

Combine static analysis with model-assisted code review to assess security, performance, correctness, and architecture. Use when designing review automation or reviewing complex changes.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/code-review-ai-ai-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 content delivers genuinely actionable, code-heavy guidance organized as a coherent review pipeline, which is its strength. However, it is severely padded with domain knowledge Claude already possesses (OWASP, SOLID, N+1 queries) and time-sensitive model listings, and it inlines everything into one large file instead of splitting detail into reference files.

Suggestions

Cut sections that restate knowledge Claude already has — the OWASP Top 10 list, SOLID principles/anti-patterns, and scalability red flags — and keep only the tool-specific mappings and workflow guidance unique to this skill.

Split the large standalone artifacts (the complete Python orchestrator, the GitHub Actions workflow, the architecture/security checklists) into references/ files linked from a lean SKILL.md overview, one level deep.

Remove the dated, hard-coded model catalog ("GPT-5", "Claude 4.5 Sonnet/Haiku", "Model Selection (2025)") in favor of guidance to select from the account's currently available models, and fix the internally inconsistent model naming.

DimensionReasoningScore

Conciseness

The ~450-line body extensively re-explains concepts Claude already knows: a full OWASP Top 10 (2025) list, SOLID principles and common anti-patterns, scalability red flags like "N+1 Queries" and "Missing Indexes", plus filler sections ("Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes") and tautological use/don't-use lists. It also embeds time-sensitive model names and a dated "Model Selection (2025)" section with inconsistent model IDs ("Claude 4.5 Sonnet" vs "claude-sonnet-4-6") outside any deprecated/old-patterns section, matching the 2 anchor of noticeably verbose with several padded sections rather than the 3 anchor of mostly efficient.

2 / 5

Actionability

Most guidance is concrete: a ready-to-adapt review prompt template, a runnable trufflehog+jq secret-scanning command, a complete GitHub Actions workflow, a structured ReviewComment schema with a worked SQL-injection example, and a near-complete Python orchestrator. It falls short of 5 because several examples rely on undefined pieces (detectsSharedDatabase, AIEngine, issue.to_github_comment(), get_pr_diff()) and the CI workflow invokes scripts/ai_review.py which does not exist in the bundle.

4 / 5

Workflow Clarity

A clear sequence is present — Initial Triage (4 numbered steps) → parallel multi-tool static analysis → AI-assisted review → routing → structured comment generation → CI/CD integration — with an explicit Quality Gate checkpoint that fails the build on CRITICAL issues and JSON-extraction robustness in the orchestrator. Minor validation gaps (no retry/feedback loop when static analysis or the AI call fails) keep it at the 4 anchor rather than 5.

4 / 5

Progressive Disclosure

The file has usable section headers, but it is a single 450-line monolith with zero bundle files: content that clearly belongs in separate references (the complete Python orchestrator example, the CI/CD pipeline YAML, the architecture and security checklists) is fully inlined. This matches the 3 anchor of some structure with content that should be separate inline, rather than the 2 anchor whose example lacks any section headers.

3 / 5

Total

13

/

20

Passed

Description

75%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 that clearly and concisely states what the skill does and when to use it, with good natural trigger terms and a distinct AI-automation niche. Its main weakness is a slightly generic 'when' clause ("reviewing complex changes") that could name more concrete triggers such as pull requests or CI/CD review pipelines.

DimensionReasoningScore

Specificity

"Combine static analysis with model-assisted code review to assess security, performance, correctness, and architecture" names a concrete method and several specific assessment areas. It falls just short of the 5 anchor because it describes one combined action applied to four dimensions rather than multiple distinct concrete actions like "extract text, fill forms, merge documents".

4 / 5

Completeness

Both parts are present: the 'what' ("Combine static analysis with model-assisted code review to assess...") and an explicit 'when' ("Use when designing review automation or reviewing complex changes"). The 'when' could be more specific — "complex changes" is subjective and lacks concrete trigger phrases or synonyms, so it sits at the 4 anchor rather than 5.

4 / 5

Trigger Term Quality

Includes natural phrases users would say — "code review", "review automation", "static analysis", "reviewing complex changes" — matching the 4 anchor of good keyword coverage with a few natural terms missing. Not a 5 because common variations like "pull request", "PR review", or "vulnerability scanning" are absent.

4 / 5

Distinctiveness Conflict Risk

The AI-automation framing ("model-assisted code review", "designing review automation") carves out a clear niche distinct from generic code-review or static-analysis skills. Minor overlap risk remains with closely related skills (e.g., a general code-review or security-review skill), matching the 4 anchor rather than the minimal-conflict 5 anchor.

4 / 5

Total

16

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/code-review-ai-ai-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.