CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-review-ai-ai-review

You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

42%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 offers a genuinely comprehensive review playbook with useful checklists and some runnable commands, but it is padded with known-concept explanations and boilerplate sections, and its flagship code examples are non-executable illustrations. Splitting reference material into bundle files and trimming filler would substantially improve it.

Suggestions

Move the full CI/CD GitHub Actions workflow, the Python orchestrator example, and the security/performance checklists into files under references/, keeping SKILL.md as a concise overview with clearly signaled links.

Cut sections restating common knowledge (SOLID principles, the OWASP Top 10 list) and the filler "Use this skill when" / "Do not use this skill when" / "Instructions" / "Summary" boilerplate.

Make the orchestrator example executable (define get_pr_diff() and to_github_comment()) or explicitly label it as pseudocode, and remove version-year-pinned model recommendations ("Model Selection (2025)") that will become stale.

DimensionReasoningScore

Conciseness

The ~450-line body contains several padded sections ("Use this skill when", "Do not use this skill when", generic "Instructions" bullets, a "Summary" restating the entire document) and explains concepts Claude already knows (SOLID principles, the OWASP Top 10 listing, N+1 queries), plus time-sensitive content ("Model Selection (2025)", "OWASP Top 10 (2025)") that will age. Not 1: the core workflow sections are genuinely instructive rather than tutorial-style concept explanation.

2 / 5

Actionability

Concrete, runnable commands exist (the trufflehog secret-scanning pipeline, the semgrep/codeql steps in the GitHub Actions YAML), but the centerpiece examples are illustrative rather than executable: the Python orchestrator calls undefined methods (get_pr_diff(), issue.to_github_comment()) and ReviewRoutingStrategy references undefined engine classes. The "Local execution boundary" section explicitly flags examples as illustrative, which prevents a lower score. Not 4: key examples would not run as written.

3 / 5

Workflow Clarity

A clear multi-step sequence is present (Initial Triage with 4 numbered steps → Multi-Tool Static Analysis → AI-Assisted Review → structured Comment Generation) and a CI quality gate ("if [ $CRITICAL -gt 0 ]; then exit 1") provides one explicit checkpoint. However, there are no validate→fix→retry feedback loops between stages, and handoffs (e.g., triage results feeding the AI review) are implicit. Not 4: checkpoints are mostly missing or implicit outside the final gate.

3 / 5

Progressive Disclosure

Section headers are clear and navigation within the file is reasonable, but all content is inlined in a single ~450-line SKILL.md with zero bundle files ("no additional playbook is bundled"); the full CI/CD GitHub Actions workflow, the complete Python orchestrator script, and the security checklists clearly belong in separate reference files. Not 2: the structure is present and well-organized, not minimal; not 4: nothing is split out, so the main file carries everything.

3 / 5

Total

11

/

20

Passed

Description

40%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 truncated, second-person persona statement dominated by buzzwords. It conveys the general domain (AI-assisted code review) but names no concrete actions, provides no use-when triggers, and cuts off mid-tool-list.

Suggestions

Rewrite in third person with concrete actions, e.g. "Reviews pull requests and diffs for security, performance, architecture, and maintainability issues using static analysis (CodeQL, Semgrep, SonarQube) and AI-assisted contextual review."

Add an explicit trigger clause: "Use when asked to review code, a pull request, or a diff, or when setting up automated code review in CI/CD pipelines."

Remove buzzword padding ("intelligent pattern recognition", "modern DevOps practices") and complete the truncated tool list so the description is a valid, self-contained sentence.

DimensionReasoningScore

Specificity

Second-person persona text ("You are an expert AI-powered code review specialist") uses abstract phrases like "intelligent pattern recognition, and modern DevOps practices" and names no concrete actions; base level 2 (domain named, actions generic) reduced by 1 for second-person voice per the rubric guideline. The description is also truncated mid-sentence ("GPT-5, C"), leaving the capability list incomplete.

1 / 5

Completeness

The 'what' is stated (AI-assisted code review combining static analysis tools), but there is no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline. Not 2: the 'what' is genuinely present rather than vague-only; not 4: the 'when' is entirely absent and the text cuts off mid-sentence.

3 / 5

Trigger Term Quality

Contains some natural keywords ("code review", "static analysis") and tool names users might mention (GitHub Copilot, Qodo, GPT-5), but misses common variations users would actually say such as "review my PR", "pull request", "diff", or "find bugs". Not 4: coverage is partial and buried in marketing-fluff phrasing.

3 / 5

Distinctiveness Conflict Risk

"AI-powered code review specialist" carves out a recognizable niche, but the description overlaps with generic code-review and security-review skills since no distinct triggers or scoped boundaries differentiate it. Not 4: nothing signals when this skill should win over a plain code-review skill.

3 / 5

Total

10

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/ai_review.py)

Warning

Total

14

/

16

Passed

Repository

BigSimmo/Communication

Path

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