How do I install the Cofounder Tools skill?

Run npx skillmds@latest add vellum-ai/cofounder-tools in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cofounder Tools safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cofounder Tools?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cofounder Tools free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cofounder Tools?

vellum-ai (@vellum-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cofounder Tools by vellum-ai — Agent Skill

Name: Cofounder Tools
Author: vellum-ai

Cofounder Tools

Company-memory tools for the co-founder plugin: company profile, decision log, OKRs, blind-spot analysis, and briefings. Load when the user wants to log, review, or search a strategic decision, set or update OKRs, update company profile details, or asks "what did I decide about..." — any co-founder data operation outside a full onboarding, strategy session, or weekly review.

vellum-ai 3c6fad3 7 files · 23.8 KB Updated Sep 17, 2026

File contents

Co-Founder Tools

Data operations for the co-founder plugin. These tools read and write the company memory that the other co-founder skills (onboarding, strategy sessions, weekly reviews) build on — those skills include this one, so the tools are available whenever any of them is active. Load this skill directly for standalone data operations: logging a decision, updating OKR progress, or answering "what did I decide about X."

The data model

Company profile — name, stage, sector, description, team, funding, top challenges, current focus. One profile per workspace; update merges only the fields provided. The profile powers the automatic company-context injection at the start of every conversation.
Decisions — strategic choices with title, rationale, alternatives considered, tags, and a lifecycle status: proposed → decided → implemented (or reversed / abandoned). Review updates status and records the outcome.
OKRs — quarterly objectives, each with key results tracked by target, current value, and progress (0-100). KR status auto-derives from progress unless overridden.

Usage guidance

Log decisions with the rationale in the founder's words, not a paraphrase. Capture alternatives considered — that context is what makes the log useful months later.
When the user mentions a strategic choice that was clearly made ("we decided to...", "we're going with..."), offer to log it. Don't log without asking.
Answer "what did I decide about X" with cofounder_decision action search, then summarize the matches with dates and statuses.
Keep OKR progress updates lightweight: update_kr with the new current value and progress. Only override kr_status when the auto-derived status is misleading.
cofounder_blindspot and cofounder_briefing return structured data plus an instruction field — follow that instruction when formatting the response.

---name: cofounder-toolsdescription: Company-memory tools for the co-founder plugin: company profile, decision log, OKRs, blind-spot analysis, and briefings. Load when the user wants to log, review, or search a strategic decision, set or update OKRs, update company profile details, or asks "what did I decide about..." — any co-founder data operation outside a full onboarding, strategy session, or weekly review.---# Co-Founder ToolsData operations for the co-founder plugin. These tools read and write thecompany memory that the other co-founder skills (onboarding, strategysessions, weekly reviews) build on — those skills include this one, so thetools are available whenever any of them is active. Load this skill directlyfor standalone data operations: logging a decision, updating OKR progress, oranswering "what did I decide about X."## The data model- **Company profile** — name, stage, sector, description, team, funding, top challenges, current focus. One profile per workspace; `update` merges only the fields provided. The profile powers the automatic company-context injection at the start of every conversation.- **Decisions** — strategic choices with title, rationale, alternatives considered, tags, and a lifecycle status: proposed → decided → implemented (or reversed / abandoned). Review updates status and records the outcome.- **OKRs** — quarterly objectives, each with key results tracked by target, current value, and progress (0-100). KR status auto-derives from progress unless overridden.## Usage guidance- Log decisions with the rationale in the founder's words, not a paraphrase. Capture alternatives considered — that context is what makes the log useful months later.- When the user mentions a strategic choice that was clearly made ("we decided to...", "we're going with..."), offer to log it. Don't log without asking.- Answer "what did I decide about X" with `cofounder_decision` action `search`, then summarize the matches with dates and statuses.- Keep OKR progress updates lightweight: `update_kr` with the new current value and progress. Only override `kr_status` when the auto-derived status is misleading.- `cofounder_blindspot` and `cofounder_briefing` return structured data plus an `instruction` field — follow that instruction when formatting the response.

Frequently asked questions