update-knowledge-base

Maintain and update product knowledge base from releases, features, and project changes with optional wiki sync

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/update-knowledge-base/SKILL.md

Quality

Content

57%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 highly actionable with concrete commands, globs, MCP tool names, and templates across a well-sequenced 6-phase workflow, but it is padded and monolithic — inlining templates and agent prompts that would benefit from reference files, and missing a post-execution validation loop for a batch operation.

Suggestions

Add an explicit post-write verification step in Phase 4 (e.g., re-read each updated entry and confirm frontmatter/version/history are consistent before moving on) to lift workflow clarity past the batch-operation cap.

Move the large reusable templates (new-entry template, update-log template) and the three agent prompt specs into files under references/ and link to them, reducing the SKILL.md to an overview.

Trim the verbose Phase 1 multiple-choice menu and the KB organization tree to the essentials; assume Claude can infer standard directory layout from the glob examples.

Dimension	Reasoning	Score
Conciseness	The body is mostly purposeful action scaffolding without explaining concepts Claude already knows, but at ~362 lines it carries noticeable padding — the full update-log template, KB organization tree, Phase 1 menu, and repeated plan-presentation blocks could be tightened.	3 / 5
Actionability	Provides concrete, executable guidance — specific globs ('05-knowledge/*/.md'), real commands ('gh release list --repo ... --json tagName,name,body,publishedAt'), named MCP tools, and copy-paste frontmatter templates — with only justified placeholders like '[CUSTOMIZE: your-org/your-repo]' keeping it short of fully copy-paste ready.	4 / 5
Workflow Clarity	The 6-phase sequence is clear with explicit approval gates ('Wait for user approval before making changes', 'NEVER auto-publish'), but this batch/destructive operation lacks a post-write validate→fix→retry feedback loop, so per the batch-operations cap workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	Sections are well-organized into phases, but with no bundle files present the SKILL.md inlines substantial content that belongs in separate references — the new-entry template, update-log template, and three multi-line agent prompt specs — keeping it at 'some structure but content that should be separate is inline'.	3 / 5
	Total	13 / 20 Passed

Description

58%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 clearly states what the skill does and stakes out a distinct niche, but it omits an explicit 'Use when...' trigger clause and lacks the natural user phrasings that would drive reliable activation. It sits solidly at the midpoint of the scale.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user says "update knowledge base", "update KB", "sync knowledge", or after a release, feature launch, or architecture change.'

Surface the natural trigger phrases already in the body ('update KB', 'sync knowledge', 'update product docs') into the description to improve trigger-term coverage.

Expand the action verbs beyond 'maintain/update' to name concrete outcomes (e.g., create, update, deprecate, and sync KB entries) for fuller capability specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete action sources — 'Maintain and update product knowledge base from releases, features, and project changes with optional wiki sync' — but the distinct verbs are limited to maintain/update/sync, leaving minor coverage gaps short of the comprehensive 5 anchor.	4 / 5
Completeness	The 'what' is clear, but there is no explicit 'Use when...' trigger clause; 'when' is only weakly implied via 'from releases, features, and project changes', so per the missing-trigger-clause guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Contains relevant keywords ('knowledge base', 'releases', 'features', 'wiki sync') but misses the natural phrases users would actually say ('update KB', 'sync knowledge', 'update product docs') — those appear only in the body, not the description.	3 / 5
Distinctiveness Conflict Risk	The 'product knowledge base' + 'wiki sync' niche is mostly distinct from other skills, with only minor overlap risk against general docs/release-notes skills, fitting the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: huytieu/COG-second-brain
Path: .claude/skills/update-knowledge-base/SKILL.md
Commit: cb4644d

Reviewed: 2 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.