CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/blog-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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, actionable skill body with a clear two-phase write workflow, a separate review mode, and strong guardrails. It stays lean for an instruction-only skill. Adding concrete examples (a sample frontmatter block, a validate→fix→retry loop) would lift actionability and workflow clarity.

Suggestions

Include a concrete example YAML frontmatter block so the required fields and format are copy-paste ready.

Add an explicit verify-then-fix-retry loop (e.g., re-checking frontmatter constraints after edits) to strengthen the workflow's feedback loop.

Dedupe the style-guide link and "Happy coding! 💙" reminders to tighten conciseness.

DimensionReasoningScore

Conciseness

Mostly efficient instruction-only content that assumes Claude's competence without explaining basic concepts; minor repetition (style guide linked four times, "Happy coding! 💙" stated twice) could be trimmed.

4 / 5

Actionability

Provides concrete guidance: exact folder paths, enumerated frontmatter fields, byline format, a source-repo table, and gh CLI usage; lacks a concrete example frontmatter block or sample section.

4 / 5

Workflow Clarity

Two-phase workflow and Review Mode are clearly sequenced with explicit checkpoints (stop-and-wait for approval, verify public availability, verify technical claims); no explicit validate-then-fix-retry loop is specified.

4 / 5

Progressive Disclosure

Body is well-sectioned and references to the style guides are one-level-deep and clearly signaled; no bundle files exist, and references point to external instructions files rather than an organized in-bundle reference set.

4 / 5

Total

16

/

20

Passed

Description

83%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 that clearly states capabilities and provides explicit, natural trigger phrases for both writing and reviewing blog posts. The outline-first, no-edit-until-approval behavior adds useful specificity. Naming the sibling skills to disambiguate would push distinctiveness higher.

Suggestions

Mention the sibling skills (doc-writer, release-note-writer) in the description to further reduce overlap risk, mirroring the disambiguation already in the body.

Add "announce this on the blog" as an explicit trigger synonym to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("Plan, write, and review", "proposes an outline", "asks clarifying questions", "does not edit any files until you approve"), with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (plan/write/review with outline-first behavior) and when ("ALWAYS use this skill when..." with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Includes multiple natural trigger phrases users would say ("write a blog post", "draft a blog", "add a blog post for", "review this blog post", "announce on the VS Code blog"); a few synonyms are absent but coverage is strong.

4 / 5

Distinctiveness Conflict Risk

"VS Code blog posts" is a clear niche with blog-specific triggers and minimal conflict risk; the description alone does not name sibling skills (doc-writer, release-note-writer) to fully disambiguate.

4 / 5

Total

17

/

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.

Validation14 / 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
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.