CtrlK
BlogDocsLog inGet started
Tessl Logo

source-comparison

Compare multiple sources on a topic and produce a grounded comparison matrix. Use when the user asks to compare papers, tools, approaches, frameworks, or claims across multiple sources.

69

Quality

84%

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

86%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.

An extremely concise, well-structured delegating skill that points to a slash command for the substantive workflow. It is lean and well-organized, but the actual comparison methodology and any validation of the output matrix are not visible in the body.

Suggestions

Add a brief validation step for the produced comparison matrix (e.g., 'verify every cell is grounded in a cited source before writing to outputs/') to raise workflow_clarity and guard against ungrounded claims.

Include a one-line sketch of the comparison dimensions or matrix schema so the skill is actionable even if the `/compare` command is unavailable or expands slowly.

DimensionReasoningScore

Conciseness

Three lean lines with no concept over-explanation or padding; the clarifying note about the slash command prevents a real failure mode rather than adding fluff. Every token earns its place.

5 / 5

Actionability

Gives a concrete, copy-paste-ready command ('Run the `/compare` workflow') plus specific agents and output location. Not a 5 because the actual comparison/matrix-building steps are delegated to the slash command rather than shown inline.

4 / 5

Workflow Clarity

The single action is unambiguous and metadata (agents, output path) is explicit. Not a 5 because the multi-step workflow sequencing itself lives in `/compare` and is not visible here, and there is no validation checkpoint for the produced matrix.

4 / 5

Progressive Disclosure

Under 50 lines, single task, no external reference files needed (no bundle files exist in references/scripts/assets), and the body is well-organized into heading, instruction, agents, and output. Matches the simple-skill exception for a 5.

5 / 5

Total

18

/

20

Passed

Description

82%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-crafted description that clearly states what the skill does and when to use it, with strong natural trigger terms and a distinct niche. The only weakness is moderate specificity, with just two fairly high-level actions named.

Suggestions

Add one or two more concrete actions to the 'what' clause (e.g., 'extracts claims, normalizes fields, surfaces disagreements') to lift specificity toward a 4 or 5.

Consider naming the output artifact type or comparison dimensions explicitly to make the capability more tangible.

DimensionReasoningScore

Specificity

Names the domain (comparing sources) and two concrete actions ('Compare multiple sources' and 'produce a grounded comparison matrix'), but coverage is not comprehensive. Matches the anchor for naming domain and 1-2 concrete actions; not a 4 because only two actions are listed and they are fairly high-level.

3 / 5

Completeness

Explicitly answers both 'what' (compare multiple sources and produce a grounded comparison matrix) and 'when' ('Use when the user asks to compare papers, tools, approaches, frameworks, or claims across multiple sources') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('compare papers, tools, approaches, frameworks, or claims across multiple sources'), giving good keyword coverage with synonyms. Not a 5 because a few common variants or file-type triggers are missing, but clearly above the 3 anchor.

4 / 5

Distinctiveness Conflict Risk

The 'comparison matrix across multiple sources' framing is a clear niche with distinct triggers and minimal overlap risk with other skills.

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

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.