菜单
Use when the founder needs a reusable business artifact from saved workspace context, especially investor/stakeholder updates or competitive snapshots. Combines recent context, tasks, research, closeouts, weekly plans, metrics supplied by the user, and competitor inputs into paste-ready drafts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | artifacts |
| description | Use when the founder needs a reusable business artifact from saved workspace context, especially investor/stakeholder updates or competitive snapshots. Combines recent context, tasks, research, closeouts, weekly plans, metrics supplied by the user, and competitor inputs into paste-ready drafts. |
| user-invocable | true |
Turn the workspace into concrete founder outputs. This is the eighth operating workflow in Founders OS.
Artifacts are not hidden intelligence. They are visible drafts the founder can inspect, edit, and send.
Use when the user asks for:
Read:
knowledge-bases/company-context.mddata/setup-status.mdviews/weekly-plan.mdviews/daily-briefing.mddata/tasks.mddata/research/data/closeouts/Output:
Save to:
exports/investor-update-{date}.mdDo not invent metrics, investor names, runway, revenue, customer names, or commitments.
Use when the user asks for:
Read:
knowledge-bases/company-context.mdOutput:
Save to:
data/research/competitive-snapshot-{date}.mdDo not create full battlecards, win-probability models, landmine libraries, or displacement playbooks in this starter version.
After saving an artifact:
data/ops.logdata/setup-status.md workflow usage if the workflow tracker existsFILES UPDATED blockUse when the founder needs a reusable business artifact from saved workspace context, especially investor/stakeholder updates or competitive snapshots. Combines recent context, tasks, research, closeouts, weekly plans, metrics supplied by the user, and competitor inputs into paste-ready drafts.
Fires when the user pastes a transcript or says they just finished a meeting. Provides: summary, what matters now, risks or blockers, tasks, and follow-up email. Output contract: every closeout leaves the user with a saved record and clear next actions.
Use when the founder needs to identify, connect, verify, or document email, calendar, Drive, CRM, call recording, Apollo, Slack, Teams, search/Tavily, or other operating connectors for SalesSidekick Lite.
Fires when the user wants to get ready for a meeting. Provides: account context, person point of view, talk track angles, questions to ask, watch-outs, and desired next step. Output contract: the user walks into the meeting with a clear point of view and practical talking points.
Use when the user wants to build an outbound SDR campaign, create a target account list, research a market from ICP, find buyers, build account/persona POVs, or draft a 3-5 step outbound sequence. Runs a staged campaign workflow: ICP/value prop/offer intake, 3x long-list, preliminary scan, top-50% deep account research, final prioritized list, top-20 company POVs, buyer persona research, persona POVs, offer mapping, then message sequence.
Fires during setup and daily briefing. Provides: seller identity, company/product context, competitor context, communication style, daily briefing preference, and setup-state logic. Output contract: the system always knows what has been captured and what is still missing.