AgentStack
SKILL verified MIT Self-run

Fundraising Thread Tracker

skill-igptai-skills-fundraising-thread-tracker · by igptai

Tracks every active investor conversation in a fundraising process — where each conversation stands, what was said, what the next step is, and which leads have gone cold. Use when a founder is in an active fundraise and wants to manage their pipeline from email. Triggers on "fundraising pipeline", "investor conversations", "fundraise tracker", "which investors are warm", "fundraising status", "wh…

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-igptai-skills-fundraising-thread-tracker

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Fundraising Thread Tracker? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Fundraising Thread Tracker

Prerequisites

This skill needs the iGPT MCP at https://mcp.igpt.ai/.

If the MCP tools aren't available or return an auth error, tell the user to install the iGPT plugin (/plugin marketplace add igptai/skills) or add https://mcp.igpt.ai/ as a connector, then complete OAuth and say "ready". Retry once after they confirm. Never invent tokens or OAuth URLs. For deeper troubleshooting: https://raw.githubusercontent.com/igptai/skills/main/shared/mcp-guard.md


What This Skill Does

Scans all investor outreach and fundraising email threads to produce a full pipeline view — where each investor conversation stands, what was last said, what the next step is, who has gone quiet, and which conversations are most likely to convert.


Workflow

  1. Before calling any tool, collect these values from the user. Offer the

defaults and let the user override them; do not invent values they did not give.

  • [time_range] — what window of email to scan. The user may give this

in any form ("last 6 months", "the last 90 days", "May 2024", "since the round opened"). Default: the last 6 months. Keep the user's natural phrasing for use in the ask input; convert to ISO dates separately for the search call.

  • [investor_scope] — either "all" (default) or the name of a specific

investor or fund to focus on.

  • [investorclause] — derived. When [investorscope] is not "all", set

to " for investor [investorscope]". When [investorscope] is "all", set to empty string.

  1. Call search with:
  • query: term sheet investment round deck meeting intro fund interest

due diligence commit lead follow (if [investor_scope] is not "all", append the investor name to the query)

  • datefrom: ISO start date derived from [timerange]
  • dateto: ISO end date derived from [timerange] (or today if open-ended)
  1. Call ask with:
  • input: Review all fundraising and investor outreach email threads from [timerange][investorclause]. For each investor or fund in the pipeline, determine: their current stage in the conversation, when contact was last made, what was last discussed, what the next step is and who owns it, their apparent level of interest based on email tone, and any signals suggesting they are moving toward a decision or pulling back.
  • output_format:

{ "strict": true, "schema": { "type": "object", "description": "Fundraising pipeline tracker across all active investor conversations", "additionalProperties": false, "properties": { "asof": { "type": "string", "description": "ISO8601 date when this pipeline was generated" }, "pipeline": { "type": "array", "description": "List of every investor in the current fundraising pipeline", "items": { "type": "object", "description": "A single investor conversation with current pipeline status", "additionalProperties": false, "properties": { "investorname": { "type": "string", "description": "Name of the investor or fund" }, "investortype": { "type": "string", "description": "Type of investor", "enum": [ "leadvc", "tier1vc", "tier2vc", "angel", "familyoffice", "strategic", "unknown" ] }, "stage": { "type": "string", "description": "Current stage of this investor conversation", "enum": [ "initialoutreach", "intromeetingscheduled", "intromeetingdone", "followupmeeting", "duediligence", "partnermeeting", "termsheetdiscussion", "termsheetreceived", "closing", "passed", "gonequiet", "unknown" ] }, "lastcontactdate": { "type": "string", "description": "ISO8601 date of the most recent email exchange" }, "dayssincecontact": { "type": "number", "description": "Number of days since the last email exchange" }, "interestlevel": { "type": "string", "description": "Apparent level of investment interest based on email signals", "enum": ["veryhigh", "high", "medium", "low", "unknown"] }, "lastexchangesummary": { "type": "string", "description": "Brief summary of what was discussed in the most recent email exchange" }, "nextstep": { "type": "string", "description": "The next action required to move this conversation forward" }, "nextstepowner": { "type": "string", "description": "Who owns the next step", "enum": ["us", "investor", "both", "unknown"] }, "keyconcernsraised": { "type": "array", "description": "Any concerns, objections, or questions this investor has raised", "items": { "type": "string", "description": "A single concern or question raised by this investor" } }, "conversionlikelihood": { "type": "string", "description": "Estimated likelihood of this investor converting to a check", "enum": ["high", "medium", "low", "unknown"] } }, "required": [ "investorname", "investortype", "stage", "lastcontactdate", "dayssincecontact", "interestlevel", "lastexchangesummary", "nextstep", "nextstepowner", "keyconcernsraised", "conversionlikelihood" ] } }, "activecount": { "type": "number", "description": "Number of investors in active conversation" }, "gonequietcount": { "type": "number", "description": "Number of investors who have gone quiet and need follow-up" }, "highconversioncount": { "type": "number", "description": "Number of investors with high conversion likelihood" }, "summary": { "type": "string", "description": "One or two sentence summary of the fundraising pipeline and most important next actions" } }, "required": [ "asof", "pipeline", "activecount", "gonequietcount", "highconversion_count", "summary" ] } }

  1. Present ordered by conversion likelihood then by stage proximity to close.

Lead with active count, high conversion count, and gone quiet count.

  1. Ask: "Would you like me to draft follow-up messages for any investors

who have gone quiet or where the next step is ours?"

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.