CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

notes

Turn user-provided notes into a concise agenda.

Quality

74%

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 ./scripts/security/fixtures/template-qualification/skills/notes/SKILL.md
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.

The body is an exemplar of token efficiency for a simple instruction-only skill: concrete deliverable, explicit input constraint, and sensible safety boundaries in four lines. The only meaningful gaps are the absence of a small output example and slight terminological drift between "agenda" (description) and "bullet summary and open questions" (body).

DimensionReasoningScore

Conciseness

The body is four lean lines — "Use only text supplied by the user. Return a heading, bullet summary and open questions." — with no padding and no explanation of concepts Claude already knows. Every token earns its place, matching the anchor 5 example of lean, competence-assuming content.

5 / 5

Actionability

"Return a heading, bullet summary and open questions" gives concrete, executable guidance about the deliverable, and the constraints ("Use only text supplied by the user", "Do not read credentials, contact services or install dependencies") are specific. It falls short of 5 only because there is no example output or template showing the expected format.

4 / 5

Workflow Clarity

As a simple single-task skill the action is largely unambiguous — the single-pass transform is clearly stated — but "Return a heading" is vague (a title? section headings?) and the body's "bullet summary and open questions" does not fully match the description's "concise agenda", leaving minor ambiguity. No validation steps are needed for this non-destructive task, so no cap applies.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and no bundle files (references/, scripts/, assets/) exist or are referenced. Per the simple-skill guideline, well-organized minimal content with no unnecessary file splitting earns a 5.

5 / 5

Total

18

/

20

Passed

Description

50%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 clear and concise with a concrete what, but it is a bare-minimum trigger description: no 'when to use' guidance, no synonyms or natural trigger variations, and only a single stated action. All dimensions land at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user provides meeting notes, minutes, or raw notes and wants an agenda or structured summary."

Include natural keyword variations users would say — "meeting notes", "minutes", "action items", "summarize my notes" — to improve trigger-term coverage and distinctiveness.

Briefly specify the deliverable's shape (e.g. "a titled agenda with bullet summary and open questions") so the what is more complete without adding fluff.

DimensionReasoningScore

Specificity

"Turn user-provided notes into a concise agenda" names a concrete input, transformation, and output, but describes only a single action with no detail on structure or variations, matching the '1-2 concrete actions, not comprehensive' anchor. It is above level 2 because the action is specific rather than generic, but below level 4 because no several-action coverage is offered.

3 / 5

Completeness

The description clearly answers 'what' (turn notes into a concise agenda) but contains no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is above 2 because the 'what' is clear, not vague.

3 / 5

Trigger Term Quality

"notes" and "agenda" are natural terms a user might say, but common variations and synonyms such as "meeting notes", "minutes", "action items", or "summarize" are absent, matching the 'some relevant keywords but missing common variations' anchor. It does not reach 4 because keyword coverage is only two terms.

3 / 5

Distinctiveness Conflict Risk

"user-provided notes" and "agenda" give it some specificity, but it could still overlap with general summarization or note-taking skills, matching the 'somewhat specific but could still overlap' anchor. It lacks the distinct trigger phrases needed for level 4 or 5.

3 / 5

Total

12

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openclaw/clawhub

Path

scripts/security/fixtures/template-qualification/skills/notes/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.