CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

performance-testing-review-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

52%

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 ./.agents/skills/performance-testing-review-ai-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 contains genuinely concrete material (scanner commands, CI/CD configuration, a well-specified comment schema) and an unusually good 'Local execution boundary' safety section, but it is bloated with concepts Claude already knows, dated model lists, and large non-executable code blocks that belong in reference files. The workflow is sequenced yet lacks validation feedback loops.

Suggestions

Move the CI/CD YAML, the Python orchestrator, and the language-specific checklists (microservices, security, performance) into files under references/ and keep SKILL.md as a concise overview with clearly signaled links.

Delete the OWASP Top 10 listing, SOLID principles recap, and 'Model Selection (2025)' section — Claude already knows these and the hardcoded model versions are time-sensitive.

Replace the pseudocode routing/orchestrator examples with one small executable procedure, and add explicit validation checkpoints (e.g., confirm SARIF outputs parsed correctly before generating or posting review comments).

DimensionReasoningScore

Conciseness

The ~450-line body re-explains concepts Claude already knows — the full 'OWASP Top 10 (2025)' list, 'SOLID Principles: Single Responsibility, Open/Closed, Liskov Substitution...', and anti-pattern definitions — and includes time-sensitive model/version lists ('Model Selection (2025)', 'claude-3.5-sonnet-20241022', 'GPT-4o-mini') outside any deprecated section. Multiple padded sections ('Context', 'Summary') push this to 'Noticeably verbose', above the severely padded anchor 1 only because much of the content is task-specific rather than tutorial filler.

2 / 5

Actionability

There is concrete guidance — real commands ('trufflehog git file://. --json', 'semgrep scan --config=auto --sarif', a nearly complete GitHub Actions YAML) and a structured ReviewComment format — but the central examples are non-executable: the Python orchestrator calls undefined methods (get_pr_diff(), issue.to_github_comment()), and the TypeScript/Go routing snippets are pseudocode the skill itself flags as 'illustrative roles and examples'. This lands on 'Some concrete guidance but incomplete; pseudocode instead of executable code'.

3 / 5

Workflow Clarity

The 'Initial Triage' steps (1-4) and tool-matching give a recognizable sequence, and the Quality Gate ('if [ $CRITICAL -gt 0 ]... exit 1') is one explicit checkpoint, but there are no validate-fix-retry feedback loops between stages, and the local fallback ('perform the review roles directly in sequence') leaves the actual order implicit. Matches 'Steps listed but validation gaps; checkpoints missing or implicit' rather than anchor 4's 'most checkpoints present'.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent, and the body says 'no additional playbook is bundled'), while roughly 400 lines of CI/CD YAML, Go, TypeScript, and Python reference code are inlined directly in SKILL.md — classic 'content that clearly belongs in separate files is inlined'. The clear section headers keep it above the unstructured anchor 1, but the total inlining with zero one-level-deep references fits anchor 2 better than anchor 3.

2 / 5

Total

10

/

20

Passed

Description

45%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 names a clear domain and real tools, but it is written in second person, leans on buzzwords ('intelligent pattern recognition', 'modern DevOps practices'), is cut off mid-sentence, and provides no trigger guidance for when the skill should be used. It reads as an auto-generated role preamble rather than a skill description.

Suggestions

Rewrite in third person and complete the truncated sentence, e.g. 'Runs multi-tool static analysis (CodeQL, Semgrep, SonarQube) and AI-assisted review of pull requests to produce severity-rated, line-referenced review comments.'

Append an explicit trigger clause such as 'Use when reviewing a pull request, triaging static-analysis findings, or setting up automated code review in CI.'

Replace buzzword phrases ('intelligent pattern recognition', 'modern DevOps practices') with the concrete actions the skill actually performs.

DimensionReasoningScore

Specificity

The description names the domain ('AI-powered code review specialist') and specific tools ('GitHub Copilot, Qodo, GPT-5'), but the actions are generic buzzwords ('automated static analysis, intelligent pattern recognition, and modern DevOps practices') and the text is truncated mid-sentence at 'GPT-5, C'. Base fit is anchor 3 (domain plus 1-2 concrete actions), reduced by 1 because it opens in second person ('You are an expert...') rather than third person.

2 / 5

Completeness

A 'what' is present ('combining automated static analysis... Leverage AI tools'), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3. Not score 2 because the 'what' is identifiable despite being buzzword-heavy and cut off.

3 / 5

Trigger Term Quality

'code review' and 'static analysis' are natural terms users would say, and tool names like 'GitHub Copilot' and 'Qodo' are relevant, but common variations such as 'review my PR', 'pull request review', or 'lint' are absent — matching 'Some relevant keywords but missing common variations or synonyms'. Not score 4 because the truncated tail and buzzword phrasing leave clear gaps in natural trigger coverage.

3 / 5

Distinctiveness Conflict Risk

'AI-powered code review specialist' signals a recognizable niche, but 'code review' broadly overlaps with any general code-review or PR-review skill, and the truncated description offers few distinguishing triggers — 'Somewhat specific but could still overlap with similar skills'. Not score 4 because nothing in the description sharply separates it from a generic review assistant.

3 / 5

Total

11

/

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/performance-testing-review-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.