CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

contextualize

Use when a result, this session's or one brought in, may not fit where it lands or may leave out what was asked, or when the user asks to check that fit; opened without the user's call only where a mismatch has actually been detected, saying so. The user sees each misfit found, settled or withdrawn, and the fixes carried out and reread until nothing is open.

Quality

61%

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

Fix and improve this skill with Tessl

tessl review fix ./epharmoge/skills/contextualize/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 skill encodes a coherent, carefully thought-through protocol with one genuinely concrete worked example, but its execution is specified almost entirely through a monolithic Lean 4 formal block whose rules are restated many times across sections. An executor must mine dense formalism for the actual workflow, and the token cost is high relative to the actionable content delivered.

Suggestions

Move the bulk of the Lean formal block to a reference file (e.g. references/formal-model.md) and keep in SKILL.md a short prose summary of the flow and invariants, leaving the worked example and Rules inline.

State each rule once canonically: the person-resolves, one-sheet, reach-named, and evidence-settles rules each appear in the Definition, the MORPHISM comments, the axiom docs, TOOL GROUNDING, CONVERGENCE, and Rules — cut to one authoritative statement per rule.

Replace abstract axiom prose (e.g. around `observe` and `mismatches`) with one or two more end-to-end worked examples like the nightly-report sheet, showing what observation looked at, what was judged, and what perform wrote.

DimensionReasoningScore

Conciseness

The body is ~500 lines dominated by a Lean 4 block, and the same rules — the person resolves each mismatch, one sheet, reach named, evidence settles only what is not the person's — are restated in the Definition, the FLOW/MORPHISM comments, the axiom doc comments, TOOL GROUNDING, CONVERGENCE, and Rules. This is noticeably verbose with several padded, redundant sections (anchor 2); it avoids anchor 1 only because the padding is repetition of its own protocol, not explanation of concepts Claude already knows, and it is far below anchor 3's "mostly efficient".

2 / 5

Actionability

There is real concrete guidance — the worked sheet example for the nightly report ("1. The report goes out at 18:00 Seoul time… a. Send it at 09:00 Seoul time — `0 0 * * *`") and the Rules' rendering requirements — but the core operations are specified as abstract axioms: "Where to look is yours to judge", "Which grounds do this is your reading each time". This is formal pseudocode with missing execution detail, matching anchor 3 rather than 4's mostly-executable guidance.

3 / 5

Workflow Clarity

A sequence is present — "pass(c): observe; perform — the relay; observe again", then the sheet, then "next utterance u… pass(c')" — and a revalidation loop is built in ("a write changes what the next observation reads", a write that did not repair leaves its mismatch open). But the sequence and its checkpoints are embedded in dense formal notation and prose comments rather than presented as an executable order, leaving implicit what a reader must extract; anchor 3, not 4.

3 / 5

Progressive Disclosure

The single bundle reference (references/round-composition.md) is well signaled — "Read `references/round-composition.md` before composing when…" with explicit read conditions — and is one level deep. However, ~450 lines of Lean formalism are inlined directly in SKILL.md, content that clearly belongs in a separate reference file, matching anchor 3 (content that should be separate is inline) rather than 4.

3 / 5

Total

11

/

20

Passed

Description

62%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 explicitly covers both when to trigger and what the user experiences, in third person, and carves a genuinely distinct niche. Its weaknesses are abstraction in the 'what' (behavioral outcomes rather than concrete capabilities) and thin coverage of natural trigger variations users would actually say.

Suggestions

Lead with a plainer statement of the core action, e.g. "Checks a result against every place it lands and every intent it was meant to carry, shows each misfit on one sheet, and carries out the fixes the user settles."

Add the natural phrases a user would actually say when they need this, e.g. "does this match what I asked for", "this is in the wrong place", "check this result fits".

DimensionReasoningScore

Specificity

The description names the domain (a result's fit to where it lands) and a few actions — "check that fit", "each misfit found, settled or withdrawn", "the fixes carried out and reread until nothing is open" — but these are abstract behavioral commitments rather than concrete operations, matching anchor 3. It is above anchor 2 (more than a generic action) but below anchor 4, which expects several specific concrete actions listed.

3 / 5

Completeness

Both parts are explicit: the 'when' opens with "Use when a result… may not fit where it lands or may leave out what was asked, or when the user asks to check that fit", and the 'what' follows as "The user sees each misfit found, settled or withdrawn, and the fixes carried out and reread until nothing is open". The 'what' is outcome-focused and convoluted rather than crisp, keeping it at anchor 4 instead of 5.

4 / 5

Trigger Term Quality

Phrases like "may not fit where it lands", "may leave out what was asked", and "when the user asks to check that fit" are natural, but coverage of common variations is thin — no synonyms like "does this match what I asked for", "review this result", or "wrong context". This sits at anchor 3 (some relevant keywords, missing common variations) rather than 4.

3 / 5

Distinctiveness Conflict Risk

The niche — checking a result against every place it lands and every intent it was meant to carry — is distinctive, with triggers unlikely to fire for unrelated skills; there is minor overlap risk with general review/verification skills a user might invoke with "check this". Anchor 4 fits better than 3 (the trigger is genuinely specific) and better than 5 (some overlap with review-type skills remains).

4 / 5

Total

14

/

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

skill_md_line_count

SKILL.md is long (508 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

jongwony/epistemic-protocols

Path

epharmoge/skills/contextualize/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.