メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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 when the user asks to research a company or person. Provides: company snapshot, person snapshot, likely pressures, point of view for the company, point of view for the person, talk track angles, and questions to ask. Output contract: the result is directly usable for prep, outreach, or the next meeting.
| name | profile |
| description | 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. |
| user-invocable | false |
Holds the starter identity and setup-tracking logic for SalesSidekick Lite.
The canonical local tracker is data/setup-status.md.
The global settings block should be written from templates/global-identity.md.
The local company context should be written to knowledge-bases/company-context.md using templates/company-context.md.
Connector status should be written to data/connectors.md using templates/connector-status.md.
Read:
data/setup-status.mdtemplates/company-context.mdtemplates/global-identity.mdtemplates/setup-status.mdtemplates/connector-status.mddata/connectors.md if presentWrite:
data/setup-status.mdknowledge-bases/company-context.mddata/connectors.md when connector setup runsdata/ops.log/connectors; do not claim live tools are connected unless available./slack-setup or /teams-setup when used.If global write is not available automatically:
global_identity_copy_ready: true in data/setup-status.mddata/setup-status.mdDuring setup, explain that the founder installed:
The daily briefing should use this skill to:
Setup is not complete until these fields are captured or explicitly marked unknown: