agentleFS
Sign inStart free
latour-ailatour-ai/skills/deal-pipeline-tracker-updater/SKILL.md

deal-pipeline-tracker-updater

Skill69 starsChanged 27 days agoNo licenceView on GitHub

Keep the deal pipeline tracker current from the communication exhaust instead of from someone remembering to update it — on a schedule, read the shared deal inbox and deal-team chat (or an exported batch of emails and messages), work out which messages concern which live opportunity, and propose the updates: stage changes, new intermediary contacts, moved bid dates and process deadlines, diligence items requested, and pass decisions, each cited to its source message, with a separate list of the changes it was not confident enough to apply and the pre-meeting delta of what moved, what has gone quiet, and what has no next step. For operations leads and deal teams at private equity and private credit firms whose pipeline meeting runs on a shared tracker. Trigger on phrases like "update the pipeline tracker," "what moved this week," "sync the tracker from the inbox," "pipeline delta before Tuesday," "which deals went quiet," "pull the bid dates out of the deal inbox," "reconcile the tracker against email," or when a user provides exported deal emails alongside a pipeline spreadsheet. Do NOT use for the LP fundraising pipeline. Do NOT use for screening brand-new inbound teasers or CIMs — use the cim-first-pass skill. Do NOT use for a personal inbox's action items — use the inbox-triage skill. Do NOT use for sourcing sweeps for add-on targets. The tracker is the system of record; this skill proposes changes to it and never overwrites a human entry without a citation.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free