CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blog-writer

Plan, write, and review VS Code blog posts. ALWAYS use this skill when the user asks to "write a blog post", "draft a blog", "add a blog post for", "review this blog post", or provides a feature/issue/PR to announce on the VS Code blog. For new posts, it proposes an outline and asks clarifying questions first, and does not edit any files until you approve the plan.

Quality

86%

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

73%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 well-structured, genuinely actionable instruction skill with an exemplary two-phase plan-first workflow and an explicit approval checkpoint. Its main weakness is token efficiency: guardrail rules are repeated verbatim across the Guardrails, Phase 1, Phase 2, and Review sections, and a few concrete artifacts (example frontmatter, example TODO comment) would make the drafting phase fully copy-paste ready.

Suggestions

State each guardrail once and cross-reference it instead of repeating: public availability, the blogs/<year>/<month>/<day>/ folder rule, the frontmatter field list, and the style-guide link each appear 3-4 times across Guardrails, Phase 1, Phase 2, and Review Mode; the style-guide link alone is repeated four times.

Add a filled-in example YAML frontmatter block and an example TODO image comment in Phase 2 so the drafting step is copy-paste ready (the field names and byline template are given, but never shown assembled).

Make 'check existing posts' for the next Order value concrete, e.g. a specific instruction or command to list recent posts and find the highest Order value.

DimensionReasoningScore

Conciseness

The body is directive and free of concept over-explanation, but systematically restates the same rules across sections: public availability appears in Guardrails, Phase 1 step 4, and Review step 3; the folder path 'blogs/<year>/<month>/<day>/' appears three times; the style-guide link is repeated four times; and 'Happy coding! 💙' is spelled out three times. This is more than minor trimming — the Guardrails section largely previews the Phase 1 steps, so the file could be noticeably tightened without losing clarity.

3 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: exact frontmatter field names ('Order', 'TOCTitle', 'MetaDescription' under 160 chars), a byline template '<Month> <day>, <year> by [<author>](<social link>)', 'gh' CLI for GitHub lookups, and a TODO placeholder policy for images. It falls short of fully copy-paste ready because there is no filled-in example frontmatter block or example TODO comment, and 'check existing posts' for the next Order value gives no concrete command.

4 / 5

Workflow Clarity

Both modes are clearly sequenced with explicit checkpoints: Phase 1 ends with 'Stop and wait for approval. Do not proceed to Phase 2 until the user explicitly approves', ambiguity triggers clarifying questions ('If it is ambiguous or lacks detail, ask clarifying questions before continuing'; framing confirmation before proposing the outline), and Phase 2 plus Review mode include verification steps (public-availability check, technical claims verified via gh, persona/intent check). This is not a destructive or batch operation, so no validation cap applies.

5 / 5

Progressive Disclosure

Good structure with clear sections and well-signaled, one-level-deep references to the blog-writing and docs-writing instruction guides, and the workflow content is appropriately kept in SKILL.md. However, the skill ships no bundle files of its own, the referenced style guides live two directories up outside the bundle, and style-guide details (tone rules, frontmatter limits, closing CTA) are restated inline rather than left solely to the referenced guide — minor organization gaps that keep it below a 5.

4 / 5

Total

16

/

20

Passed

Description

96%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.

An excellent description that states concrete capabilities in third person and pairs them with an explicit, natural-language 'use when' clause containing multiple quoted trigger phrases. The only meaningful improvement is distinctiveness: adding a brief exclusion (e.g., not for release notes or API docs) would further reduce overlap with sibling writing skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering all modes — 'Plan, write, and review VS Code blog posts' plus 'proposes an outline and asks clarifying questions first, and does not edit any files until you approve the plan' — in third-person framing, matching the comprehensive-coverage anchor. It is not a 4 because the actions span the skill's full capability set (planning behavior, writing, reviewing) with no material gaps.

5 / 5

Completeness

It explicitly answers both questions: what ('Plan, write, and review VS Code blog posts') and when ('ALWAYS use this skill when the user asks to...') with concrete trigger phrases, plus behavioral expectations for new posts. This matches the anchor for clearly and explicitly answering both what and when.

5 / 5

Trigger Term Quality

It quotes the exact natural phrases a user would say — '"write a blog post"', '"draft a blog"', '"add a blog post for"', '"review this blog post"', and 'provides a feature/issue/PR to announce on the VS Code blog' — giving comprehensive verb-synonym coverage (write/draft/add/review/announce). It is not a 4 because no common natural variation of the request is missing.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (VS Code blog posts, with 'announce on the VS Code blog' scoping one trigger), but the primary quoted triggers like '"write a blog post"' and '"draft a blog"' are generic blog phrasing that a closely related general blog- or writing-skill would also match, and the description itself does not state the reference-docs/release-notes exclusion that the body relies on. This is 'mostly distinct; minor overlap risk' rather than the minimal-conflict 5 anchor.

4 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing, 5 suspicious

Warning

Total

14

/

16

Passed

Repository

microsoft/vscode-docs

Path

.github/skills/blog-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.