connector-readiness

name	connector-readiness
description	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.
user-invocable	true

Connector Readiness — Tool And Fallback Contract

Purpose

Make connector setup explicit and inspectable.

This skill does not assume connectors exist. It checks what is available, explains what each connector unlocks, records read/write boundaries, and gives a paste/export fallback when a live connector is missing.

Required Paths

Read:

• data/setup-status.md
• data/connectors.md
• knowledge-bases/company-context.md
• data/slack/channel-map.md if Slack is used
• data/teams/channel-map.md if Teams is used

Write:

• data/connectors.md
• views/connector-readiness.md
• data/setup-status.md
• append one line to data/ops.log

Use:

• templates/connector-status.md

Tool Requirements

Use live connector tools only when available and authorized by the environment.

Minimum stack:

• Email: read inbox/sent history for follow-ups and buyer threads; sending requires explicit approval.
• Calendar: read events for daily briefing and meeting prep; changes require explicit approval.
• Google Drive or equivalent docs: read selected folders; writes only to approved output/workspace folders.
• CRM: read accounts/opportunities/notes; record updates require explicit approval.
• Call recording/transcripts: read selected transcripts/summaries or synced transcript folder.
• Apollo: account discovery, firmographic filters, buyer personas, titles, email/contact export.
• Slack or Teams if used: selected channels/sources only; posting or meeting changes require explicit approval.
• Search/Tavily or equivalent: fresh cited account, market, trigger, hiring, press, and news research.

Fallbacks:

• Email threads can be pasted or exported.
• Calendar context can be listed manually.
• Drive docs can be dropped into knowledge-bases/ or exports/.
• CRM can be exported to CSV/Markdown.
• Call transcripts can be pasted or saved into the workspace.
• Apollo lists can be exported to CSV.
• Slack/Teams can use pasted threads, selected channel exports, or meeting recap notes.
• Search can use built-in web search or pasted source links.

Process

1. Identify what the founder uses.
2. Mark each connector as: connected / available but not configured / export-only / not used / unknown.
3. For each connector, record:
   • workflows improved
   • minimum read permission
   • write permissions that require approval
   • fallback path
   • next setup action
4. If Slack or Teams is used, route to /slack-setup or /teams-setup.
5. Update data/setup-status.md connector fields.
6. Write views/connector-readiness.md.
7. Append one line to data/ops.log.

Boundaries

• Do not claim a connector is connected unless it is actually available.
• Do not request broad access when selected/read-only access is enough.
• Do not send email, post messages, edit CRM, update calendar events, modify meetings, or write to external systems without explicit approval.
• Do not block the workflow when a connector is missing; record the fallback.