CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

curate-stories

Refresh this notebook with a small selection of source-backed developer growth and AI stories and LinkedIn drafts. Use for a requested content refresh, not arbitrary code changes or publishing to social networks.

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 exemplary instruction-only skill body: dense, concrete, and honest about failure states, with specific file targets, commands, and verification requirements. The only minor gap is the absence of an explicit error-recovery loop when npm run check or build fails.

DimensionReasoningScore

Conciseness

The ~180-word body is lean and directive throughout (e.g., "Open the original source; search snippets are not evidence."), explains nothing Claude already knows, and every token earns its place.

5 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact file paths (content/stories.json, content/drafts.json, content/profile.json), commands (npm run check, npm run build), a concrete output schema (title, value sentence, up to three facts, URLs, dates), and specific PR submission requirements.

5 / 5

Workflow Clarity

A clear paragraph-ordered sequence (read current state, research, verify, write stories, draft, check/build, submit PR) with validation checkpoints (npm run check and build) and failure handling ("A failed research run leaves the last verified edition unchanged"), but there is no explicit fix-and-retry loop if the checks fail, matching 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no bundle files, and is well organized under one heading; external data-file references are one level deep and clearly signaled, so the simple-skill exception applies.

5 / 5

Total

19

/

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 strong description: it states concrete deliverables, includes an explicit 'Use for' trigger clause with helpful negative boundaries, and occupies a distinct niche. The only weakness is that the action list is limited to two deliverables rather than several specific actions.

Suggestions

Enumerate a few more concrete actions to raise specificity, e.g., 'Verify sources, update stories.json, and draft LinkedIn posts' instead of the single verb 'refresh'.

Add one or two natural trigger synonyms (e.g., 'update', 'curate') alongside 'content refresh' so the trigger term coverage is comprehensive.

DimensionReasoningScore

Specificity

Names the domain ("source-backed developer growth and AI stories") and 1-2 concrete actions ("Refresh this notebook with... stories and LinkedIn drafts"), but does not enumerate several distinct actions, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

The 'what' is explicit ("Refresh this notebook with a small selection of source-backed... stories and LinkedIn drafts") and the 'when' is an explicit trigger clause ("Use for a requested content refresh") reinforced with negative boundaries ("not arbitrary code changes or publishing to social networks"), matching the top anchor.

5 / 5

Trigger Term Quality

"content refresh", "stories", "LinkedIn drafts", and "developer growth" are natural phrases a user would say when requesting this skill; a few synonyms (e.g., "update", "curate") are missing, which matches 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

"this notebook" with specific story types carves out a clear niche, and the explicit exclusions ("not arbitrary code changes or publishing to social networks") minimize overlap with other skills, matching 'clear niche with distinct triggers; minimal conflict risk'.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fernandezbaptiste/baptiste-notebook

Path

skills/curate-stories/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.