Loading...
Loading...
Found 105 Skills
- **Role**: Niklas Luhmann for the AI age—turning complex tasks into **organic parts of a knowledge network**, not one-off answers.
Use when asking a question against a personal wiki built with wiki-init and wiki-ingest. Do not answer from general knowledge — always read the wiki pages first.
Use this skill to ingest external materials into the current project-scoped Obsidian KB as source notes under Sources/Papers, Sources/Web, Sources/Docs, Sources/Data, Sources/Interviews, or Sources/Notes.
Catalog GitHub starred repositories into a structured Obsidian vault with AI-synthesized summaries, normalized topic taxonomy, graph-optimized wikilinks, and Obsidian Bases (.base) index files for filtered views. Fetches repo metadata and READMEs via gh CLI, classifies repos into categories and normalized topics, generates individual repo notes with frontmatter, and creates hub notes for categories/topics/authors that serve as graph-view connection points. Use this skill when users want to: (1) Catalog or index their GitHub stars into Obsidian (2) Create a searchable knowledge base from starred repos (3) Organize and discover patterns in their GitHub stars (4) Export GitHub stars as structured markdown notes (5) Build a graph of starred repos by topic, language, or author For saving/distilling a specific URL to a note, use kcap instead. For browsing AI tweets, use ai-twitter-radar instead.
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.
Build and maintain a research repository that makes findings findable, reusable, and cumulative across the organization.
Compile durable knowledge into interlinked-markdown stores the "karpathy method" way — atomic files, [[wiki-links]], a maintained index. Use after producing research, intel, a digest, a learned non-obvious fact, or finishing any knowledge-shaped task, BEFORE you close it. Also when asked to "save this", "write this to the wiki", "update the wiki/memory", "log this finding", "structure this knowledge", or "follow the karpathy method".
Review the current session for durable learnings, then route each one through the five-way matrix: wiki page, guidance file, checkpoint, task annotation/plan, or discard. Use when the session uncovered decisions, architecture facts, commands, conventions, gotchas, or open questions that future sessions should inherit. Not for source ingestion or correcting stale wiki claims; use /loam::adding-to-memory or /loam::amending-memory. Routes goal-specific progress to /loam::setting-goals.
Answer questions against existing memory (the wiki substrate). Use this whenever the user is asking what is happening in the project, directory, codebase, architecture, workflow, decisions, or current state and the wiki likely contains the answer, even if they do not explicitly mention the wiki. Also use it for summaries, comparisons, and reusable analyses grounded in current wiki pages. Routes authoritative goal-state questions to /loam::setting-goals. Not for surfacing unresolved gaps; use /loam::reviewing-memory for that.
Intelligent Q&A Appender that appends Q&A content from conversations to existing notes or creates new independent cards. Adopting the C+I structure (Insight + Context), it resolves the conflict between "unintelligible after simplification" and "too verbose without simplification". Triggers: /qa, /ask
Structured web research workflow that ensures research results are incrementally saved to files, preventing loss due to session truncation. This skill is triggered when users say "research", "search for information", "help me look up", "learn about", or "latest information".
Shared optimization guidance plus CuTe Python DSL overlays. Use when: (1) selecting optimizations for a CuTe Python DSL kernel, (2) deciding whether a finding is shared or cute-dsl-specific, (3) recording CuTe Python DSL implementation notes, (4) reviewing the knowledge layout for cute-dsl work, (5) mapping shared patterns to a CuTe Python DSL implementation surface.