CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-lens-improvement

Run one of the factory's four proposal-only learners on its Europe/London schedule (lens tuning six-hourly, review-feedback and run learning daily, instruction tidy on Mondays), or as a bounded manual initial inspection, and save evidence-based, deduplicated proposals in the factory-state/review-lenses ledger. Use when running the review-lens improvement or factory learning loops. Never edits, weakens or approves anything.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally actionable, well-sequenced procedure whose commands, JSON templates and validation gates leave nothing ambiguous about what to run, when to stop, and what to record. Its costs are density and self-containment: the coverage and ledger rules are stated redundantly inline, and material that belongs in one-level-deep reference files (schemas, receipt rules) is embedded in the body.

Suggestions

Move the proposal/run JSON schemas and the coverage-receipt classification rules into a reference file (e.g. references/ledger-schema.md) and keep a compact summary plus a clearly signaled link in SKILL.md.

Tighten the Inspect coverage section by stating each `through`/receipt rule once — the conditions currently appear in both the prose paragraph and the `record` refusal list.

Replace the long prose list of `record` refusals with a short table (refusal → reason → action), which would cut tokens without losing any rule.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no concept explanations, no padding) but restates the coverage/`through` rules repeatedly — the receipts paragraph ('It accepts a partial `coverage.through` only when every source not read in full is a `complete` or `capped` source whose content you read and names its own `through` at or after it...') and the record-refusal list re-cover the same ground. Mostly efficient with sections that could be tightened, matching anchor 3 rather than the minor-trim level of 4.

3 / 5

Actionability

Guidance is fully executable: copy-paste-ready commands with real flags (`node scripts/lenses/ledger.mjs due <LEARNER>`, `gh pr list --state all --search "updated:>=<time> sort:updated-asc" --limit 100`), a complete JSON run-record template, and a precise field-by-field proposal schema with exact allowed values. Matches anchor 5; for an instruction-only skill the absence of code is not penalized because the commands and schemas are exact.

5 / 5

Workflow Clarity

The sequence (Guards → Inspect → Record → Run output) is explicit with hard validation checkpoints at every stage: `"due": true`/`"allowed": true` gates before any work, `record` refusing malformed, late, out-of-window or oversized runs, per-source coverage receipts, and explicit error recovery (push refused → report and stop, slot stays due; revision semantics for changed repeats). This batch-write skill has the feedback loops anchor 5 requires, well above anchor 4's 'minor validation gaps'.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent; `scripts/lenses/ledger.mjs` is a repository path, not a bundle file), so the 200+ line body inlines material — coverage-receipt rules, the proposal schema, the ledger refusal rules — that would fit one-level-deep reference files. Headers are clear and well-ordered, but there are no references to signal and the inline bulk is substantial, matching anchor 3 rather than the mostly-appropriate placement of 4.

3 / 5

Total

16

/

20

Passed

Description

80%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 highly specific, distinctive description that clearly states both what the skill does and when to use it, with an explicit trigger clause and honest non-action guarantees. Its main weakness is trigger phrasing limited to internal jargon ('factory learning loops') without the natural synonyms or learner-level phrasings a user might actually say.

Suggestions

Broaden the 'Use when' clause with natural variations users might say, e.g. 'Use when running the review-lens improvement or factory learning loops, or when asked to tune review lenses, process review feedback, or tidy factory instructions'.

Surface the four learner names (lens tuning, review feedback, run learning, instruction tidy) as trigger keywords rather than only as schedule parentheticals, so a learner-level request matches the description.

DimensionReasoningScore

Specificity

Concrete actions are stated ('Run one of the factory's four proposal-only learners', 'save evidence-based, deduplicated proposals in the factory-state/review-lenses ledger', 'Never edits, weakens or approves anything') with a named destination. It lists several specific actions with minor gaps — the per-learner outputs are summarized rather than enumerated — so it fits anchor 4, not the comprehensive coverage of 5.

4 / 5

Completeness

It explicitly answers both questions: a concrete 'what' (run the four learners on their London schedule, or a bounded manual inspection, and save deduplicated proposals to the ledger) and an explicit 'Use when...' clause with concrete trigger phrases. This matches anchor 5; it is above anchor 4 because the 'when' is explicit and specific, not merely implied or improvable.

5 / 5

Trigger Term Quality

The 'Use when' clause offers only two insider phrases ('review-lens improvement or factory learning loops') and the learner names appear as schedule parentheticals rather than triggers, with no synonyms or natural variations. Relevant keywords exist but common variations are missing, matching anchor 3 rather than the good coverage of 4.

3 / 5

Distinctiveness Conflict Risk

The niche is unmistakable — 'proposal-only learners', 'factory-state/review-lenses ledger', 'Never edits, weakens or approves anything' — with distinct triggers that would not fire for any other skill. Clear match to anchor 5 with minimal conflict risk.

5 / 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

referenced_paths_exist

Referenced path issues: 7 missing, 7 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

guypod/carnival-evolution-20261028

Path

tessl-factory/skills/review-lens-improvement/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.