
Idea Ingest
- 237 installs
- 27.8k repo stars
- Updated August 5, 2026
- garrytan/gbrain
Capture raw ideas, links, and notes into gbrain so agents can index, tag, and recall them during later research and planning sessions.
About
The idea-ingest skill for garrytan/gbrain normalizes and stores incoming ideas, snippets, and references into the personal knowledge graph so Claude Code agents can search, relate, and reuse them during ideation and planning.
- Structured idea capture for gbrain
- Feeds downstream agent recall
- Low-friction knowledge intake
- Supports early brainstorming loops
- Pairs with research workflows
Idea Ingest by the numbers
- 237 all-time installs (skills.sh)
- Ranked #2,617 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/garrytan/gbrain --skill idea-ingestAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 237 |
|---|---|
| repo stars | ★ 27.8k |
| Last updated | August 5, 2026 |
| Repository | garrytan/gbrain ↗ |
What it does
Capture raw ideas, links, and notes into gbrain so agents can index, tag, and recall them during later research and planning sessions.
Files
Idea Ingest Skill
Filing rule: Read skills/_brain-filing-rules.md before creating any new page.Contract
This skill guarantees:
- Every ingested item has a brain page with genuine analysis (not just a summary)
- The author gets a people page (MANDATORY for anyone whose thinking is worth ingesting)
- Cross-links created bidirectionally (source ↔ author, source ↔ mentioned entities)
- Raw source preserved for provenance via
gbrain files upload-raw - Every fact has an inline
[Source: ...]citation - Filing follows primary subject rules (not format-based)
Convention: See skills/conventions/quality.md for Iron Law back-linking.Every mention of a person or company with a brain page MUST create a back-link. Format: - **YYYY-MM-DD** | Referenced in [page title](path) — brief context
Phases
1. Fetch the content. Use appropriate tools for the content type (web fetch for articles, API for tweets, PDF reader for documents).
2. Upload raw source. Save the fetched content for provenance: gbrain files upload-raw <file> --page <slug>
3. Identify the author — MANDATORY people page. Anyone whose thinking is worth ingesting is worth tracking.
- Search brain for existing author page
- If no page → CREATE ONE with compiled truth + timeline format
- If page exists → update timeline with this new publication
- Cross-link both directions
4. Save to brain. File by PRIMARY SUBJECT (read skills/_brain-filing-rules.md):
- About a person →
people/ - About a company →
companies/ - A reusable framework →
concepts/ - Raw data dump →
sources/
5. Analyze for the user. Reply with analysis that connects the content to what the brain knows. Think about:
- Active projects — is this relevant?
- Contradictions — does this challenge existing brain knowledge?
- Connections — does this involve known people/companies?
- Don't just summarize. Tell the user things they wouldn't have noticed.
6. Sync. gbrain sync to update the index.
Output Format
# {Title} — {Author}
**Source:** {URL}
**Author:** {Author}, {role}
**Published:** {date}
**Ingested:** {date}
## Context
{Why this matters now, connected to brain knowledge}
## Summary
{3-5 bullet core arguments}
## Key Data / Claims
{Specific facts, numbers, quotes}
## Analysis
{How this connects to existing brain knowledge. What's new. What contradicts.}Anti-Patterns
- Just summarizing without connecting to brain knowledge
- Filing everything in
sources/(sources is for raw data dumps only) - Skipping the author people page
- Not cross-linking to mentioned entities
- Ingesting without checking brain first for existing coverage