timeline-inject-v2

Inject gbrain-compatible Timeline sections into company and people pages.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/tapway/shogun-os --skill timeline-inject-v2-tapway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: timeline-inject-v2
Source: https://github.com/tapway/shogun-os/tree/main/skills/gbrain/timeline-inject-v2
Command: npx skills add https://github.com/tapway/shogun-os --skill timeline-inject-v2-tapway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Timeline entries in a gbrain knowledge base are silently skipped by the extractor unless they follow the exact format - **YYYY-MM-DD** | Source — Summary, leaving company and people pages without usable chronological data. ## Core Features & Use Cases - Format-compliant injection: Writes ## Timeline sections using the exact bold-date, pipe, and em-dash pattern that gbrain extract timeline parses. - Bulk campaign runs: Supports dry-run and --apply modes for processing hundreds of company and people pages at once. - Extraction integration: Pairs with gbrain extract timeline and gbrain extract all to persist entries into the gbrain database with deduplication. - Use Case: After collecting dated events from meetings and deals, run the injector across 383 pages to add timeline sections, then extract them into the gbrain DB. ## Quick Start Run the timeline injector script in dry-run mode against my brain repo, then apply the changes and run gbrain extract timeline to load the new entries.

Frequently Asked Questions about timeline-inject-v2

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

FAQPage Schema
How do I add timeline entries to gbrain pages?

Add a `## Timeline` section to the company or person page using the format `- **YYYY-MM-DD** | Source — Summary`, then run `gbrain extract timeline` from the brain repo. The injector script automates this across many pages with dry-run and apply modes.

What format does gbrain extract timeline require?

The extractor parses lines matching `- **YYYY-MM-DD** | Source — Summary` with bold dates, a pipe separator, and an em-dash before the summary. Plain `- YYYY-MM-DD | text` lines are silently skipped and never extracted.

Why is gbrain not extracting my timeline entries?

Extraction fails when dates are not bold, the pipe or em-dash separators are missing, or entries duplicate existing DB records. Extraction is also incremental, so unchanged files are skipped unless you force a full re-extract.

Can I use gbrain timeline-add together with Timeline sections?

You can, but both the CLI `timeline-add` command and `## Timeline` sections create database entries, and the extractor skips duplicates. Running both on the same page causes dedup conflicts, so pick one method per page.

Why did my timeline campaign extract so few entries?

Low yields are expected because the extractor deduplicates against existing DB entries and most stub pages lack date frontmatter. Timeline coverage compounds over time as meetings, deals, and emails get linked to pages.