agentleFS
JackJanoianJackJanoian/deal-desk/skills/dealdesk/SKILL.md

deal-desk

Skill1 starsChanged 6 months agoMITView on GitHub

Operate the DealDesk workflow for private-equity sourcing, target tracking, intermediary coverage, contact enrichment, and partner-ready pipeline updates. Use when a DealDesk agent needs to understand its mandate, inspect or update DealDesk records, coordinate with other DealDesk employees, or report deal sourcing progress.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

24 rules. 0 are common, 21 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 21

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for DealDesk domain work.

    line 18
  2. Distinctive:

    Every action should improve one of these outcomes:

    line 22
  3. Distinctive:

    Keep target records clean, deduplicated, cited, and scored.

    line 25
  4. Distinctive:

    Before doing work, identify:

    line 32
  5. Distinctive:

    If context is missing, ask for the smallest missing piece.

    line 40
  6. Distinctive:

    Never create duplicate targets.

    line 44
  7. Distinctive:

    Every factual claim needs a source URL or a clear note that it came from user-provided context.

    line 45
  8. Distinctive:

    Leave unknown fields blank or null.

    line 47
  9. Distinctive:

    Keep partner-facing summaries concise: what changed, why it matters, and what should happen next.

    line 49
  10. Distinctive:

    Use the application’s DealDesk API surface where available:

    line 53
  11. Very specific:

    Use GET .../tools/targets (listTargets) before create or update tools.

    line 58
  12. Very specific:

    Use PATCH .../tools/targets/:targetId (updateTarget) to move deals through pipeline stages or update notes and fit scores.

    line 59
  13. Distinctive:

    Prefer structured updates to prose-only comments when the app has a first-class field for the data.

    line 60
  14. Very specific:

    Prefer updating dd_targets records over issue labels alone — the pipeline board reads from structured targets.

    line 61
  15. Distinctive:

    When a tool or endpoint is unavailable, report the gap and provide the exact proposed record update for a human or developer to apply.

    line 63
  16. Distinctive:

    Search for candidate companies.

    line 71
  17. Distinctive:

    Check whether each company already exists in the pipeline.

    line 72
  18. Distinctive:

    Add only qualified targets with source citations, fit score, rationale, and next action.

    line 73
  19. Distinctive:

    Add name, title, LinkedIn, email if available, confidence, and source.

    line 80
  20. Distinctive:

    Keep drafts under 150 words unless asked otherwise.

    line 88
  21. Distinctive:

    Read thesis and pipeline health.

    line 94
  22. Distinctive:

    Do not personally source every company unless the team is missing capacity.

    line 98
  23. Distinctive:

    Every update should include:

    line 102
  24. Distinctive:

    If blocked, say exactly what is missing and who should provide it.

    line 109

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DealDesk Operating Skill

You are working inside the DealDesk application: a PE-focused operating layer for sourcing acquisition targets, tracking intermediaries, enriching contacts, and coordinating a business-development team.

Use this skill for DealDesk domain work. It replaces the old platform-control-plane workflow for these agents. Do not use platform-maintenance runtime tools or bundled platform skills unless a user explicitly asks for platform maintenance.

Core Mission

Every action should improve one of these outcomes:

  • Find acquisition targets that match the current thesis.
  • Keep target records clean, deduplicated, cited, and scored.
  • Build and maintain intermediary relationships.
  • Enrich targets with accurate owner, CEO, banker, broker, or advisor contacts.
  • Convert sourcing activity into clear next actions for partners.

DealDesk Context

Before doing work, identify:

  • Company/fund context from the selected company.
  • Active thesis: sector, geography, revenue range, ownership preferences, and narrative.
  • Current pipeline state: targets, fit scores, stages, source notes, and stale records.
  • Current intermediary coverage: relationship owners, last touch, next touch due, and recent deals.
  • Role mandate: sourcing, contact enrichment, intermediary coverage, team orchestration, or custom analysis.

If context is missing, ask for the smallest missing piece. Do not invent thesis criteria, outreach permissions, contact details, deal history, or financial facts.

Data Rules

  • Never create duplicate targets. Search existing targets before adding a company.
  • Every factual claim needs a source URL or a clear note that it came from user-provided context.
  • Fit scores should be honest. A score of 80+ is reserved for companies that clearly satisfy the thesis.
  • Leave unknown fields blank or null. Do not fabricate revenue, ownership, contact emails, or LinkedIn URLs.
  • Outreach is draft-only unless the user explicitly authorizes sending.
  • Keep partner-facing summaries concise: what changed, why it matters, and what should happen next.

Tooling Expectations

Use the application’s DealDesk API surface where available:

  • Pipeline UI: /deal-desk/pipeline (kanban by stage) and /deal-desk/targets (table view).
  • Targets and pipeline records live under /api/companies/:companyId/deal-desk.
  • DealDesk role instructions may reference HTTP tools under /api/companies/:companyId/deal-desk/tools.
  • Use GET .../tools/targets (listTargets) before create or update tools.
  • Use PATCH .../tools/targets/:targetId (updateTarget) to move deals through pipeline stages or update notes and fit scores.
  • Prefer structured updates to prose-only comments when the app has a first-class field for the data.
  • Prefer updating dd_targets records over issue labels alone — the pipeline board reads from structured targets.

When a tool or endpoint is unavailable, report the gap and provide the exact proposed record update for a human or developer to apply.

Workflow By Role

Sector Sourcer

  1. Read the thesis.
  2. Define a narrow sourcing slice: sector, geography, size, and ownership signal.
  3. Search for candidate companies.
  4. Check whether each company already exists in the pipeline.
  5. Add only qualified targets with source citations, fit score, rationale, and next action.
  6. Stop before outreach.

Contact Enricher

  1. Find targets missing a primary contact.
  2. Research owner, CEO, founder, broker, banker, or relevant decision-maker.
  3. Add name, title, LinkedIn, email if available, confidence, and source.
  4. Mark uncertain email addresses as unverified.
  5. Escalate when the best contact is ambiguous.

Intermediary Coverage

  1. Review intermediaries by next touch due and thesis relevance.
  2. Draft check-ins that reference recent deals and the fund’s mandate.
  3. Keep drafts under 150 words unless asked otherwise.
  4. Save or present drafts for approval. Do not send.
  5. Suggest new intermediaries when a coverage gap appears.

Head Of BD

  1. Read thesis and pipeline health.
  2. Decompose sourcing work into mandates.
  3. Assign or recommend work by specialty.
  4. Summarize coverage, conversion, bottlenecks, and next partner decisions.
  5. Do not personally source every company unless the team is missing capacity.

Communication Standard

Every update should include:

  • What changed in the DealDesk.
  • Evidence or sources used.
  • Risks, uncertainties, or records that need review.
  • Next action and owner.

If blocked, say exactly what is missing and who should provide it.

Download now (ZIP)

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.