update-cog

Check for and apply upstream COG framework updates (skills, docs, scripts) without touching personal content

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/update-cog/SKILL.md

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tight, actionable, well-sequenced procedure with executable commands, proper customization safeguards before destructive updates, and clear verification. Minor redundancy in the closing notes is the only token-efficiency nit.

Dimension	Reasoning	Score
Conciseness	The body is lean: a short purpose, trigger list, and a numbered procedure with copy-paste bash, avoiding beginner explanations of git or COG; every section earns its place with only minor redundancy between "Important Notes" and earlier steps.	3 / 3
Actionability	It provides fully executable, complete commands (git remote add/fetch/show/diff/checkout) plus concrete script invocations with flags, all copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	The 7-step flow is clearly sequenced with a decision/feedback loop in step 5 (detect customizations -> warn -> keep/use-upstream/backup options) and explicit verification in step 7, so the destructive checkout is properly gated rather than missing validation.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the single file is organized into well-signaled sections with no nested references, satisfying the simple-skill allowance for a clean, self-contained skill.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 concise and distinct with a clear what-statement and a useful content-safety guard, but it omits explicit trigger guidance and relies on somewhat generic action verbs. Adding a "Use when..." clause with natural user phrasing would lift completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to update COG, check for updates, get the latest COG version, or asks about their COG version."

Make the actions more concrete by mentioning the actual mechanics (fetch upstream, compare versions, diff files, checkout updates) rather than the generic "check for and apply".

Include common natural phrasings users would say ("get latest COG", "update my COG skills") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Check for and apply upstream COG framework updates (skills, docs, scripts)" names the domain and two actions plus scope categories, but the verbs ("check for", "apply") are general and do not enumerate the concrete update mechanics, matching the anchor that names domain and some actions without being comprehensive.	2 / 3
Completeness	It clearly states what the skill does ("Check for and apply upstream COG framework updates... without touching personal content") but lacks any "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "COG framework updates", "upstream", and "personal content" are relevant, but common natural variations a user might say ("get latest COG", "update my skills", "COG version") are absent, so it has some relevant keywords but missing variations.	2 / 3
Distinctiveness Conflict Risk	"upstream COG framework updates... without touching personal content" carves out a clear niche (COG framework updating with a content-preservation guard) that is unlikely to trigger for unrelated skills.	3 / 3
	Total	9 / 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-cog/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.