CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blog-post-writer

Transform brain dumps into polished blog posts in Nick Nisi's voice. Use when the user wants to write a blog post with scattered ideas, talking points, and conclusions that need organization into a cohesive narrative with Nick's conversational, authentic, and thoughtful tone.

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 ./skills_all/blog-post-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 well structured for an instruction-only skill, with concrete voice guidance, example patterns, and a clear six-step workflow ending in a review checklist and user feedback loop. However, the process critically depends on two reference files that are absent from the bundle, and the voice guidance is repeated across four sections at noticeable token cost.

Suggestions

Add the actual references/voice-tone.md and references/story-circle.md files to the bundle, or remove the load instructions and consolidate their essential content inline so the six-step process is executable as shipped.

Merge the repeated voice guidance from 'Key characteristics', 'Write in Nick's Voice', 'Do/Don't', and the step-6 checklist into a single authoritative section to cut duplicate tokens (vulnerability, varied length, humor, and ending momentum each appear 3-5 times).

Trim the redundancy between the 'Bundled Resources' annotations and the process steps that re-describe when to read each reference — one clearly signaled mention is enough.

DimensionReasoningScore

Conciseness

The same voice guidance is repeated across four sections: vulnerability appears as "Vulnerable and authentic", "Show vulnerability where appropriate", "Admit uncertainty or being wrong" / "Hide mistakes or uncertainty", and "Does it show vulnerability appropriately?"; similar duplication occurs for conversational tone, varied paragraph length, humor, and endings. Content is skill-specific (no explanation of concepts Claude already knows), but the systematic repetition could be consolidated into one section, matching 'mostly efficient but could be tightened' rather than the lean score-4/5 anchors.

3 / 5

Actionability

Concrete guidance exists — explicit Do/Don't lists, example patterns with real markdown snippets ("I must have heard that phrase a hundred times in the last year"), and a fully worked workflow example — but steps 2 and 3 instruct "Load `references/voice-tone.md`" and "Read `references/story-circle.md`" and neither file exists in the bundle. Missing key dependencies keep this at 'some concrete guidance but incomplete' rather than the mostly-executable score-4 anchor.

3 / 5

Workflow Clarity

A clear six-step sequence (receive → read voice → check story → organize → write → review) with an explicit review checklist ("Does it sound conversational?... Does it end with momentum?") and a feedback loop ("Show the post to the user for feedback and iterate") matches 'clear sequence with most checkpoints present'. It falls short of 5 because steps 2-3 are unexecutable as bundled and the checklist largely restates earlier sections rather than adding validation detail.

4 / 5

Progressive Disclosure

Internal structure is well organized with a dedicated Bundled Resources section clearly signaling one-level-deep references ("references/voice-tone.md - Complete voice and tone guide. Read this first"), but scoring against the actual bundle shows no references/ directory exists — both referenced paths are dangling. Good organizational intent, broken in practice: 'some structure but could be better organized' rather than the well-placed score-4 anchor.

3 / 5

Total

13

/

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.

The description is strong: it states a clear what, an explicit and specific when-clause with natural trigger phrases, and a highly distinctive niche (a specific author's voice). Its only weakness is modest action coverage — one composite transformation rather than a list of several discrete capabilities.

DimensionReasoningScore

Specificity

"Transform brain dumps into polished blog posts" and "organization into a cohesive narrative" name the domain plus 1-2 concrete actions, matching the 'Processes PDF files and extracts content' anchor. It does not list several distinct actions, so the score-4 anchor ('Extracts text from PDF files, fills forms, converts pages to images') does not fit; it is clearly above the vague single-action anchors.

3 / 5

Completeness

Explicitly answers both: what ("Transform brain dumps into polished blog posts in Nick Nisi's voice") and when ("Use when the user wants to write a blog post with scattered ideas, talking points, and conclusions that need organization into a cohesive narrative"). The when-clause contains concrete trigger conditions, matching the top anchor; it is clearly more explicit than the score-4 example where the when is generic.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "write a blog post", "brain dumps", "scattered ideas", "talking points", "conclusions". A few natural synonyms are missing (e.g., "article", "draft", "organize my notes"), so it falls just short of the comprehensive-synonyms anchor at 5 but is well above the 'Works with PDF files' level of partial keyword coverage.

4 / 5

Distinctiveness Conflict Risk

"in Nick Nisi's voice" and "Nick's conversational, authentic, and thoughtful tone" carve out a clear, named niche with triggers unlikely to fire for generic writing or editing skills. This is a distinct trigger set, not the broad overlap of 'Helps with document files'.

5 / 5

Total

17

/

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

referenced_paths_exist

Referenced path issues: 2 possibly missing (references/story-circle.md, references/voice-tone.md)

Warning

Total

15

/

16

Passed

Repository

Microck/ordinary-claude-skills

Path

skills_all/blog-post-writer/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.