Update to StartupSprints

{
  "description": "Use when a StartupSprints founder asks to prepare targeted outreach, relevant follow-up, introductions, editor or podcast pitches, community research, answers to discussion threads, or participation in a specific community.",
  "included_files": [
    {
      "relative_path": "references/mcp-workflow.md",
      "size_in_bytes": 10072
    },
    {
      "relative_path": "references/outreach-preparation.md",
      "size_in_bytes": 4485
    },
    {
      "relative_path": "references/prompt-examples.md",
      "size_in_bytes": 1867
    }
  ],
  "name": "startupsprints-outreach-and-communities",
  "skill_md_contents": "---\r\nname: startupsprints-outreach-and-communities\r\ndescription: Use when a StartupSprints founder asks to prepare targeted outreach, relevant follow-up, introductions, editor or podcast pitches, community research, answers to discussion threads, or participation in a specific community.\r\n---\r\n\r\n# StartupSprints outreach and communities\r\n\r\nPrepare useful, relevant contact and community contributions within the founder's mission and approved limits. Willingness to consider outreach is separate from permission to send it.\r\n\r\nRead [MCP workflow](references/mcp-workflow.md) before work. Follow [outreach preparation](references/outreach-preparation.md) for recipient/thread qualification and output; [prompt examples](references/prompt-examples.md) provide entry points.\r\n\r\n## Inputs\r\n\r\nResolve the startup/action, confirmed audience and offer, founder identity/outreach preferences, current channel rules, existing contacts/work, time/budget and approved contact/follow-up limits. Ask only for facts required by the next step.\r\n\r\n## Read → select → act → save → review\r\n\r\n1. **Read:** Use `list_startups`, `get_startup_profile`, and `list_actions` to resolve the returned `actionId`; read `get_execution_brief` and `get_action_workspace`, plus relevant `get_distribution_kit`/`get_results`. Pass explicit `startupId` with all-startup grants.\r\n2. **Select:** Choose recipients or threads using observed audience/problem relevance and a permitted route. Check current venue rules, affiliation disclosure and promotion limits. Respect opt-outs, no-cold-contact choices and “existing communities only.” Inspect only enough authenticated context to identify the account and obtain missing confirmation for that service; reuse the existing explicit identity confirmation while the account/scope is unchanged.\r\n3. **Act:** Draft actual individual messages or complete useful thread replies. Ground personalization in observed facts; disclose the relationship and make one easy next step. Do not claim a prior relationship or pad a shortlist. Before any send/post/invitation, prepare the account, named destinations/recipients, exact content, costs and volume/follow-up limit. Execute only an existing explicit bounded authorization or obtain the missing one. Account confirmation alone does not authorize sending. Stop on declines, access denial or platform restrictions; do not compensate for non-response with more volume.\r\n4. **Save:** When the task includes saving, merge existing entries and complete notes according to the live `outreach`, `content`, `shortlist` or other template. Use current `workRevision`, reread/merge conflicts, and verify. Keep draft content separate from actual send receipts, responses and links. Preserve legacy findings. A save does not publish or end the action.\r\n5. **Review:** Report qualified recipients, drafted/sent messages and actual responses separately. Compare observed signal, effort and window with the strategy's stop condition and mission. Ambiguous “wrap up” produces a summary and necessary clarification before an attempt-ending call. `record_action_result` requires explicit actual-result instruction and completed/failed intent, current `attemptNumber` and `outcomeRevision`, and accurate `measuredMetrics`; unknown is not zero. Use `record_action_feedback` only for an explicit founder vote.\r\n\r\n## Output and fallback\r\n\r\nReturn qualified destinations with evidence/rules, exact drafts, approval scope still needed, actual execution evidence, save status and one next step. Missing browser/email capabilities: use another permitted integration, public research, or manual-ready messages with a response log. Missing MCP write access: keep the deliverable available without claiming persistence or broadening consent.\r\n"
}