research-intake

Parse inbox.md entries into frontmatter-backed research note stubs.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/marcmontecalvo/waywarden --skill research-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-intake
Source: https://github.com/marcmontecalvo/waywarden/tree/main/.waywarden/skills/research-intake
Command: npx skills add https://github.com/marcmontecalvo/waywarden --skill research-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn a line-item inbox of URLs, repo links, and article references into properly-formatted research note stubs that the research-note-router can process.

Core Features & Use Cases

  • Parse docs/research/inbox.md and extract every non-comment, non-blank line as an entry; preserve operator notes as seeds for the "Why it is interesting" section.
  • For each entry, fetch the URL, verify HTTP 200, skip thin sources, and extract title, primary topic, and source_type (repo / article / docs / video / paper).
  • Generate kebab-case filenames from the primary subject, check for duplicates, and write standardized frontmatter-backed notes to docs/research/.
  • Enforce a consistent template with sections: Why it is interesting, What appears strong, Relevance to WayWarden, Source summary.

Quick Start

Run the research-intake skill on docs/research/inbox.md to generate completed research notes.

Frequently Asked Questions about research-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically generate research notes from URLs and references in a markdown inbox?

You can automatically generate research notes from a markdown inbox by parsing each non-blank line, fetching the URL to verify HTTP 200, classifying the source type, and writing standardized frontmatter-backed notes to your research directory.

What is the best way to convert a list of repo links and articles into structured markdown notes?

Converting repo links and articles into structured markdown notes involves extracting titles and primary topics from fetched URLs, deriving kebab-case filenames, and populating a consistent template with sections like source summary and relevance.

How does inbox parsing handle duplicate sources and thin content?

Inbox parsing handles duplicates by checking existing kebab-case filenames before writing, and it skips thin sources by verifying HTTP 200 responses and extracting meaningful titles and primary topics during the fetch process.

Can I classify sources like videos, papers, and docs automatically when creating research note stubs?

Yes, you can classify sources automatically when creating research note stubs by fetching each URL and categorizing it as repo, article, docs, video, or paper to produce consistent frontmatter metadata.

Do I need network access to parse an inbox file and generate research notes?

Yes, you need network access to parse an inbox file and generate research notes because the process requires fetching URLs to validate HTTP 200 responses and extract titles, topics, and source types for each entry.

What sections are included in the standardized template for generated research notes?

The standardized template for generated research notes includes sections for why it is interesting, what appears strong, relevance to the project, and a source summary, using operator notes from the inbox as initial seeds.