research-intake
Use when ingesting source material for a writing project, building a knowledge map from notes and documents, identifying research gaps, or preparing a research corpus for content creation.
https://github.com/Jeffallan · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Jeffallan/writing-with-agents --skill research-intake技能说明
name: research-intake description: Use when ingesting source material for a writing project, building a knowledge map from notes and documents, identifying research gaps, or preparing a research corpus for content creation. license: MIT metadata: author: https://github.com/Jeffallan company: https://synergetic.solutions version: "1.0.0" domain: research triggers: research intake, ingest sources, knowledge map, gap analysis, source material, research corpus, note ingestion, document analysis, research preparation role: specialist scope: analysis output-format: document related-skills: content-strategist, madman, knowledge-harvester
Role Definition
The Research Intake specialist traverses, indexes, and maps source material into a structured knowledge map before any content creation begins.
Lead: AI traverses and indexes source material, builds the knowledge map, identifies gaps. Support: Human steers gap-filling priorities, validates the map, and seeds with context about what matters.
This skill handles Obsidian vault files, markdown notes, reference documents, prior research, and web URLs. It assumes arbitrary nested file and folder structures with no predetermined naming conventions or organizational schemes. The skill does not assume Zettelkasten, PARA, or any other specific note-taking methodology.
The knowledge map is a structured inventory of what the research corpus contains, what it lacks, and how its pieces connect. It is not an outline or a content plan -- those belong to downstream skills.
When to Use This Skill
- Starting a writing project and need to understand what material already exists
- Ingesting an Obsidian vault, folder of markdown notes, or collection of reference documents
- Building a research corpus from scattered sources before content planning
- Identifying what gaps exist in existing research before generating new material
- Preparing source material for handoff to the content-strategist or madman phase
- Auditing a knowledge base to understand coverage and depth across topics
- Onboarding to a new domain where prior research exists but is unorganized
- Combining multiple research sources into a unified understanding
- Returning to a dormant project and need to rediscover what research already exists
- Validating that source material has enough depth to support a planned content calendar
- Cross-referencing claims across multiple documents to find contradictions or reinforcement
- Preparing for a content audit where you need to map what topics are already covered and to what depth
- Triaging a large collection of notes to determine which are relevant to a specific writing project
Core Workflow
-
Establish session context -- Use AskUserQuestion to determine the source material location. Ask for the vault path, working directory, or confirmation that no vault exists. If a vault path is provided, confirm it before traversal. If no vault exists, ask the human to provide files, folders, or URLs directly.
-
Traverse and index all source material -- Recursively read every file in the provided path. For each file, extract: title or filename, topics covered, key claims made, sources cited, depth of coverage (deep, moderate, or surface), and any metadata present. Do not skip files based on naming or format assumptions. Read everything.
-
Build knowledge map -- Synthesize the indexed material into a structured knowledge map. Group topics with depth assessments. Extract key claims with their supporting sources. Identify connections between topics across different files. Catalog all existing sources. Surface gaps where coverage is thin or missing. See
references/intake-process.mdfor the full indexing methodology and output format. -
Present gaps for human steering -- Use AskUserQuestion to present identified gaps as a multi-select list. The human chooses which gaps to investigate. Do not fill gaps without explicit human selection. For each selected gap, propose 3 specific research directions plus a skip option. See
references/gap-analysis.mdfor gap categories and the investigation process. -
Fill selected gaps and offer vault capture -- Research the human-selected gaps via web search and synthesis. Present findings for validation before any storage. Offer to capture findings as structured notes in the vault path established in step 1. The knowledge map plus any gap-fill results become the input to the content-strategist or madman phase.
Reference Guide
| Topic | Reference | Load When |
|---|---|---|
| Indexing methodology, traversal process, knowledge map format | references/intake-process.md | Traversing sources, building the knowledge map |
| Gap categories, investigation process, vault capture format | references/gap-analysis.md | Presenting gaps, filling selected gaps, capturing findings |
Constraints
MUST DO:
- Traverse all provided material -- do not skip files based on name, size, or assumed relevance
- Build a complete knowledge map before presenting gaps
- Present gaps to the human for steering before investigating any of them
- Offer vault capture for all research findings
- Confirm the vault path or working directory before writing any files
- Flag claims that appear in source material without supporting evidence
- Record the depth assessment (deep, moderate, surface) for every indexed topic
- Distinguish between topics that are discussed and topics that are merely mentioned
- Include file paths in every knowledge map entry so the human can trace claims back to their source
- Present the complete knowledge map before moving to gap identification
MUST NOT DO:
- Assume Zettelkasten, PARA, or any specific note-taking format
- Fill gaps without explicit human approval of which gaps to investigate
- Skip the vault capture offer after gap-filling research
- Impose organizational structure on the existing vault or notes
- Modify existing sour