CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-blog

You are a technical writer reviewing a VS Code blog post for clarity, conciseness, and adherence to the writing style guidelines.

Quality

68%

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

The body is maximally token-efficient and appropriately delegates the review criteria to a single, clearly signaled one-level-deep reference. Its main weakness is actionability: the skill never specifies how suggestions should be structured or delivered, leaving the output format and review scope implicit.

Suggestions

Specify the suggestion format, e.g. "For each issue, quote the original text, name the guideline it violates, and propose a concrete rewrite."

Clarify scope handling: state whether to review the entire post by default or the section passed as the argument.

Consider copying or referencing the style guidelines from within the skill's own directory so the bundle is self-contained and the link is verifiable.

DimensionReasoningScore

Conciseness

The body is two lean sentences — "Review the article for clarity, conciseness, and adherence to our blog post writing style guidelines" and "Provide concrete and practical suggestions for improvement" — with zero padding and full assumption of the model's competence, matching the anchor-5 example.

5 / 5

Actionability

As an instruction-only skill it names the three review criteria and points to the style-guidelines doc, but it leaves key details unspecified: no suggestion output format (e.g., issue + original text + rewrite), no example, and no guidance on section vs. whole-post scope — "some concrete guidance but incomplete".

3 / 5

Workflow Clarity

The single action (review against three criteria, produce concrete suggestions) is unambiguous in intent, and no validation is needed for a non-destructive task, but minor gaps — output format and how to handle a section vs. the full post — keep it below 5.

4 / 5

Progressive Disclosure

The one external reference ([writing style guidelines](../../instructions/blog-writing.instructions.md)) is clearly signaled and exactly one level deep, and the body is appropriately tiny; however, no bundle directories exist, and the reference escapes the skill directory via a ../../ relative path that is unverifiable from the skill's location — a minor organization gap versus anchor 5.

4 / 5

Total

16

/

20

Passed

Description

48%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 identifies a clear niche (VS Code blog post review) and names its three evaluation criteria, but it omits any trigger guidance and uses second-person role framing instead of third-person capability statements. As a result it answers "what" but not "when", limiting discoverability and specificity.

Suggestions

Rewrite in third person as a capability statement, e.g. "Reviews VS Code blog posts for clarity, conciseness, and adherence to the blog writing style guidelines, and provides concrete improvement suggestions."

Add a trigger clause: "Use when asked to review, edit, or give feedback on a blog post or draft, or when the user mentions the VS Code blog or writing style guidelines."

Include natural trigger synonyms such as "draft", "article", "proofread", and "writing feedback" so the skill surfaces for the phrasings users actually say.

DimensionReasoningScore

Specificity

"reviewing a VS Code blog post for clarity, conciseness, and adherence to the writing style guidelines" names the domain and one action with three criteria — anchor 3 material — but the second-person framing ("You are a technical writer") incurs the rubric's mandatory 1-point specificity penalty, landing at 2.

2 / 5

Completeness

The "what" is clear (review for clarity, conciseness, style-guideline adherence) but the "when" is entirely absent — no "Use when..." clause or equivalent trigger guidance — which is anchor 3 and also caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant keywords like "blog post", "review", and "writing style" are present, but there are no explicit trigger phrases and common variations users would say ("draft", "article", "edit", "proofread") are missing — matching anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

"VS Code blog post" plus "our blog post writing style guidelines" carves a mostly distinct niche (anchor 4), with only minor overlap risk from the overloaded term "review" and general writing/editing skills; it lacks the distinct trigger phrases that would justify a 5.

4 / 5

Total

12

/

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 suspicious

Warning

Total

14

/

16

Passed

Repository

microsoft/vscode-docs

Path

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