kb-article

Draft a knowledge base article from a resolved issue or common question. Use when a ticket resolution is worth documenting for self-service, the same question keeps coming up, a workaround needs to be published, or a known issue should be communicated to customers.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%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 a well-structured, highly actionable writing guidance skill with concrete templates, comparison tables, and a clear four-step workflow. Its main limitations are minor padding in editorial lead-ins, implicit rather than explicit validation checkpoints, and a large single-file monolith that could benefit from splitting templates into reference files.

Suggestions

Trim editorial lead-ins such as "Articles are useless if customers can't find them" and "Knowledge bases decay without maintenance" to lift conciseness toward 5.

Make validation explicit in the workflow (e.g., a step to verify the drafted steps reproduce the resolution, or a self-test checklist before publishing) to reach the top workflow-clarity anchor.

Move the per-article-type templates into one-level-deep reference files (e.g. references/templates.md) with clear links from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Most content earns its place — article-type templates, the good/bad title table, and the opening-sentence formula are high-value — but a few editorial lead-ins ("Articles are useless if customers can't find them", "Knowledge bases decay without maintenance") could be trimmed. Not a 5 because of these minor padded passages; not a 3 because the bulk is efficient and actionable.	4 / 5
Actionability	As an instruction-only skill it provides fully concrete, copy-paste-ready templates for each article type, a good/bad title comparison table, exact opening-sentence formulas, and explicit formatting rules covering the common cases. Absence of code is not penalized because the guidance is concrete and actionable.	5 / 5
Workflow Clarity	A clear four-step sequence (Understand → Draft → Generate → Offer Next Steps) with an output template and publishing notes; the operation is non-destructive so the validation cap does not apply. Not a 5 because validation checkpoints are implicit (SME review, suggested review date) rather than an explicit validate→fix→retry loop.	4 / 5
Progressive Disclosure	No bundle files exist, so this is a single self-contained file with a clear, well-organized section hierarchy and no nested references. Good structure and navigation, but it is a sizable monolith whose article-type templates could plausibly live in one-level-deep reference files, keeping it below 5.	4 / 5
	Total	17 / 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 answers both what the skill does and when to use it with concrete, natural trigger phrases and a distinct niche. The only mild gap is specificity, which lists the single drafting action rather than a fuller set of concrete capabilities.

Dimension	Reasoning	Score
Specificity	"Draft a knowledge base article from a resolved issue or common question" names the domain and one concrete action but does not enumerate a broader, comprehensive set of capabilities. Not a 2 because the action is concrete rather than generic, and not a 4 because only the single drafting action is listed.	3 / 5
Completeness	It explicitly answers both what ("Draft a knowledge base article from a resolved issue or common question") and when via a concrete "Use when..." clause listing multiple trigger scenarios. This matches the anchor for clearly and explicitly answering both with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases users would say appear throughout: "ticket resolution", "the same question keeps coming up", "workaround", "known issue". Good coverage but a few synonyms (e.g. "documentation", "help article") are absent, so it is not a 5.	4 / 5
Distinctiveness Conflict Risk	KB-article drafting from resolved tickets is a clear niche with distinct triggers (ticket resolution, recurring question, workaround, known issue) and minimal overlap with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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: anthropics/knowledge-work-plugins
Path: customer-support/skills/kb-article/SKILL.md
Commit: 8444efc

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.