CtrlK
BlogDocsLog inGet started
Tessl Logo

update-cog

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

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

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 content is highly actionable with executable commands and a well-sequenced, safeguarded workflow; it is concise and well-structured, with only minor room to tighten notes and add a post-update validation step.

DimensionReasoningScore

Conciseness

The body is efficient — concrete git commands in code blocks, no padding explaining concepts Claude already knows — with only minor over-explanation (e.g. the "Important Notes" reiterating the .gitignore rationale) that could be trimmed.

4 / 5

Actionability

Every step provides copy-paste-ready, fully executable git commands (`git remote add`, `git fetch`, `git show`, `git diff`, `git checkout`, the commit line) covering the common update cases.

5 / 5

Workflow Clarity

A clearly sequenced 7-step process with an explicit pre-update customization-detection checkpoint and user-choice feedback loop; held below 5 because step 7 verify is summarization rather than a post-update correctness validation.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Purpose, When to Invoke, 7-step Process Flow, Alternative, Important Notes) with no nested references; as a cohesive single-workflow skill it is appropriately kept inline, with only minor organization gaps.

4 / 5

Total

17

/

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 is specific and distinct, clearly stating what the skill does and its safety constraint, but it lacks an explicit "Use when..." trigger clause, which caps its completeness and trigger-term coverage.

Suggestions

Add an explicit "Use when..." clause listing natural trigger phrases such as "update COG", "check for COG updates", or "get the latest COG version".

Include common synonyms or the version-file trigger (e.g. mentions of COG-VERSION) to broaden natural keyword coverage.

Consider naming the upstream source explicitly to further reduce overlap with generic git-update skills.

DimensionReasoningScore

Specificity

"Check for and apply upstream COG framework updates (skills, docs, scripts) without touching personal content" names the domain, two concrete actions (check, apply), the file scopes, and a safeguard constraint — listing several specific actions with only minor coverage gaps.

4 / 5

Completeness

The description gives a clear "what" but no explicit "when"/"Use when..." trigger guidance; per the judging guidelines, a missing "Use when" clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like "update", "check for", "upstream COG framework updates" are relevant and somewhat natural, but common variations or synonyms a user would actually say (e.g. "get latest COG version") are missing from the description.

3 / 5

Distinctiveness Conflict Risk

"upstream COG framework updates" carves a specific niche with distinct triggers and low conflict risk, though "framework updates" could minorly overlap with generic git/update skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
huytieu/COG-second-brain
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.