AgentStack
SKILL verified MIT Self-run

Partnership Pipeline Tracker

skill-igptai-skills-partnership-pipeline-tracker · by igptai

Tracks every active partnership conversation from email — where each discussion stands, what was agreed, what the next step is, and which conversations have stalled. Use when a marketing or BD team wants a full view of the partnership pipeline without manually reviewing every thread. Triggers on "partnership pipeline", "active partnership conversations", "partnership status", "where are partnersh…

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

Install

$ agentstack add skill-igptai-skills-partnership-pipeline-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 Partnership Pipeline Tracker? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Partnership Pipeline 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 partnership and business development email threads to produce a structured pipeline view — current stage of each conversation, last contact date, open commitments, next steps, and which discussions have gone quiet or stalled.


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 BD kicked off"). 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.

  • [partnership_scope] — either "all" (default) or a specific

partnership type or partner company to focus on.

  • [partnershipclause] — derived. When [partnershipscope] is not

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

  1. Call search with:
  • query: partnership collaboration co-marketing integration BD agreement

joint launch announcement deal (if [partnership_scope] is not "all", append the partnership type or partner 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 partnership and business development email threads from [timerange][partnershipclause]. For each active partnership conversation identify: the partner company, the type of partnership being discussed, the current stage of the conversation, when contact was last made, what was last agreed or discussed, the next step required, who owns that next step, and any open commitments from either side.
  • output_format:

{ "strict": true, "schema": { "type": "object", "description": "Partnership pipeline report across all active BD conversations", "additionalProperties": false, "properties": { "asof": { "type": "string", "description": "ISO8601 date when this report was generated" }, "partnerships": { "type": "array", "description": "List of every active partnership conversation in the pipeline", "items": { "type": "object", "description": "A single partnership conversation with current pipeline status", "additionalProperties": false, "properties": { "partner": { "type": "string", "description": "Name of the partner company or organization" }, "partnershiptype": { "type": "string", "description": "Category of partnership being discussed", "enum": [ "comarketing", "integration", "reseller", "referral", "jointventure", "content", "event", "technology", "other" ] }, "stage": { "type": "string", "description": "Current stage of this partnership conversation", "enum": [ "initialoutreach", "exploratorydiscussion", "alignmentmeeting", "proposalshared", "negotiatingterms", "agreementinprogress", "active", "stalled", "declined", "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" }, "lastexchangesummary": { "type": "string", "description": "Brief summary of what was discussed in the most recent exchange" }, "opencommitments": { "type": "array", "description": "Commitments from either side that have not been confirmed as complete", "items": { "type": "object", "description": "A single open commitment in this partnership", "additionalProperties": false, "properties": { "commitment": { "type": "string", "description": "Description of the commitment made" }, "ownedby": { "type": "string", "description": "Which side owns this commitment", "enum": ["us", "partner", "unknown"] } }, "required": ["commitment", "ownedby"] } }, "nextstep": { "type": "string", "description": "The next action required to move this partnership forward" }, "nextstepowner": { "type": "string", "description": "Who owns the next step", "enum": ["us", "partner", "both", "unknown"] }, "potentialvalue": { "type": "string", "description": "Assessment of the strategic value of this partnership if it progresses", "enum": ["high", "medium", "low", "unknown"] } }, "required": [ "partner", "partnershiptype", "stage", "lastcontactdate", "dayssincecontact", "lastexchangesummary", "opencommitments", "nextstep", "nextstepowner", "potentialvalue" ] } }, "stalledcount": { "type": "number", "description": "Number of partnership conversations that have stalled" }, "ournextstepcount": { "type": "number", "description": "Number of partnerships where the next step is ours to take" }, "summary": { "type": "string", "description": "One or two sentence summary of the partnership pipeline health and most urgent items" } }, "required": [ "asof", "partnerships", "stalledcount", "ournextstep_count", "summary" ] } }

  1. Present ordered by stage proximity to active, with stalled partnerships

flagged. Lead with ournextstep count and stalled count.

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

next-step-ours partnerships?"

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.