update-knowledge-base

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

Quality

56%

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

77%

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 a clear, well-gated multi-phase workflow, but it is verbose and monolithic: large templates and reference material are inline with no bundle files to enable progressive disclosure.

Suggestions

Move the large KB-entry template, update-log template, and directory-structure block into separate reference files (e.g. references/templates.md) and link to them from SKILL.md.

Tighten or trim placeholder-heavy scaffolding to reduce token load without losing actionability.

Consider extracting the per-agent prompt blocks (release-scanner, existing-kb-auditor, tracker-feature-collector) into a referenced file to keep the overview concise.

Dimension	Reasoning	Score
Conciseness	The ~355-line body is mostly procedural rather than concept-explaining, but the large inline KB-entry template, update-log template, and directory-structure block add padding that could be tightened; it is not lean enough to earn the top score.	2 / 3
Actionability	It provides concrete, executable guidance: specific Globs, gh CLI commands with JSON fields, named MCP tool calls, mkdir commands, and copy-paste templates; placeholders like [CUSTOMIZE: your-org/your-repo] are explicitly flagged user-specific customization, not pseudocode.	3 / 3
Workflow Clarity	A clear six-phase sequence is paired with explicit validation/approval checkpoints ('Wait for user approval before making changes', 'NEVER auto-publish') and an approval gate before batch/destructive execution, plus error-handling and fallback sections.	3 / 3
Progressive Disclosure	No bundle files (references/scripts/assets) exist and the entire content is inline; large reference-style material (templates, directory structure) that should be split into separate files lives in SKILL.md with no one-level-deep references, though sectioning is otherwise good.	2 / 3
	Total	10 / 12 Passed

Description

35%

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 conveys the skill's purpose and domain but omits explicit user trigger phrases and a 'Use when' clause, capping trigger quality and completeness. It is solid but not optimized for skill routing.

Suggestions

Add a 'Use when...' clause with natural trigger phrases users would say, e.g. 'Use when the user says update knowledge base, update KB, sync knowledge, or after a release/feature launch'.

List concrete actions (e.g. 'audit stale entries, create and update KB files, mark deprecations, sync to Confluence/Notion') to raise specificity.

Add distinctiveness cues (e.g. 'product/feature knowledge base, not general docs') to reduce overlap with document-editing skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('product knowledge base') and several actions (maintain, update, sync to wiki) plus source categories ('releases, features, and project changes'), but does not enumerate a comprehensive list of concrete actions.	2 / 3
Completeness	It states what the skill does, but lacks any explicit 'Use when...' trigger guidance; per the rubric, a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	The description contains no natural user-spoken trigger phrases such as 'update knowledge base' or 'sync knowledge'; those appear only in the body, leaving the description with functional jargon and no user-facing keywords.	1 / 3
Distinctiveness Conflict Risk	The product-KB-maintenance-with-wiki-sync niche is reasonably specific, but the absence of distinct trigger phrases means it could still overlap with general documentation-update skills.	2 / 3
	Total	7 / 12 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: dfbf9e9

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.