CtrlK
BlogDocsLog inGet started
Tessl Logo

eli5

Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.

74

Quality

91%

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

92%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 concise, well-structured, and clearly actionable, with an unambiguous workflow for a simple skill. The only improvement would be showing the exact 'feynman alpha' command syntax instead of a placeholder.

Suggestions

Replace the 'feynman alpha ...' placeholder with a concrete, copy-paste-ready command example (e.g. the actual subcommand and argument form) to lift actionability to fully executable.

Optionally add one short worked example showing the six-section structure applied to a sample paper, so the expected output shape is unambiguous.

DimensionReasoningScore

Conciseness

Lean and token-efficient with no padding; it assumes Claude's competence, never explains concepts Claude already knows, and every line (tool-call pointer, answer structure, guidelines) earns its place.

5 / 5

Actionability

Provides concrete, actionable guidance — a specific shell invocation pattern ('feynman alpha ...', not a bare global 'alpha') and a fixed six-section answer structure — but 'feynman alpha ...' is a placeholder rather than copy-paste-ready executable syntax, leaving a minor gap.

4 / 5

Workflow Clarity

As a simple single-purpose skill under 50 lines, its single action is unambiguous: branch on paper-vs-topic input, anchor on a representative paper, and fill the named section structure, with no destructive or batch operations requiring validation.

5 / 5

Progressive Disclosure

For a sub-50-line single-purpose skill with no need for external references, the body is well-organized into headed sections and bullets; no bundle files are present or needed, satisfying the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

90%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 is well-crafted: it states concrete capabilities, supplies multiple natural trigger phrases, and explicitly covers both what and when. Its only mild weakness is specificity coverage that is strong but not exhaustive.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Explain...in plain English', 'minimal jargon', 'concrete analogies', 'clear takeaways') naming the research/papers domain, with only minor gaps in coverage rather than the comprehensive list needed for a 5.

4 / 5

Completeness

Clearly answers both what (explain research/papers/technical ideas in plain English with analogies and takeaways) and when, via an explicit 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrasings users actually say — 'ELI5 this', 'simple explanation of a paper or research result', 'wants jargon removed', 'what something technically dense actually means' — covering synonyms and the distinctive ELI5 idiom.

5 / 5

Distinctiveness Conflict Risk

The ELI5 niche has distinct triggers ('ELI5 this', jargon removal, explaining technically dense material) with minimal overlap risk against other skills.

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
companion-inc/feynman
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.