Domain knowledge for creating and managing the Founder OS HQ Notion workspace.
From founder-osnpx claudepluginhub thecloudtips/founder-os --plugin founder-osThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Domain knowledge for creating and managing the Founder OS HQ Notion workspace.
The Founder OS HQ consists of 22 databases organized into 5 sections. CRM Companies is the central hub — all client-facing databases relate back to it.
| Section | Databases | Template Files |
|---|---|---|
| CRM | Companies, Contacts, Deals, Communications | hq-companies.json, hq-contacts.json, hq-deals.json, crm-sync-hub-communications.json |
| Operations | Tasks, Meetings, Finance | hq-tasks.json, hq-meetings.json, hq-finance.json |
| Intelligence | Briefings, Knowledge Base, Research, Reports | hq-briefings.json, hq-knowledge-base.json, hq-research.json, hq-reports.json |
| Content & Deliverables | Content, Deliverables, Prompts | hq-content.json, hq-deliverables.json, team-prompt-library-prompts.json |
| Growth & Meta | Goals, Milestones, Learnings, Weekly Insights, Workflows, Activity Log, Memory, Intelligence | goal-progress-tracker-goals.json, goal-progress-tracker-milestones.json, learning-log-tracker-learnings.json, learning-log-tracker-weekly-insights.json, hq-workflows.json, google-drive-brain-activity.json, hq-memory.json, hq-intelligence.json |
All databases created by this skill use the [FOS] prefix:
[FOS] Companies[FOS] Tasks[FOS] BriefingsThis prefix is used for discovery by all 32 plugins. The 3-step discovery pattern in plugins searches for:
[FOS] <Name> (primary — created by this skill)Founder OS HQ - <Name> (legacy consolidated name)Inbox Zero - Action Items)Databases must be created in dependency order because relations reference other databases:
Several databases merge data from multiple plugins. The Type column distinguishes records:
| Database | Type Values |
|---|---|
| Tasks | Email Task, Action Item, Follow-Up |
| Meetings | (no type — shared Event ID distinguishes Prep vs Analysis) |
| Finance | Invoice, Expense |
| Briefings | Daily Briefing, Weekly Review, Slack Digest, Morning Sync |
| Knowledge Base | Source, Query |
| Research | Newsletter Research, Competitive Analysis |
| Reports | Business Report, Expense Report, ROI Report |
| Content | Email Draft, Newsletter, LinkedIn Post |
| Deliverables | Proposal, Contract, SOW |
| Workflows | Execution, SOP |
Each template JSON in _infrastructure/notion-db-templates/ follows this structure:
{
"name": "Display Name",
"description": "Purpose of this database",
"properties": {
"Name": { "title": {} },
"Status": {
"select": {
"options": [
{ "name": "To Do", "color": "gray" },
{ "name": "In Progress", "color": "blue" },
{ "name": "Done", "color": "green" }
]
}
},
"Company": {
"relation": {
"database_id": "{{companies_db_id}}",
"single_property": {}
}
}
}
}
The {{companies_db_id}} placeholder is replaced at runtime with the actual database ID after creation.
[FOS] <display_name>.The source of truth for database names, template filenames, and creation order is:
_infrastructure/notion-db-templates/founder-os-hq-manifest.json
Always read this file at runtime rather than hardcoding the database list.