CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

guardrails-lens

Argument check first: scan a draft in three passes for argument problems (straw men, false binaries, AI determinism, stakes inflation), then clarity and evidence gaps, then structural mechanics, logging each finding with location, verbatim line, diagnosis, and suggested fix. Flags, never scores. Use when the user asks to review, fact-check, tighten, or edit a draft before publishing — 'review my writing', 'edit my essay', 'argument check'. Runs as the last review lens on a draft, after the allergist and taste-lens.

Quality

96%

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 editorial checklist that is maximally concise and actionable, with concrete report templates and clear pass structure. The only notable gap is a pass-order inconsistency between the description (argument first) and the body (clarity first), plus no rule for findings that span multiple passes.

Suggestions

Reconcile the pass order: the frontmatter description says "argument problems... then clarity and evidence gaps" but the body runs Pass 1 as clarity/evidence and Pass 2 as argument — align both so the execution order is unambiguous.

Add one line to the Logging section covering findings that fit multiple checks (e.g. a straw man that is also an attribution gap) so each finding is logged once under the strongest check rather than duplicated across passes.

DimensionReasoningScore

Conciseness

The body is lean throughout: each check is a compact definition plus fix directive (e.g. "**False binary.** Two options where the reader can name a third."), with no explanations of concepts Claude already knows and no padding. Every token earns its place, matching the anchor-5 lean example.

5 / 5

Actionability

For an instruction-only skill the guidance is fully executable: each check names the diagnosis and the fix ("Scope it to the cases observed", "Gloss them on first mention"), the Logging section specifies the exact record fields, and the Report section gives two complete output templates with verbatim quoted findings. Per the code-vs-instruction note, absence of code is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

The sequence is clear ("Make three full passes, one per category" → Logging → Report) with decision checkpoints (the 10+ findings summarization branch and the send-back-to-other-lens dedup rule). It falls short of anchor 5 because there is no explicit error-recovery loop and the frontmatter description orders the passes (argument, then clarity) differently from the body (Pass 1 clarity, Pass 2 argument), leaving minor ambiguity in execution order. It is above anchor 3 because checkpoints are present, not merely implicit.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the ~80-line body is well organized under clear section headers with nothing that clearly belongs in a separate file. Mentions of `allergist`, `taste-lens`, and `lessons` are pointers to sibling skills, not nested file references, so the single-file structure is appropriate and fully navigable.

5 / 5

Total

19

/

20

Passed

Description

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

An excellent description: concrete and comprehensive on capabilities, explicit trigger phrases in the user's own voice, and a clear what/when pair. The only weakness is that its generic editing triggers rely on pipeline position rather than distinctive keywords to avoid overlap with sibling editing skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with the specific checks named: "scan a draft in three passes for argument problems (straw men, false binaries, AI determinism, stakes inflation), then clarity and evidence gaps, then structural mechanics" plus a fully specified logging format ("location, verbatim line, diagnosis, and suggested fix") and the "Flags, never scores" behavior. Coverage of what the skill does is comprehensive, matching the anchor-5 example rather than the minor-gaps anchor 4.

5 / 5

Completeness

Both what and when are explicit: the what covers three named passes, their checks, the logging fields, and the flags-not-scores policy; the when is a clear "Use when" clause with concrete trigger phrases. This matches the anchor-5 example structure exactly, so it is not the 4 anchor where 'when' could be more explicit.

5 / 5

Trigger Term Quality

It includes natural verbs users would say ("review, fact-check, tighten, or edit a draft before publishing") plus verbatim user-voice trigger phrases ("'review my writing'", "'edit my essay'", "'argument check'"). This is comprehensive natural-term coverage with synonyms and example utterances, exceeding the good-coverage anchor 4.

5 / 5

Distinctiveness Conflict Risk

The pipeline positioning ("Runs as the last review lens on a draft, after the allergist and taste-lens") carves a clear niche, but the trigger phrases "review my writing" and "edit my essay" are generic editing requests that overlap with other editing/review lenses, so it is not the minimal-conflict anchor 5. It is above anchor 3 because the argument-check focus and explicit ordering against sibling lenses distinguish it.

4 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

shortrib-labs/content-loop

Path

plugins/review/skills/guardrails-lens/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.