跳到正文
FunCoding

搜索

搜索文档、Skill 和 MCP

second-brain-ingest

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 knowledge base.

文档与办公736skills/second-brain-ingest/SKILL.md

安装

把这段话发给 Claude Code、Codex 或 Cursor。智能体会先检查安全性,你确认后才安装。

读取 https://funcoding.ai/skills/nicholasspisak/second-brain/second-brain-ingest/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Second Brain — Ingest

Process raw source documents into structured, interlinked wiki pages.

Identify Sources to Process

Determine which files need ingestion:

  1. If the user specifies a file or files, use those
  2. If the user says "process new sources" or similar, detect unprocessed files:
    • List all files in raw/ (excluding raw/assets/)
    • Read wiki/log.md and extract all previously ingested source filenames from ingest entries
    • Any file in raw/ not listed in the log is unprocessed
  3. If no unprocessed files are found, tell the user

Process Each Source

For each source file, follow this workflow:

1. Read the source completely

Read the entire file. If the file contains image references, note them — read the images separately if they contain important information.

2. Discuss key takeaways with the user

Before writing anything, share the 3-5 most important takeaways from the source. Ask the user if they want to emphasize any particular aspects or skip any topics. Wait for confirmation before proceeding.

3. Create source summary page

Create a new file in wiki/sources/ named after the source (slugified). Include:

---
tags: [relevant, tags]
sources: [original-filename.md]
created: YYYY-MM-DD
updated: YYYY-MM-DD
---

# Source Title

**Source:** original-filename.md
**Date ingested:** YYYY-MM-DD
**Type:** article | paper | transcript | notes | etc.

## Summary

Structured summary of the source content.

## Key Claims

- Claim 1
- Claim 2
- ...

## Entities Mentioned

- [[Entity Name]] — brief context
- ...

## Concepts Covered

- [[Concept Name]] — brief context
- ...

4. Update entity and concept pages

For each entity (person, organization, product, tool) and concept (idea, framework, theory, pattern) mentioned in the source:

If a wiki page already exists:

  • Read the existing page
  • Add new information from this source
  • Add the source to the sources: frontmatter list
  • Update the updated: date
  • Note any contradictions with existing content, citing both sources

If no wiki page exists:

  • Create a new page in the appropriate subdirectory:
    • wiki/entities/ for people, organizations, products, tools
    • wiki/concepts/ for ideas, frameworks, theories, patterns
  • Include YAML frontmatter with tags, sources, created, and updated fields
  • Write a focused summary based on what this source says about the topic

Ensure all related pages link to each other using [[wikilink]] syntax. Every mention of an entity or concept that has its own page should be linked.

6. Update wiki/index.md

For each new page created, add an entry under the appropriate category header:

- [[Page Name]] — one-line summary (under 120 characters)

7. Update wiki/log.md

Append:

## [YYYY-MM-DD] ingest | Source Title
Processed source-filename.md. Created N new pages, updated M existing pages.
New entities: [[Entity1]], [[Entity2]]. New concepts: [[Concept1]].

8. Report results

Tell the user what was done:

  • Pages created (with links)
  • Pages updated (with what changed)
  • New entities and concepts identified
  • Any contradictions found with existing content

Conventions

  • Source summary pages are factual only. Save interpretation and synthesis for concept and synthesis pages.
  • A single source typically touches 10-15 wiki pages. This is normal and expected.
  • When new information contradicts existing wiki content, update the wiki page and note the contradiction with both sources cited.
  • Prefer updating existing pages over creating new ones. Only create a new page when the topic is distinct enough to warrant its own page.
  • Use [[wikilinks]] for all internal references. Never use raw file paths.

What's Next

After ingesting sources, the user can:

  • Ask questions with /second-brain-query to explore what was ingested
  • Ingest more sources — clip another article and run /second-brain-ingest again
  • Health-check with /second-brain-lint after every 10 ingests to catch gaps

相似的 Skill

pdf
anthropics/skills180k

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

文档与办公

discernment-nudge
anthropics/skills180k

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

文档与办公

doc-coauthoring
anthropics/skills180k

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

文档与办公

docx
anthropics/skills180k

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

文档与办公

pptx
anthropics/skills180k

pptx

Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

文档与办公

canvas-design
anthropics/skills180k

canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

文档与办公