CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ulw-research

Runs maximum-saturation research with a cooperating team, claim-graph gating, and a cited, QA'd deliverable. Use when the user explicitly asks for research or a deep investigation, including any 'ulw' research wording.

Quality

83%

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

73%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 exceptionally actionable and validation-rich, with ordered gates, bounded repair loops, and exact commands throughout. Its main cost is token weight: heavy duplication and run-on paragraph density, plus large inline blocks that the reference files could absorb.

Suggestions

Deduplicate the harness-compatibility rule ("If a code block below conflicts with this section, this section wins") by stating it once at the top of the compatibility section instead of three times.

Move the literal meaning-reader prompt template and the per-gate defect-code details into the existing references (report-gates.md / deliverable-phase.md), keeping only the command invocations inline.

Break the 250+ word single-paragraph directives (design-spec, V1/V2 routing, repair bounds) into bullets or tables so the same binding content costs fewer tokens and parses faster.

DimensionReasoningScore

Conciseness

The ~194-line body is noticeably verbose: "If a code block below conflicts with this section, this section wins" is repeated three times (lines 20, 22, 24), and single paragraphs run 250+ words of nested clauses (e.g., the design-spec paragraph and the V1/V2 routing paragraph). It does not pad with concepts Claude already knows, but the duplication and run-on density leave substantial tightening potential, placing it below the mostly-efficient midpoint.

2 / 5

Actionability

Guidance is fully executable: exact commands with flags ("node \"$SKILL_DIR/scripts/report-tools.mjs\" fact verify \"$SESSION_DIR/report.html\" --session-dir \"$SESSION_DIR\"", "chrome --headless --disable-gpu --no-pdf-header-footer --print-to-pdf=<out.pdf> file://<report.html>"), a literal copy-paste meaning-reader prompt with an exact verdict JSON schema, and a concrete OpenCode-to-Codex tool translation table. Copy-paste-ready commands cover the common cases.

5 / 5

Workflow Clarity

The delivery workflow is explicitly sequenced with validation everywhere: "every gate for the QA tier must PASS, in order" (numbered gates 1-4 with exit-code semantics), a bounded repair feedback loop ("3 attempts, a 2-attempt plateau, an oscillation, or 15 minutes"), a success-criteria checklist, and a mandatory closing briefing. Phases 0-4 are delegated to references with explicit read-order guidance ("Read research-collection.md before scoping... then research-delivery.md before verification"), keeping the overall sequence coherent.

5 / 5

Progressive Disclosure

References are one level deep, well-signaled with when-to-read conditions ("Read research-collection.md before scoping or collecting sources", "Every asset lane reads report-visualization.md first"), and every referenced path (research-collection.md, research-delivery.md, report-visualization.md, report-gates.md, deliverable-phase.md, fact-ledger.md, scripts/report-tools.mjs) exists in the bundle. However, the body still inlines ~90 lines of Phase 5/gate/meaning-verifier detail that belongs in references, so SKILL.md is not a lean overview — good structure with minor organization gaps.

4 / 5

Total

16

/

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.

The description cleanly answers both what and when with concrete trigger phrases and a distinctive niche vocabulary. Its only weaknesses are jargon-tinged capability nouns and a slightly thin synonym set around "research"/"investigation".

DimensionReasoningScore

Specificity

"Runs maximum-saturation research with a cooperating team, claim-graph gating, and a cited, QA'd deliverable" lists several distinct concrete actions (team orchestration, claim-graph gating, cited/QA'd deliverable), matching the several-specific-actions anchor with minor gaps. It is not 5 because the actions rely on skill-internal jargon rather than fully user-observable capabilities, and not 3 because coverage goes beyond 1-2 actions.

4 / 5

Completeness

Both questions are explicitly answered: what ("Runs maximum-saturation research with a cooperating team, claim-graph gating, and a cited, QA'd deliverable") and when ("Use when the user explicitly asks for research or a deep investigation, including any 'ulw' research wording") with concrete trigger phrases. This matches the top anchor exactly.

5 / 5

Trigger Term Quality

Natural triggers include "explicitly asks for research", "deep investigation", and "'ulw' research wording" — good keyword coverage with only a few natural variants missing (e.g., "deep research", "investigate", "dig into"). Not 5 because there is no comprehensive synonym sweep; not 3 because more than minimal keywords are present and naturally phrased.

4 / 5

Distinctiveness Conflict Risk

Distinctive markers ("maximum-saturation", "claim-graph gating", "'ulw' research wording") carve a clear niche, but the broad trigger "research or a deep investigation" could overlap with other research-flavored skills. Mostly distinct with minor overlap risk — anchor 4, not 5 given the generic breadth of the word "research".

4 / 5

Total

17

/

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

code-yeongyu/lazycodex

Path

plugins/omo/skills/ulw-research/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.