CtrlK
BlogDocsLog inGet started
Tessl Logo

python-review

Python code review guidelines for the Cog SDK

56

Quality

63%

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

Quality

Content

78%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.

A tight, well-structured review checklist that assumes Claude's competence and gives specific, file-level guidance without padding. Its only gaps are the absence of an explicit findings-validation step and any concrete code snippets.

DimensionReasoningScore

Conciseness

Lean bullet structure with no concept padding (no "what is Python" filler); only minor introductory clauses could be trimmed, fitting the "efficient; minor over-explanation" anchor.

4 / 5

Actionability

Concrete, specific guidance names exact files (base_predictor.py, python/cog/server/) and exact rules (no bare except:, from __future__ import annotations, support 3.10–3.13); as an instruction-only skill it lacks copy-paste examples, keeping it at 4.

4 / 5

Workflow Clarity

A single-purpose read-only review organized into clearly-labeled categories with an unambiguous action; no destructive/batch ops trigger the cap-3 rule, but there is no explicit verify-findings checkpoint, so it stops at 4.

4 / 5

Progressive Disclosure

Under 50 lines, no external references or bundle files needed, and well-organized into labeled sections, matching the under-50-lines exception for a 5.

5 / 5

Total

17

/

20

Passed

Description

48%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 identifies a clear, specific niche but is phrased as a passive noun phrase with no explicit trigger guidance and only generic action language. Adding a "Use when..." clause and concrete review actions would substantially raise its score.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when reviewing changes to the Cog SDK Python code under python/cog/." to fix the missing trigger guidance that caps completeness at 3.

Replace the generic noun "code review guidelines" with concrete actions, e.g. "Reviews Cog SDK Python code for type-annotation correctness, Python 3.10–3.13 compatibility, async pitfalls, and backward-compatible predictor-interface changes."

Include natural trigger synonyms users actually say ("review my Python code", "lint Cog SDK changes", "check type annotations") to broaden trigger-term coverage beyond "code review".

DimensionReasoningScore

Specificity

The phrase "Python code review guidelines" names the domain (Python/Cog SDK) but states no concrete review actions, reading as a generic noun phrase rather than a list of capabilities.

2 / 5

Completeness

It clearly states the "what" (Python code review for the Cog SDK) but has no "Use when..." clause, so completeness is capped at 3 per the missing-trigger guideline.

3 / 5

Trigger Term Quality

"Python", "code review", and "Cog SDK" include the natural phrase users say, but common synonyms like "lint" or "check my code" are absent.

3 / 5

Distinctiveness Conflict Risk

The "Cog SDK" qualifier plus "Python" carves a mostly-distinct niche with only minor overlap risk against generic Python-review skills.

4 / 5

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
replicate/cog
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.