Loading...
Loading...
Found 150 Skills
Defragment and reorganize agent memory files: split bloated files, merge duplicates, remove stale information, and restructure the memory hierarchy. Use when memory files have grown unwieldy, contain redundancies, or need reorganization. Run periodically (weekly) or on demand.
Automatically create PRs for registering insights, patterns, and workflows obtained from the current project as skills to the TBSten/skills repository. It performs the full process consistently: collecting insights from the project's CLAUDE.md, .claude/rules/, .claude/skills/, and codebase, packaging them into reusable skills, and creating the corresponding PR. Use when requested: "Register insights to the skill repository", "contribute skill", "Share this insight", "Register as a skill", "Compile insights into a PR", "Turn this pattern into a skill". gh CLI and git must be installed.
Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs
LLM Wiki — persistent markdown knowledge base that compounds across sessions (Karpathy model)
Use when the agent needs access to information beyond its training data — knowledge sources, RAG pipelines, or grounding data.
Ingest documents into the Obsidian wiki by distilling their knowledge into interconnected wiki pages. Use this skill whenever the user wants to add new sources to their wiki, process a document or directory, import articles, papers, or notes into their knowledge base, or says things like "add this to the wiki", "process these docs", "ingest this folder". Also triggers when the user drops a file and wants it incorporated into their existing knowledge base. Also handles raw mode: "process my drafts", "promote my raw pages", or any reference to the _raw/ staging directory.
Apply the Knowledge-Based View (Grant, 1996) and Nonaka and Takeuchi's SECI model to analyze how organizations create, transfer, and integrate knowledge for competitive advantage. Use this skill when the user needs to design knowledge management systems, understand why knowledge transfer fails across teams, evaluate knowledge creation processes, or when they ask 'how do we capture tacit knowledge', 'why does knowledge stay siloed', or 'how can we turn individual expertise into organizational capability'.
Set up a new Obsidian knowledge base with the LLM Wiki pattern. Use when the user wants to create a wiki, second brain, personal knowledge base, initialize a vault, or says "onboard", "set up", "new wiki", or "new vault".
Process raw source documents into wiki pages. Use when the user adds files to raw/ and wants them ingested, says "process this source", "ingest this article", "I added something to raw/", or wants to incorporate new material into their wiki, second brain, or knowledge base.
Compiles and extracts session knowledge into a living, interconnected LLM-Wiki. Instead of writing isolated logs, it identifies key entities, updates cross-referenced topic files in docs/knowledgelib/, and maintains an index and chronological log. Use this to ensure persistent, compounding project knowledge.
Documents the results of a completed experiment or A/B test with statistical analysis, learnings, and recommendations. Use after experiments conclude to communicate findings, inform decisions, and build organizational knowledge.
Use when bootstrapping a new personal wiki for any knowledge domain — research, codebase documentation, reading notes, competitive analysis, or any long-term knowledge accumulation project.