CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

note-summarizer

Organize study notes into a structured knowledge-point outline and export to a .docx summary when you need a shareable, hierarchical document from Word/PPT/Text/Markdown inputs.

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Other/note-summarizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 substantive half of this skill body (sections 1-5) is genuinely good — concrete commands, a complete config schema, and clear output criteria — but it is buried under an entire duplicated template-generated section set full of filler and internal contradictions (Python version, dependency pinning). The result reads as two skills stitched together, which costs token efficiency and muddies the workflow and verification story.

Suggestions

Delete the first, template-generated copies of 'When to Use', 'Key Features', 'Dependencies', 'Example Usage', and 'Implementation Details' (the generic filler versions), keeping only the concrete sections 1-5 — this removes the duplication and the 3.10+/3.9+ and pinning contradictions in one pass.

Fix the verification command to reference a real file: either add examples/example.json to the bundle or change it to the inline input.json example already shown in section 4.

Add a short error-recovery note after 'Basic verification' (e.g., what to check when the .docx fails to open or sections are missing) to turn the success criteria into a genuine validate-and-fix checkpoint.

DimensionReasoningScore

Conciseness

The body duplicates an entire template-generated section set — 'When to Use', 'Key Features', 'Dependencies', 'Example Usage', 'Implementation Details' each appear twice — padded with vacuous filler like 'Structured execution path designed to keep outputs consistent and reviewable' and broken boilerplate like 'Use this skill when a others task needs a packaged method'. This is noticeably verbose with several padded sections (anchor 2); it is not a 1 because it never explains concepts Claude already knows, and not a 3 because roughly half the body is redundant filler.

2 / 5

Actionability

Sections 4-5 are highly concrete and executable: an exact run command, a full JSON config example, a complete input schema with defaults, the output structure, and a verification command with success criteria. The main gaps are minor: the verification command references 'examples/example.json' which does not exist in the bundle, and the contradictory duplicate Dependencies sections (Python '3.10+' vs '3.9+'; 'not explicitly version-pinned' vs a pinned install command) leave the reader unsure which guidance is authoritative.

4 / 5

Workflow Clarity

A rough sequence exists (the four-step 'Example run plan' and the 'Basic verification' with success criteria), but the checkpoints are generic ('Review the generated output') and there is no feedback loop for what to do when validation fails (e.g., output docx missing sections, image copy failure). The two conflicting copies of the usage/dependency guidance further blur the actual workflow, fitting anchor 3: 'sequence present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The skill is a single self-contained script (scripts/note_summarizer.py exists and matches the documented --json interface) with no reference files, and the body does have section headers and an appropriately small inline schema. However, the duplicated parallel section sets ('When to Use' twice, etc.) mean the overview is not well organized — the same information lives in two places with conflicting details — so structure is present but navigation and organization could clearly be better (anchor 3).

3 / 5

Total

12

/

20

Passed

Description

70%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 solid description that explicitly covers both what the skill does and when to use it, with a clear niche and mostly natural trigger terms. Its weaknesses are modest: only two concrete capabilities are named, and the 'when' trigger is woven into an awkward run-on sentence rather than a crisp standalone clause.

Suggestions

Restructure into a distinct what/when pattern: 'Organize study notes from Word/PPT/Text/Markdown into a structured knowledge-point outline and export a Word (.docx) summary. Use when the user mentions study notes, class notes, lecture slides, or wants a shareable outline document.'

Mention the additional concrete capabilities the skill actually has (merging multiple sources, preserving heading hierarchy, copying images into sections) to raise specificity.

DimensionReasoningScore

Specificity

The description names the domain ('study notes') and two concrete actions — 'Organize study notes into a structured knowledge-point outline' and 'export to a .docx summary' — but coverage is not comprehensive (no mention of merging multiple sources, preserving heading hierarchy, or image handling, all of which the skill body documents). This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; a 4 would require several specific actions listed.

3 / 5

Completeness

Both 'what' ('Organize study notes into a structured knowledge-point outline and export to a .docx summary') and 'when' ('when you need a shareable, hierarchical document from Word/PPT/Text/Markdown inputs') are explicitly present. However, the trigger clause is embedded in a single run-on sentence that repeats 'when you need' twice, so the 'when' is less crisply separated and specific than the anchor-5 pattern of a distinct, concrete 'Use when...' phrase; this fits anchor 4 ('when' could be more explicit or specific).

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'study notes', 'outline', '.docx summary', 'shareable, hierarchical document', 'Word/PPT/Text/Markdown inputs'. A few natural terms users would say are missing, such as 'class notes', 'lecture slides', 'notes summary', or explicit extensions (.pptx, .md), so it falls just short of the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The niche (study-note summarization to .docx from Word/PPT/Text/Markdown) is mostly distinct with concrete format triggers, giving minor overlap risk only with closely related document-summarization skills. It lacks the sharp single-format focus of the anchor-5 example (e.g., 'PDF files, PDFs, forms'), so 4 rather than 5.

4 / 5

Total

15

/

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

aipoch/medical-research-skills

Path

scientific-skills/Other/note-summarizer/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.