CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pipeline-review-and-agents

Use when changing review sessions, finding decisions, the review fix-round carry, review schema retries, agent timeouts, local Test behavior and its live-validation contract, approval overrides and parked gates, or intent conformance.

Quality

52%

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

Quality

Content

46%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 is an exhaustively concrete but monolithic invariant dump: every rule is anchored to real files, functions, and regression tests, yet the 60KB single-file wall with zero bundle references makes it expensive to load and hard to navigate. Splitting per-subsystem reference files and tightening the run-on sentences would address both weakest dimensions.

Suggestions

Split each bold subsystem section (sessions, recorded decisions, timeouts, Test contract, review carry, approval overrides) into its own file under references/ and keep SKILL.md as a one-page index with one-line summaries — this fixes the missing progressive disclosure.

Break the 100+ word run-on sentences (especially the timeout and fix-response sections) into short rule statements; roughly half the current token load is clause nesting that could be flattened without losing information.

Move the exhaustive regression-test name lists into the per-topic reference files and keep only the primary test per invariant inline, so the always-loaded overview carries the rules rather than the full test inventory.

DimensionReasoningScore

Conciseness

The 60KB body is a wall of mammoth run-on sentences with nested parentheticals (e.g. the timeout section chaining baseline-freeze, still-working-cap, and #1109-case rules into a single sentence), which could be cut or split drastically. It is not 1 because it never explains concepts Claude already knows — every line is repo-specific invariant — but the density-per-token is poor and much phrasing is redundant.

2 / 5

Actionability

Guidance is concrete and specific throughout: exact file paths ("internal/pipeline/sessions.go"), function names ("splitFixResponse", "mergeOutstandingFindingsJSON"), config keys ("review_agent_working_timeout"), explicit directives ("Do not raise the shipped 30m default"), and named regression tests. It is not 5 because the prose describes invariants rather than giving copy-paste-ready coverage of the common cases an editor would execute.

4 / 5

Workflow Clarity

The body is organized into clearly labeled subsystem sections, each stating coherent fail-safe rules ("a failed fixer resume drops the identity and re-runs the same turn, never skipping the turn"). However, there are no multi-step sequences or validation checkpoints anywhere — it is descriptive invariant prose, not a workflow — so it cannot reach 4.

3 / 5

Progressive Disclosure

No references/, scripts/, or assets/ exist; the entire ~12-subsystem corpus (sessions, decisions, timeouts, Test contract, review carry, etc.) is inlined in one 60KB monolith where each section clearly belongs in its own reference file. The bold section headers provide some structure, keeping it above 1, but the total absence of any file split matches the anchor for content that clearly belongs in separate files being inlined.

2 / 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 pure trigger clause: it excels at scoping when the skill applies via niche domain terms, but it never states what the skill actually does with those areas. Adding a capability statement (e.g. "Holds the invariants and regression inventory for ...") would lift both completeness and specificity.

Suggestions

Add a "what" clause before the "Use when" trigger, e.g. "Reference of invariants, design decisions, and regression tests for the review pipeline. Use when changing...", so completeness covers both dimensions.

State one or two concrete actions the skill supports (e.g. "check which regressions guard a subsystem before editing it") so specificity moves beyond domain naming.

Include natural synonyms for trigger terms — "re-review", "fix round", "timeout budget", "parked gate" — so trigger_term_quality covers variations users actually say.

DimensionReasoningScore

Specificity

The description names many concrete domains ("review fix-round carry", "review schema retries", "live-validation contract", "approval overrides and parked gates") but states no actions the skill performs beyond "changing" — domains without verbs. It is not 3 because no concrete action is listed anywhere, and not 1 because the domains themselves are specific rather than abstract.

2 / 5

Completeness

The "when" is explicit and rich ("Use when changing review sessions, finding decisions, ... or intent conformance") but the "what" is entirely absent — the description never says what the skill does with those areas. This matches the anchor for having a clear trigger without a stated capability, and cannot be 4 because both what and when are required.

3 / 5

Trigger Term Quality

Phrases like "review sessions", "finding decisions", "agent timeouts", and "intent conformance" are terms the target audience would naturally say, but they are jargon-heavy and offer no synonyms or common variations (e.g. no "re-review", "timeout budget", "gate approval"). Not 4 because several natural restatements a user might actually type are missing.

3 / 5

Distinctiveness Conflict Risk

Triggers like "the review fix-round carry", "review schema retries", and "live-validation contract" occupy a clear niche with minimal conflict risk. Not 5 because broader terms such as "agent timeouts" and "review sessions" could overlap with sibling pipeline skills in the same repository.

4 / 5

Total

12

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

kunchenguid/no-mistakes

Path

.agents/skills/pipeline-review-and-agents/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.