CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

logic-review

Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right",...

Quality

73%

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

Quality

Content

52%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 demonstrates sophisticated domain expertise — detailed format contracts, taxonomy disambiguation, and a well-checkpointed review workflow with adversarial validation. Its two real problems are the missing `logic-review-guide.md`, which the process depends on for key step details, and substantial repetition of the five-field format contract across at least five sections.

Suggestions

Bundle `logic-review-guide.md` (e.g., in references/) or inline the essential content of the guide steps it cites — the premise/type/state checklists (Step 2), the three rebuttal questions (Step 5.5), and the Logic Score formula (Step 7) — since the file is referenced ~15 times but does not exist in the bundle.

Consolidate the five-field label discipline into one authoritative statement (e.g., in the Output Skeleton Contract section) and reference it from Steps 5 and 6 instead of restating the full label list and the 'Divergence is not optional' warning in each place.

Move the four L-code disambiguation paragraphs (L1 vs L6, L2 vs L6, L5 vs L7, L9) into the guide or a reference table; they are valuable but interrupt the Process step sequence and inflate the core SKILL.md token budget.

DimensionReasoningScore

Conciseness

The body is mostly high-value, non-obvious guidance (L-code disambiguation rules, formatting pitfalls tied to specific eval failures) and does not explain concepts Claude already knows. However, the five-field label discipline is restated at least five times (the pitfalls section, line 41, Step 5's no-bug discipline, Step 6, and the no-bug example), and the "Divergence is not optional" point is repeated nearly verbatim across sections — clear tightening opportunities that keep it below anchor 4.

3 / 5

Actionability

Two complete, copy-paste-ready finding templates (critical and no-bug cases) and concrete disambiguation rules ("any state access involving more than one execution context ... is L7, never L4") are strong. But the substance of Steps 1–8 repeatedly defers to a guide that is not bundled — "using the name, type, state and control checks in guide Step 2", "guide Step 5.5", "compute the bounded Logic Score using guide Step 7" — so key executable details (the premise checklists, the three rebuttal questions, the scoring formula) are simply missing, matching anchor 3's 'incomplete; missing key details'.

3 / 5

Workflow Clarity

Steps 0–8 are clearly sequenced with unusually strong validation checkpoints: an adversarial red-team step with withdraw/downgrade rules, a reachability gate, a remedy dry-run, and an optional execution verification gate that withdraws false positives — a genuine feedback loop. The gap keeping it below anchor 5 is that several checkpoints' operational detail (rebuttal question content, scoring computation) lives only in the unbundled guide, leaving those steps implicitly defined.

4 / 5

Progressive Disclosure

The body points to exactly one bundle file — "Use only the relevant steps in `logic-review-guide.md` as you reach them" — and cites "guide Step N" roughly fifteen times, but that file does not exist anywhere in the bundle (no references/, scripts/, or assets/ directories). The reference is one level deep and clearly signaled, but it is broken: all deferred content is unreachable, which is a structural failure the rubric's 'minimal structure / buried references' anchor 2 captures better than the well-organized anchors 4–5.

2 / 5

Total

12

/

20

Passed

Description

83%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 strong description that clearly and explicitly states both what the skill does and when to trigger it, with genuinely natural trigger phrases. Its weaknesses are mild: single-capability coverage rather than a list of multiple actions, and an open-ended trigger phrase list that omits common synonyms.

Suggestions

List one or two more concrete natural trigger phrases (e.g., "is this code correct", "something feels off with this function") instead of ending the list with an ellipsis, and remove the trailing ',...' so the description reads as complete rather than truncated.

Optionally mention a second concrete capability (e.g., producing a structured five-field finding report with severity and a Logic Score) to broaden the action coverage from a single verb.

DimensionReasoningScore

Specificity

The description names a concrete capability ("Find logic bugs in a single file or function") plus an explicit method breakdown ("semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy)") with a bounded scope. It lists several specific concrete actions via the five-phase pipeline rather than multiple distinct capabilities, which is the minor gap that keeps it below the comprehensive anchor 5.

4 / 5

Completeness

Both questions are explicitly answered: what ("Find logic bugs ... via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy)") and when ("Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like ...") with concrete trigger phrases, matching the anchor-5 example pattern exactly.

5 / 5

Trigger Term Quality

It quotes natural phrases users actually say — "review this", "does this look right" — and names the triggering situation ("suspects something is wrong without naming a concrete failure"). Common variations like "is this correct", "something feels off", or "find the bug" are missing, and the trailing ",..." leaves the phrase list open-ended rather than complete, so it does not reach anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct — debugging an unnamed suspicion in a single file/function via a five-field tracing format — and the qualifier "without naming a concrete failure" separates it from general review skills. Minor overlap remains: a bare "review this" request could also plausibly route to a generic code-review skill, so it is not the minimal-conflict anchor 5.

4 / 5

Total

17

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

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