Loading...
Loading...
Found 216 Skills
Use when users ask to capture conversation decisions, problems, and lessons into persistent notes (e.g. 'harvest', '/harvest', 'save this to second brain', 'document this work').
Generate a clean morning brief in Claude Code — pulls today's priorities, unposted content, and weather from your vault.
Generate review reports focusing on research questions and methodologies based on specified papers or categories, which can be used as interview review materials.
Annual strategic review and goal-setting interview for personal life/work domains with quarterly progress check-ins
Obsidian YAML frontmatter property management via the official CLI. Covers reading, setting, and removing properties/metadata on notes. Use when user mentions frontmatter, properties, metadata, YAML, or note attributes like status, tags, dates, aliases.
Fast, zero-friction capture of technical findings from the current conversation to the wiki's _raw/ staging area. Use this skill when the user says "/wiki-quick-chat-capture", "quick capture", "capture this finding", "save this bug fix", "capture this gotcha", "drop this to raw", "quick save to wiki", or wants to capture a non-obvious discovery mid-session without a full wiki-ingest run. Writes one _raw/ file per topic cluster in under 60 seconds — no subagents, no QMD updates, no manifest writes. Run /wiki-ingest or /data-ingest later to promote raw files to proper wiki pages.
Use this skill when the user requests to "read paper", "analyze paper", "summarize paper", "read a paper", "analyze literature", "help me look at this paper", "paper notes", or provides a PDF file that appears to be an academic paper. It is specialized for CV/DL papers. It also supports Zotero integration: "read this paper...", "quickly look at this paper...", "critically analyze this paper...", "read XXX from Zotero", "batch read papers under the VLA category in Zotero" **Important Trigger Phrases**: "read XXX", "read this one", "help me read" → must call this skill
Build and maintain a personal knowledge base using Karpathy's llm-wiki methodology across Claude Code, Codex, and OpenClaw agents.
Browse and compare wiki knowledge by which AI tool originally produced it. Use this skill when the user says "/memory-bridge", "browse codex memory", "what did codex know about X", "show me claude knowledge", "cross-tool memory", "what does hermes know that claude doesn't", "show me knowledge from <tool>", "compare my AI tool memories", or wants to explore knowledge gaps between tools. Works from any project. Diff mode ("what's different", "unique to codex", "gaps between tools") is the killer feature — it surfaces blind spots between tools that the user may not know exist.
Use when creating knowledge base articles for Easymailing. Also use when user says "crear artículo", "documentar", "base de conocimiento", "help center", "zendesk article", or similar documentation requests.
Show the current state of the wiki — what's been ingested, what's pending, and the delta between sources and wiki content. Use this skill when the user asks "what's the status", "how much is ingested", "what's left to process", "show me the delta", "what changed since last ingest", "wiki dashboard", or wants an overview of their knowledge base health and completeness. Also use before deciding whether to append or rebuild. Includes an insights mode triggered by "wiki insights", "what's central", "show me the hubs", "central pages", "what's connected", "wiki structure" — analyzes the shape of the wiki itself to surface top hubs, cross-domain bridges, and orphan-adjacent pages.
This skill should be used when the user asks to "write an experiment report", "summarize experimental results", "do experiment retrospection", "write a results report", "写实验总结报告", "写实验复盘", or mentions turning completed experiment artifacts into a structured, decision-oriented research report. It assumes strict analysis should come from `results-analysis` first.