Capture Conversation
outline/outline
Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.
Maintain and update product knowledge base from releases, features, and project changes with optional wiki sync
Install Update Knowledge Base
$ npx skills add huytieu/COG-second-brain --skill update-knowledge-base -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install huytieu/COG-second-brain update-knowledge-base --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/huytieu/COG-second-brain.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/update-knowledge-base .claude/skills/update-knowledge-base && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "update-knowledge-base" agent skill from https://github.com/huytieu/COG-second-brain/tree/main/skills/update-knowledge-base into .claude/skills/update-knowledge-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-knowledge-base", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/huytieu/COG-second-brain/tree/main/skills/update-knowledge-baseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add huytieu/COG-second-brain --skill update-knowledge-base -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install huytieu/COG-second-brain update-knowledge-base --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/huytieu/COG-second-brain.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/update-knowledge-base .agents/skills/update-knowledge-base && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "update-knowledge-base" agent skill from https://github.com/huytieu/COG-second-brain/tree/main/skills/update-knowledge-base into .agents/skills/update-knowledge-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-knowledge-base", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add huytieu/COG-second-brain --skill update-knowledge-base -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install huytieu/COG-second-brain update-knowledge-base --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/huytieu/COG-second-brain.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/update-knowledge-base .cursor/skills/update-knowledge-base && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "update-knowledge-base" agent skill from https://github.com/huytieu/COG-second-brain/tree/main/skills/update-knowledge-base into .cursor/skills/update-knowledge-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-knowledge-base", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/huytieu/COG-second-brain.git --path skills/update-knowledge-base--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add huytieu/COG-second-brain --skill update-knowledge-base -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install huytieu/COG-second-brain update-knowledge-base --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/huytieu/COG-second-brain.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/update-knowledge-base .gemini/skills/update-knowledge-base && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "update-knowledge-base" agent skill from https://github.com/huytieu/COG-second-brain/tree/main/skills/update-knowledge-base into .gemini/skills/update-knowledge-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-knowledge-base", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install huytieu/COG-second-brain update-knowledge-baseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add huytieu/COG-second-brain --skill update-knowledge-base -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/huytieu/COG-second-brain.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/update-knowledge-base .github/skills/update-knowledge-base && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "update-knowledge-base" agent skill from https://github.com/huytieu/COG-second-brain/tree/main/skills/update-knowledge-base into .github/skills/update-knowledge-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-knowledge-base", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add huytieu/COG-second-brain --skill update-knowledge-base -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install huytieu/COG-second-brain update-knowledge-base --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/huytieu/COG-second-brain.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/update-knowledge-base .opencode/skills/update-knowledge-base && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "update-knowledge-base" agent skill from https://github.com/huytieu/COG-second-brain/tree/main/skills/update-knowledge-base into .opencode/skills/update-knowledge-base/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-knowledge-base", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
update-knowledge-base- GitHub stars
- 1.3k
- Token cost
- ~2.8k tokens
- SKILL.md length
- 525 words
- Files
- 1
- Skills in repo
- 37
- Repo updated
- First seen
- Licence
- MIT
At a glance
Maintain and update product knowledge base from releases, features, and project changes with optional wiki sync
- Works in 6 steps: Determine Update Scope → Gather Update Data → Identify Knowledge Updates → …
- Tasks that involve Knowledge bases
- SKILL.md covers When to Invoke, Agent Mode Awareness, Command: /update-knowledge-base and Pre-Flight Check, plus 4 more sections
- Calls gh
What it does
Update Knowledge Base is an agent skill from huytieu/COG-second-brain. Maintain and update product knowledge base from releases, features, and project changes with optional wiki sync
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Knowledge Management, covering Knowledge bases. The repository describes itself as: Self-evolving second brain with 35 AI skills, 10 agents, and people CRM. Closed-loop harness: a V-model verification lifecycle where the worker never grades its own homework… The licence is MIT.
When your agent uses it
- Tasks that involve Knowledge bases
Example prompts
- “/update-knowledge-base”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 36ac9d7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Update Knowledge Base loads about 2.8k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 525 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from huytieu/COG-second-brain at commit 36ac9d7, republished under its MIT licence (© huytieu). 525 words, ~2,752 tokens.
Download SKILL.mdSave it as
.claude/skills/update-knowledge-base/SKILL.md (or your agent's skills folder).- name
- update-knowledge-base
- description
- Maintain and update product knowledge base from releases, features, and project changes with optional wiki sync
- roles
- product-manager, engineering-lead, founder
- integrations
- github, linear, jira, confluence, notion
COG Update Knowledge Base Skill
When to Invoke
- After a release — update product knowledge with new features and changes
- User says "update knowledge base", "update KB", "sync knowledge", "update product docs"
- Periodic maintenance — ensure knowledge base reflects current product state
- After major feature launches, architecture changes, or deprecations
Agent Mode Awareness
Check agent_mode in 00-inbox/MY-PROFILE.md frontmatter:
- If
agent_mode: team— use parallel agents to scan multiple sources and update multiple knowledge files simultaneously - If
agent_mode: solo— process updates sequentially, one knowledge file at a time
Command: /update-knowledge-base
Pre-Flight Check
- Read
00-inbox/MY-INTEGRATIONS.mdfor active data sources and publishing targets - Read
00-inbox/MY-PROFILE.mdfor active projects - Get current timestamp: Run
date '+%Y-%m-%d %H:%M'using Bash - Scan existing knowledge base: Glob
05-knowledge/**/*.mdto understand current state
Execution Strategy
Phase 1: Determine Update Scope
Ask the user (or infer from context):
What triggered this knowledge base update?
a) New release shipped (I'll pull changes from release notes and tracker)
b) Feature launched or updated (I'll document the feature)
c) Architecture or technical change (I'll update technical knowledge)
d) Periodic review (I'll scan for anything that's changed since last update)
e) Custom — describe what needs updatingPhase 2: Gather Update Data
Team Mode (parallel agents)
Launch data-gathering agents using the Task tool with run_in_background: true:
Agent: "release-scanner" (for release-triggered updates)
Scan recent releases and release notes for knowledge base updates.
1. Check vault for recent release notes:
Glob: 04-projects/*/release-notes/*.md
Read the most recent release notes for each active project
2. If GitHub is active:
gh release list --repo [CUSTOMIZE: your-org/your-repo] --limit 5 --json tagName,name,body,publishedAt
Get the latest release details
3. If Linear is active:
Use ToolSearch to load Linear tools
Check recently completed cycles and milestones for shipped features
Extract from each source:
- New features added (name, description, user impact)
- Features modified (what changed)
- Features deprecated or removed
- Technical changes (architecture, API, infrastructure)
- Bug fixes that affect documented behavior
Return: structured list of knowledge updates neededAgent: "existing-kb-auditor"
Audit the current knowledge base for staleness and gaps.
1. Read all files in 05-knowledge/:
Glob: 05-knowledge/**/*.md
2. For each file, extract:
- Last updated date (from frontmatter or file modification)
- Topics covered
- Products/features documented
- Any [TODO] or [OUTDATED] markers
3. Cross-reference with active projects from MY-PROFILE.md:
- Are all active projects represented in the KB?
- Are there KB entries for discontinued/inactive projects?
4. Check for:
- Files not updated in >90 days (potentially stale)
- Topics mentioned in recent release notes but missing from KB
- Contradictions between KB entries and recent changes
Return: staleness report, gap analysis, and recommended updatesAgent: "tracker-feature-collector" (for feature-triggered updates)
Collect current feature/product state from project trackers.
If Linear is active:
1. Use ToolSearch to load Linear tools
2. List all projects and their current status: mcp__claude_ai_Linear_2__list_projects
3. List all initiatives: mcp__claude_ai_Linear_2__list_initiatives
4. For key initiatives, get details: mcp__claude_ai_Linear_2__get_initiative
If GitHub is active:
1. Check repo README and docs for current feature descriptions
2. Review recent PRs that touch documentation:
gh pr list --repo [CUSTOMIZE: your-org/your-repo] --state merged --search "label:docs merged:>=[30_DAYS_AGO]" --json number,title,body --limit 20
Return: current product/feature state for knowledge base comparisonSolo Mode
Run the most relevant agent sequentially based on the update trigger.
Phase 3: Identify Knowledge Updates
Compare gathered data against existing knowledge base to determine:
- New entries needed — features, products, or topics not yet documented
- Updates needed — existing entries that need modification
- Deprecation/removal — entries for features that no longer exist
- Gap filling — missing context, examples, or cross-references
Present the update plan to the user:
Knowledge Base Update Plan:
NEW entries to create:
1. [Topic] — [reason: new feature in v[X]]
2. [Topic] — [reason: gap identified]
UPDATES to existing entries:
1. 05-knowledge/[file].md — [what needs changing]
2. 05-knowledge/[file].md — [what needs changing]
DEPRECATION candidates:
1. 05-knowledge/[file].md — [reason: feature removed in v[X]]
STALE entries (>90 days, may need review):
1. 05-knowledge/[file].md — last updated [date]
Proceed with these updates? (yes / modify plan / skip specific items)Wait for user approval before making changes.
Phase 4: Execute Updates
4.1 Create New Knowledge Entries
For each new entry, use this template:
---
type: knowledge
domain: [product/technical/process/architecture]
project: [project-name]
topic: [topic name]
created: [YYYY-MM-DD HH:MM]
last_updated: [YYYY-MM-DD]
source: [release-notes/feature-launch/manual/periodic-review]
version: "1.0"
tags: ["#knowledge", "#[project]", "#[topic-area]"]
related:
- [path to related KB entry]
- [path to related project file]
---
# [Topic Title]
## Overview
[Clear, concise description of the topic — what it is, why it matters]
## Current State
[How this feature/system/process works as of the last update]
### Key Details
- **[Detail 1]:** [Value/description]
- **[Detail 2]:** [Value/description]
- **[Detail 3]:** [Value/description]
## History
| Date | Version | Change | Source |
|------|---------|--------|--------|
| [Date] | [Version] | [What changed] | [Release notes / PR / manual] |
## Related
- [Link to related KB entries]
- [Link to PRDs if applicable]
- [Link to project files]
## Notes
[Additional context, caveats, or open questions]
---
*Last updated: [YYYY-MM-DD] | Source: [what triggered this update]*Save to: 05-knowledge/[domain]/[topic-slug].md
mkdir -p "05-knowledge/[domain]"4.2 Update Existing Entries
For each update:
- Read the existing file
- Update the relevant sections
- Add a row to the History table
- Update
last_updatedin frontmatter - Update
version(increment minor version)
Show full SKILL.md (238 more words)Show less
4.3 Mark Deprecations
For deprecated entries:
- Add
status: deprecatedto frontmatter - Add a deprecation notice at the top of the file:
markdown > **DEPRECATED:** This feature was removed/replaced in [version/date]. See [replacement link] for the current approach. - Do NOT delete the file — historical context is valuable
Phase 5: Generate Update Summary
Create an update log:
---
type: kb-update-log
date: [YYYY-MM-DD]
created: [YYYY-MM-DD HH:MM]
trigger: [release/feature/periodic/manual]
tags: ["#knowledge", "#update-log"]
---
# Knowledge Base Update — [YYYY-MM-DD]
## Trigger
[What caused this update: release X.Y.Z / feature launch / periodic review]
## Changes Made
### New Entries
| File | Topic | Domain | Source |
|------|-------|--------|--------|
| [path] | [topic] | [domain] | [source] |
### Updated Entries
| File | Changes | Previous Version | New Version |
|------|---------|-----------------|-------------|
| [path] | [summary of changes] | [old ver] | [new ver] |
### Deprecated Entries
| File | Reason | Replacement |
|------|--------|-------------|
| [path] | [reason] | [link to replacement or N/A] |
## Knowledge Base Health
- **Total entries:** [N]
- **Updated this session:** [N]
- **Created this session:** [N]
- **Deprecated this session:** [N]
- **Stale entries remaining (>90 days):** [N]
- **Coverage:** [assessment of how well the KB covers active projects]
---
*Generated by COG Knowledge Base Updater*Save to: 05-knowledge/_logs/kb-update-YYYY-MM-DD.md
mkdir -p "05-knowledge/_logs"Phase 6: Optional Wiki Sync (requires approval)
If Confluence or Notion is active, offer to sync updated entries:
Knowledge base updated locally. Would you like to sync to your wiki?
Active wiki platforms:
- [Confluence / Notion — whichever is active]
Options:
a) Sync all changed entries to [platform]
b) Sync specific entries only
c) Skip wiki sync (vault-only)NEVER auto-publish. Wait for explicit approval.
Confluence Sync
Use the /publish-to-confluence skill pattern for each entry being synced.
Notion Sync
1. Use ToolSearch to load Notion tools
2. Search for existing pages matching the KB entry: mcp__claude_ai_Notion__notion-search
3. If exists: update with mcp__claude_ai_Notion__notion-update-page
4. If new: create with mcp__claude_ai_Notion__notion-create-pagesKnowledge Base Organization
Recommended 05-knowledge/ structure:
05-knowledge/
_logs/ # Update logs
kb-update-YYYY-MM-DD.md
product/ # Product features, capabilities, roadmap
[feature-name].md
technical/ # Architecture, APIs, infrastructure
[system-name].md
process/ # Team processes, workflows, conventions
[process-name].md
domain/ # Domain knowledge, industry context
[topic-name].md
integrations/ # Integration docs, API references
[integration-name].mdFallback Behavior
| Scenario | Behavior |
|---|---|
| No trackers active | Work from vault data only (release notes, PRDs, project files) |
| No existing KB entries | Create the initial knowledge base structure and first entries |
| Wiki sync fails | All changes are already saved locally; inform user to sync manually |
| Very large KB (>50 files) | Process in batches, prioritize most recently changed entries |
| No recent changes found | Report that KB is up to date; suggest periodic review topics |
| Conflicting information | Flag conflicts for user resolution rather than auto-resolving |
Error Handling
- File conflicts: If an update would contradict a recent manual edit, present both versions to the user
- Context overflow: Process knowledge files in batches of 10
- Stale data sources: Warn if tracker data seems outdated (API issues)
- Missing project context: Ask user to clarify which project the knowledge relates to
© huytieu, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/update-knowledge-base of huytieu/COG-second-brain.
Open the folder on GitHubat commit 36ac9d7
Compare with similar skills
Update Knowledge Base next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Update Knowledge Base this skillhuytieu/COG-second-brain | 1.3k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Capture Conversationoutline/outline | 41k | — | ~474 | Automated safety check: Pass | Custom licence | |
| Project CairniBlinkQ/project-cairn | 235 | 2 repos | ~861 | Automated safety check: Pass | MIT | |
| LLM Wiki Knowledge GraphEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Find And Citeoutline/outline | 41k | — | ~537 | Automated safety check: Pass | Custom licence | |
| Xhs Virtual Productchenjin-cmd/xhs-virtual-product | 727 | — | ~862 | Automated safety check: Pass | MIT |
Similar skills
Project Cairn
iBlinkQ/project-cairn
Standardize how an AI-collaboration project turns work into reusable knowledge.
LLM Wiki Knowledge Graph
Egonex-AI/Understand-Anything
Detects a Karpathy-pattern LLM wiki and builds an interactive knowledge graph with entities, implicit relationships and topic clusters.
Find And Cite
outline/outline
Answer questions from the Outline knowledge base with quotes and links to the source documents; use when the user asks what the team knows, documented, or decided about a topic.
Xhs Virtual Product
chenjin-cmd/xhs-virtual-product
This skill helps plan, select, produce, and market Xiaohongshu (RED) virtual/digital products — templates, knowledge bases, test tools, study materials.
Openkb
VectifyAI/OpenKB
A skill your agent uses when the user asks about content in their OpenKB knowledge base — research topics, concepts compiled from their documents, cross-document synthesis — or mentions openkb, an…
More from huytieu/COG-second-brain
All 37 skills in this repoVoice Baseline
huytieu/COG-second-brain
Measure your own writing corpus for the words and sentence shapes you over-use, so an agent writing in your voice stops amplifying your tics into a style.
Daily Journal
huytieu/COG-second-brain
A passive daily work journal that Claude keeps FOR you so you never have to write it yourself.
Editorial Illustrations
huytieu/COG-second-brain
Generate meaning-carrying editorial data-illustrations in the monotykamary / Linear aesthetic (near-black grayscale, Inter display + mono labels, hairline framed figures) with a single coral accent.
Loop Engineering
huytieu/COG-second-brain
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns.
Knowledge Consolidation
huytieu/COG-second-brain
Build frameworks from scattered insights across all braindumps and notes
Release Video
huytieu/COG-second-brain
Turn a product release (the list of shipped items plus real screen recordings) into a motion recap video and one explained demo per feature, with sound effects tied to on-screen motion and a…
Related
Categories
Questions about Update Knowledge Base
What does Update Knowledge Base do?
Maintain and update product knowledge base from releases, features, and project changes with optional wiki sync. Update Knowledge Base is an agent skill from huytieu/COG-second-brain.
When should I use Update Knowledge Base?
Update Knowledge Base fits situations like: tasks that involve Knowledge bases.
How do I install Update Knowledge Base in Claude Code?
Run `npx skills add huytieu/COG-second-brain --skill update-knowledge-base -a claude-code`. Or copy the skill folder (skills/update-knowledge-base in huytieu/COG-second-brain) into .claude/skills/update-knowledge-base in your project. Claude Code loads it when a task matches its description.
How do I install Update Knowledge Base in Codex?
Run `npx skills add huytieu/COG-second-brain --skill update-knowledge-base -a codex`. Or copy the skill folder (skills/update-knowledge-base in huytieu/COG-second-brain) into .agents/skills/update-knowledge-base in your project. Codex loads it when a task matches its description.
Can I use Update Knowledge Base in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add huytieu/COG-second-brain --skill update-knowledge-base -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-knowledge-base, .gemini/skills/update-knowledge-base, .github/skills/update-knowledge-base and .opencode/skills/update-knowledge-base in your project.
What does Update Knowledge Base need to run?
Going by SKILL.md and its folder, Update Knowledge Base needs the command-line tools its instructions call (gh).
Does Update Knowledge Base access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Update Knowledge Base safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Update Knowledge Base use?
Update Knowledge Base is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Update Knowledge Base use?
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Update Knowledge Base?
Skills that share tags, products or a category with Update Knowledge Base: Capture Conversation (outline/outline, 41k stars), Project Cairn (iBlinkQ/project-cairn, 235 stars), LLM Wiki Knowledge Graph (Egonex-AI/Understand-Anything, 86k stars) and Find And Cite (outline/outline, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Update Knowledge Base?
huytieu (a GitHub user) maintains it in huytieu/COG-second-brain, which has 1,265 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 2, 2026.
Source: huytieu/COG-second-brain on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.