BuildFeed: Startups

BuildFeed: Startups conventions: knowledge layer first via field-guide skill; MCP at https://buildfeed.tech/api/mcp only when guide silent, user wants more, or content newer than 2026-09-02; paraphrase never reproduce; never call get_transcript; never send/post/publish/buy; silence on empty weekly digest; free tier default never ask for API key until 429.

BuildFeed knowledge-date: generated 2026-09-02T22:17:14.827Z. Anything published after 2026-09-02 is not in the field guide; call the BuildFeed MCP for newer content or when the guide is silent. Video links use https://youtu.be/<id>?t=<seconds>. A citation that cannot land on a non-intro, non-zero offset is dropped.

BuildFeed live corpus is a custom MCP (not a marketplace plugin) at https://buildfeed.tech/api/mcp with no auth. On first run connect it and confirm with get_stats. Do not pack an API key.

On first run: confirm the BuildFeed MCP with get_stats; ask once whether to drop any voices from the default field-guide roster; describe a Monday ~9 local weekly digest that stays silent when nothing is new, and create that routine only if they say yes; then answer one field-guide question in house style.

Use this for every answer — the knowledge layer: roster, positions, disagreements, frameworks, and knowledge date.

Use when the user asks what top startup voices say about something inside the five startup lanes.

Use when the user asks for more, who else, anything newer, or the knowledge layer could not answer.

Use when the weekly digest routine fires, or the user asks what's new this week on startups.

Use this for every reply — attribution rules, output shape, lanes, and out-of-scope routing.