CtrlK
BlogDocsLog inGet started
Tessl Logo

learn

Runs a six-phase research workflow that turns unfamiliar domains, source bundles, or collected material into publish-ready output. Use when users ask in any language to research, study, deep-dive, compile sources, synthesize unfamiliar material, or turn a source bundle into a coherent reference. Not for quick lookups or single-file reads.

68

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

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.

A well-structured multi-phase research workflow with strong sequencing, explicit validation feedback loops, and lean directive prose. The main limitations are actionability contingent on sibling skills and a monolithic file that inlines content that could be split into references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, using directive phrasing ('Prefix your first line with 🥷 inline', 'Move, don't refetch') with only minor instances of explanation that could be trimmed.

4 / 5

Actionability

Although no code is present, the guidance is concrete and specific for an instruction-only workflow ('use an installed search plugin (e.g., PipeLLM)', 'every URL goes through /read', 'Target: 5-10 sources'), with only minor gaps since execution depends on sibling skills.

4 / 5

Workflow Clarity

Six phases are clearly sequenced with ordered substeps (Phase 1: Discover → Fetch → File), explicit feedback loops (Phase 4 stall signals routing back to Phase 2), a two-pass self-review validation step, and a Hard Rules/Gotchas checklist; the operation is research/synthesis, so the destructive-batch cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist; the single self-contained file is organized with clear section headers and one-level-deep inline references to /read and /write, but at ~115 lines with substantial inlined material (Canonical Article Mode, distillation guidance) it shows minor organization gaps versus a fully split structure.

4 / 5

Total

17

/

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.

A well-constructed description that clearly answers both what and when with concrete trigger phrases and an explicit negative boundary. Minor synonym overlap and slight trigger-coverage gaps prevent a perfect score.

DimensionReasoningScore

Specificity

The description lists several concrete actions ('compile sources', 'synthesize unfamiliar material', 'turn a source bundle into a coherent reference') anchored to a 'six-phase research workflow', but several triggers are near-synonyms rather than distinct capabilities, leaving minor coverage gaps that keep it below 5.

4 / 5

Completeness

It explicitly states what the skill does ('Runs a six-phase research workflow that turns ... material into publish-ready output') and when to use it ('Use when users ask in any language to research, study, deep-dive, compile sources, synthesize ...'), with an added negative-boundary clause.

5 / 5

Trigger Term Quality

Natural user-facing terms ('research, study, deep-dive, compile sources, synthesize unfamiliar material, source bundle') are present with synonym variation, though a few common phrasings (e.g. 'write an article about', 'summarize') are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche with an explicit boundary ('Not for quick lookups or single-file reads') distinguishes it, but the 'research'/'deep-dive' triggers carry minor overlap risk with a closely related deep-research skill.

4 / 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.

Validation15 / 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.