tim-hub/kb
personal/skills/kb/SKILL.md
Saves insights, decisions, and learnings from the current conversation to the project knowledge base. Use when the user wants to remember something or after solving a non-obvious problem.
$ install --global
skillsauthnpx skillsauth add tim-hub/powerball kbInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 20, 2026, 4:33 AM135.6s4 files scanned
SKILL.md
- name:
- kb
- description:
- Saves insights, decisions, and learnings from the current conversation to the project knowledge base. Use when the user wants to remember something or after solving a non-obvious problem.
- when_to_use:
- save this to kb, add to knowledge base, remember this, note this down, kb add, kb upsert, kb update, save insight, capture decision, stop hook save
- argument-hint:
- [optional: topic hint]
- user-invocable:
- true
- allowed-tools:
- Bash, Read
- model:
- haiku
Maintain the project knowledge base by upserting insights and information into a structured markdown file.
Setup Check
Before any operation, verify the KB is configured:
cat ~/.kb/config.json 2>/dev/null
If the config is missing or empty, invoke the kb-setup skill first.
Determine Topic and Content
- If an argument is provided: use it as the topic hint, derive content from the conversation context around that topic.
- If no argument: automatically summarise the current conversation — identify the most significant insight, decision, or pattern from the exchange, and use that as both the topic and content. Do not ask the user for input; proceed directly to upsert.
Get Project Context
- Get the project name from the current working directory folder name:
basename "$PWD" - Read
allow_list[0]from~/.kb/config.json— this is the base KB directory. - The KB file path is:
<allow_list[0]>/kb/<project-name>.md
Upsert Process
Run scripts/upsert.sh with the required arguments:
bash <skill-dir>/scripts/upsert.sh "<kb-file-path>" "<topic>" "<tags>" "<content>"
Where:
<kb-file-path>— full path to the project's KB markdown file<topic>— the section heading (derived from the conversation context or argument hint)<tags>— space-separated hashtags, e.g.#claude #performance #debugging<content>— the actual insight or information to save, formatted as bullet points (each line starting with-)
The script handles file creation from template, section detection via ripgrep, and appending or updating content.
What to Save
When triggered proactively (not by explicit user command), distill the conversation into:
- Topic: a short, specific heading (e.g., "JWT token refresh strategy", "Database migration approach")
- Tags: 1-4 hashtags starting with
#that categorize the topic (e.g.,#auth #security,#performance #database). Derive from the domain, technology, or concern the insight relates to. - Content: 2-5 bullet points capturing the key insight, decision rationale, or pattern discovered. Each line must start with
-. Never use plain prose.
Tags appear on the line immediately after the heading, e.g. #auth #security. They make sections findable via kb-search even when the topic heading isn't exact.
Avoid saving trivial or obvious information. Focus on non-obvious insights, gotchas, decisions with meaningful trade-offs, or patterns specific to this project.
Output
After the upsert, confirm briefly:
- What topic was saved
- The file path it was written to
- Whether it was a new section or an update to an existing one
References
- Example:
examples/kb.example.md— canonical format reference; match this exactly when generating topics and content - Template:
templates/kb.template.md— used when creating a new KB file - Script:
scripts/upsert.sh— handles all file I/O and ripgrep-based section detection
Related Skills
tim-hub/choosing-k8s-release-strategy
testing
VerifiedTrustedCommunity
Picks the right Kubernetes Deployment update strategy (RollingUpdate / Recreate / Blue-Green / Canary) for the situation. Use when configuring a new Deployment, changing rollout config, or deciding how to ship a risky change.
2SKILL.mdUpdated May 25, 2026
tim-hub/translate-markdown
tools
VerifiedTrustedCommunity
Translates a markdown file to a target language, preserving structure. Use when the user needs a markdown file translated.
2SKILL.mdUpdated May 21, 2026
tim-hub/language-translate
development
VerifiedTrustedCommunity
Translates text between any two languages while preserving source format. Use when the user needs to translate plain text, code, or markdown content.
2SKILL.mdUpdated May 21, 2026
tim-hub/creative-writing
testing
VerifiedTrustedCommunity
Generates written content — blog posts, social posts, emails, and marketing copy — matched to the project's existing voice. Use when the user needs written material.
2SKILL.mdUpdated May 21, 2026