SkillAgentSearch skills...

update-cog

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

Install / Use

npx skills add huytieu/COG-second-brain --skill update-cog

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Supported Platforms

Universal

Our assessment of update-cog

update-cog scores 86/100 on our quality scale, 736th of 1,155 Content & Media skills we index.

Its SKILL.md is 3.6 KB long, well organised into 22 sections with 6 code examples: a solid amount of guidance for an agent.

With 1,216 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
12/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so update-cog is actively maintained.
  • Our last check on 2026-11-03 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

update-cog compared with similar skills

All 4 of these similar skills score higher than update-cog; compare them before choosing.

SkillScoreStarsUpdatedFormat
update-cog (this skill)by huytieu861.2k59d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install update-cog?
Run npx skills add huytieu/COG-second-brain --skill update-cog. The install tabs above show the steps for each supported agent.
Which AI agents does update-cog work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is update-cog safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is update-cog still maintained?
The repository was last updated about 2 months ago, so update-cog is actively maintained.

name: update-cog description: Check for and apply upstream COG framework updates (skills, docs, scripts) without touching personal content roles: [all] integrations: [git]

COG Update Skill

Purpose

Help the user update their COG framework files (skills, documentation, scripts) from the official upstream repository without risking their personal content (braindumps, profiles, notes).

When to Invoke

  • User asks to "update COG", "check for updates", or "get latest COG version"
  • User mentions wanting new skills or features from upstream
  • User asks about their COG version

Process Flow

1. Check Current Version

Read COG-VERSION from the vault root. If it doesn't exist, inform the user they may be on an older version that predates version tracking.

2. Ensure Upstream Remote

# Add the upstream remote if not already present
git remote get-url cog-upstream 2>/dev/null || \
  git remote add cog-upstream https://github.com/huytieu/COG-second-brain.git

# Fetch latest
git fetch cog-upstream main --quiet

3. Compare Versions

# Local version
cat COG-VERSION

# Upstream version
git show cog-upstream/main:COG-VERSION

If versions match, tell the user they're up to date.

4. Show What Changed

For each framework file, compare local vs upstream:

git diff HEAD..cog-upstream/main -- <file>

Framework files (safe to update — never contain user content):

  • Core docs: README.md, SETUP.md, AGENTS.md, GEMINI.md, CHANGELOG.md, CONTRIBUTING.md
  • Skills: .claude/skills/*/SKILL.md
  • Powers: .kiro/powers/*/POWER.md
  • Gemini: .gemini/commands/*.toml, .gemini/skills/*.md
  • Config: .claude-plugin/plugin.json, marketplace-entry.json, .gitignore
  • Scripts: cog-update.sh
  • Version: COG-VERSION

5. Detect Customizations

Before updating, check if the user has customized any framework files:

# Show how the working tree differs from current upstream HEAD.
# NOTE: this cannot tell a local customization apart from an upstream
# change you have not pulled yet — both show up as a diff. Treat any
# output as "needs a look", not as proof the user edited the file.
git diff cog-upstream/main -- <file>

If a file differs, warn the user and offer options:

  • Keep yours: Skip this file
  • Use upstream: Overwrite with the new version
  • Backup + update: Save current as <file>.backup-YYYYMMDD then update

6. Apply Updates

For files the user approves:

# Surgical file replacement — no merge, no rebase, zero conflict risk
git checkout cog-upstream/main -- <file>

7. Verify & Summarize

After updating:

  • Show the new version number
  • List all files that were updated
  • List any files the user chose to skip
  • Suggest committing the update:
    git add -A && git commit -m "Update COG framework to v<new-version>"
    

Alternative: Shell Script

For users who prefer a non-AI update, mention the update script:

./cog-update.sh           # Interactive
./cog-update.sh --check   # Just check for updates
./cog-update.sh --dry-run # Preview changes
./cog-update.sh --force   # Update everything

Important Notes

  • Content folders are NEVER touched: 00-inbox/, 01-daily/, 02-personal/, 03-professional/, 04-projects/, 05-knowledge/, 06-templates/ contain user data and are always ignored
  • The .gitignore is designed so content folders are excluded from upstream tracking (only .gitkeep files are tracked)
  • The update script updates itself — cog-update.sh is in the framework file list
  • No merge conflicts possible — this uses git checkout for surgical file replacement, not git merge or git rebase

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryContent
Updated1mo ago
Forks144

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions