CtrlK
BlogDocsLog inGet started
Tessl Logo

learn

Runs a six-phase research workflow from source bundle to publish-ready output. Use when researching an unfamiliar domain or compiling materials into one reference. Not for quick lookups or single-file reads.

64

Quality

81%

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

The canonical home for this skill is learn in tw93/Waza

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 delivers a clearly sequenced six-phase workflow with explicit validation gates, feedback loops, and hard rules, plus concrete operational parameters like source-count targets and claim-test questions. It is mostly lean and actionable, held back only slightly by a couple of dense sections and the absence of worked examples of intermediate artifacts such as outlines or digests.

DimensionReasoningScore

Conciseness

The body is dense with workflow-specific rules (claim-test questions, stall signals, source-count targets) and assumes Claude's competence rather than teaching background concepts. Minor over-explanation in the Output representation guidance ("visual polish alone is not evidence of correctness") and parts of Phase 6 could be trimmed, keeping it below the lean-everywhere bar of anchor 5 but clearly above anchor 3.

4 / 5

Actionability

Concrete, executable guidance throughout: ordered Discover/Fetch/File steps with fallback behavior when /read is absent, "5-10 sources for a blog post, 15-20 for a deep technical survey", a mode table with entry/exit phases, and a specified candidate-matrix shape for distillation. Not 5 because no worked example of any intermediate artifact (outline, digest notes) is shown, leaving a minor gap.

4 / 5

Workflow Clarity

Six phases are explicitly sequenced with per-mode entry/exit mapping, an explicit validation gate ("No Phase 4 before the outline is solid"), feedback loops ("return to Phase 2 for that sub-topic, not the whole article"), enumerated stall signals, a two-pass self-review, and a publish hard-stop. This matches the top anchor's validation-plus-feedback-loop structure; the skill is not destructive/batch so no cap applies.

5 / 5

Progressive Disclosure

A single-file skill with no bundle files, organized under clear headers, tables, and phase sections; no broken or buried references exist. Not 5 because at ~105 lines it exceeds the simple-skill exception and contains dense inline blocks (Conversation Or Review Distillation, the Output representation guidance) that could be split into one-level-deep reference files.

4 / 5

Total

17

/

20

Passed

Description

75%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 an explicit exclusion boundary that strongly reduces conflict risk. Its weaker spots are moderate trigger coverage — natural phrasings like "deep dive" or "help me understand" appear only in when_to_use, not the description — and actions stated as one summary-level workflow rather than an enumerated list.

Suggestions

Enumerate the concrete stages in the description itself (e.g., "collects and fetches primary sources, digests them into a mental model, outlines, drafts, and self-reviews a publish-ready article") to raise specificity beyond a single summary action.

Fold one or two natural user phrasings currently only in when_to_use — such as "deep dive" or "help me understand" — into the description's "Use when" clause to broaden natural-keyword coverage.

DimensionReasoningScore

Specificity

"Runs a six-phase research workflow from source bundle to publish-ready output" names the domain and a composite action with concrete input and output, but only 1-2 actions are stated at a summary level and the phases' actual work (collect, digest, outline, refine) is not enumerated. Not 4 because anchor 4 requires several distinct specific actions listed, which the description does not do.

3 / 5

Completeness

The description explicitly answers what ("Runs a six-phase research workflow from source bundle to publish-ready output") and when ("Use when researching an unfamiliar domain or compiling materials into one reference"), with concrete trigger phrases plus an exclusion clause ("Not for quick lookups or single-file reads"). Clearly matches the top anchor.

5 / 5

Trigger Term Quality

"Use when researching an unfamiliar domain or compiling materials into one reference" supplies relevant keywords users would say ("researching", "compiling materials"), but common variations and synonyms such as "deep dive", "help me understand", or "learn about" are missing from the description field. Not 4 because more than a few natural phrasings are absent.

3 / 5

Distinctiveness Conflict Risk

"Not for quick lookups or single-file reads" explicitly carves the niche of multi-source research producing a new structured output, minimizing conflict with simpler read/lookup skills. The niche and triggers are distinct, matching the top anchor rather than the 'minor overlap risk' of anchor 4.

5 / 5

Total

16

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
tw93/Waza
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.