home / skills / tdhopper / dotfiles2.0 / add-knowledge

add-knowledge skill

safe

This skill helps you add notes to Tim's Spotify knowledge base from Claude Code sessions by organizing and committing updates.

npx playbooks add skill tdhopper/dotfiles2.0 --skill add-knowledge

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

886 B

---
name: add-knowledge
description: Add notes and learnings to Tim's work knowledge base at Spotify from any Claude Code session
---

You are helping Tim add notes to his work knowledge base at Spotify.

**Repository**: /Users/thopper/c/knowledge

# Workflow

1. **Change to the knowledge repo**: `cd /Users/thopper/c/knowledge`
2. **Read the instructions**: The repo's CLAUDE.md contains all organization rules and file templates
3. **Process the user's notes**: Follow the instructions in CLAUDE.md to organize and save the content
4. **Commit and push**: Always commit changes with a clear message and push to main

# Instructions

All organization rules, directory structure, file templates, and guidelines are in `/Users/thopper/c/knowledge/CLAUDE.md`. Read that file first, then follow it exactly.

Keep responses concise - just acknowledge, organize, commit, push, and confirm.

Overview

This skill adds notes and learnings from Claude Code sessions into Tim's work knowledge base at Spotify. It automates organizing content, applying repository templates and rules, and committing changes to the main branch. The goal is fast, consistent updates that keep the knowledge repo clean and discoverable.

How this skill works

The skill changes into the knowledge repository, reads the repository’s CLAUDE.md to learn organization rules and templates, and then formats the session notes to match those rules. It creates or updates files in the proper directories, writes clear commit messages, and pushes changes to main. Each update is validated against the repo’s templates and guidelines before committing.

When to use it

After a Claude Code session with actionable notes or learnings to save
When creating new how-tos, troubleshooting notes, or design decisions
When consolidating meeting takeaways or personal research into the knowledge base
Before ending a work session to ensure knowledge is preserved and versioned

Best practices

Always read CLAUDE.md in the repo first and follow its templates exactly
Keep each file focused: one topic or learning per file with clear metadata
Use descriptive commit messages that summarize what was added or changed
Place content in the existing directory structure; avoid ad-hoc folders
Review diffs locally before pushing to catch formatting or template errors

Example use cases

Turn a debugging session with Claude into a step-by-step troubleshooting doc
Extract architecture notes from a design discussion and store them under decisions
Save concise onboarding tips discovered during pair programming
Capture experimental commands, config snippets, and their rationale for future reference

FAQ

Do I need to manually run any scripts?

No; the skill performs the repository change, formatting, commit, and push steps after you provide the session notes.

What if CLAUDE.md changes?

The skill reads CLAUDE.md each time before organizing content, so it adapts to updated rules and templates.