Loading...
Loading...
Found 200 Skills
dontbesilent Content Structuring System. Build a sustainable, growing content structuring project from a large amount of local manuscripts, tweets, topic ideas, cases, and course scripts: first audit the scale and boundaries of the content, then create a new project, copy materials, extract content units, and generate topic maps and topic assembly drafts. Triggers: /dbs-content-system, /content-structuring-system, "turn my content into a structured system", "turn local materials into a reorganizable system", "help me build a content asset project", "I want to turn old content into reusable assets" Content structuring system. Audits local content volume, then builds a reusable content knowledge project with units, topic maps, and assembly drafts. Trigger: /dbs-content-system, "build a content structuring system", "turn my archive into reusable assets"
Structured prompts, vault templates, and autonomous research workflows for AI-assisted genealogy using Claude Code.
Create spatial node-based diagrams with free positioning. Best for mind maps, knowledge graphs, concept maps, and planning boards where precise spatial layout matters. Use JSON format with x/y coordinates. NOT for sequential flows (use mermaid) or data charts (use vega).
This skill should be used when the user asks to "set up agent todos", "initialize the todo store", "configure todos", "run todo init", "set up .agent-todos.local.json", or wants to set up or reconfigure the todo store for this project.
Generate a clean morning brief in Claude Code — pulls today's priorities, unposted content, and weather from your vault.
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.
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.
Run the daily wiki maintenance cycle: check all source freshness, update the index, and regenerate hot.md. Use this skill when the user says "/daily-update", "run the daily update", "update everything", "morning sync", "refresh the wiki index", or when triggered by the launchd cron at 9 AM. Also use to set up or verify the cron + terminal notification infrastructure for the first time ("set up the daily cron", "install the terminal notification", "how do I get the morning reminder?").
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.
Daily Review Assistant - An AI-assisted decision-making tool for cleaning up knowledge inboxes. The Agent provides "Keep/Delete" suggestions with reasons, and users manually execute after confirmation. Following the principle of "Collect without judging, make decisions during daily review", complete daily knowledge organization in 5-10 minutes. Triggers: /daily-review, /日清, /review
Annual strategic review and goal-setting interview for personal life/work domains with quarterly progress check-ins
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').