CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

baptiste-content-advisor

Research and curate source-backed DevRel, developer growth, and AI stories for Baptiste's LinkedIn; calibrate article selection from his feedback and develop selected stories in his voice. Use for his personal content advice, reading shortlists, or LinkedIn drafts, rather than corporate Tessl blog reviews.

Quality

92%

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

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.

A high-quality editorial skill body: dense with user-specific calibration facts, fully actionable specifications for every common request, an explicit calibration feedback loop with pre-draft validation, and clean one-level reference splitting. The only measurable weakness is minor redundancy between the curation and drafting sections.

DimensionReasoningScore

Conciseness

Nearly every sentence carries non-derivable calibration data (rejected jokes, banned phrases, the 8.75/10 bar, confirmed vs hypothetical preferences) and nothing explains concepts Claude already knows. Only minor trims exist — e.g. the one-company-experience caution appears in both the curation and drafting sections — so it sits at efficient-with-minor-over-explanation rather than lean-every-token-earns-its-place.

4 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: exact per-candidate shortlist fields, exact feedback labels ("would share / useful to read / skip"), enumerated banned phrases ("caught my attention", "the difficult part is"), exact file paths and fields (content/profile.json, content/drafts.json with storyId and status), and exact queue states. Per the rubric's instruction-only note, absence of code is not penalized; the common cases are each fully specified.

5 / 5

Workflow Clarity

Sections sequence research → shortlist → recommend → calibrate → develop → quality check, with an explicit feedback loop (offer candidates, collect feedback, update the calibration reference, test transfer on later batches) and explicit checkpoints: the pre-draft checklist ("Before presenting a draft, check whether..."), the deletion pass, and "Never mark an item published without evidence". No destructive or batch operation applies, so no cap; checkpoints are explicit rather than implicit, keeping it above the 4 anchor.

5 / 5

Progressive Disclosure

Both bundle references exist and are exactly one level deep, each linked with a stated purpose: "Read [editorial-calibration.md]... for accepted examples and unresolved preferences before curating or drafting" and "The accepted direction is the example in [preferred-example.md]". Examples and calibration history are appropriately split out of a well-sectioned body with clear headers, matching the clear-overview/well-signaled-references anchor.

5 / 5

Total

19

/

20

Passed

Description

87%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: concrete actions, an explicit "Use for..." trigger clause, and a sharp personal-vs-corporate boundary. The only gaps are minor — a few missing synonyms and unmentioned secondary features.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Research and curate source-backed DevRel, developer growth, and AI stories", "calibrate article selection from his feedback", "develop selected stories in his voice" — matching the several-specific-actions anchor. Not 5 because secondary capabilities (content queue maintenance, the site drafts workflow) are unmentioned; not 3 since coverage goes well beyond 1-2 actions. Voice is third person, so no penalty applies.

4 / 5

Completeness

Clearly answers both: what ("Research and curate source-backed... stories... calibrate... develop selected stories in his voice") and when, with an explicit trigger clause — "Use for his personal content advice, reading shortlists, or LinkedIn drafts" — supplying concrete trigger phrases, which also lifts the missing-trigger cap.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "DevRel", "developer growth", "AI stories", "LinkedIn", "content advice", "reading shortlists", "LinkedIn drafts", "article selection" — phrases a user would plausibly say. Not 5 because a few common synonyms (e.g. "posts", "articles", "blog") are absent.

4 / 5

Distinctiveness Conflict Risk

A clear personal niche (Baptiste's LinkedIn content) with distinct triggers, and the explicit delimiter "rather than corporate Tessl blog reviews" wards off the nearest overlapping skill. Minimal conflict risk.

5 / 5

Total

18

/

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/baptiste-content-advisor/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.