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
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- Hassaan146/claude-skillstheir own version, first seen Jul 25, 2026
- mahiunfiltered/claude-code-skillstheir own version, first seen Jul 8, 2026
- Hussain-Elfalah/Agentic-Skillstheir own version, first seen Jun 4, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- Hassaan146/claude-skills★ 18same name
- Hussain-Elfalah/Agentic-Skills★ 2same name
- mahiunfiltered/claude-code-skills★ 1same name
- vijaysuperpositionist/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- design-guideSkill
- deal-desk-converting-plans-to-tasksSkill
- deal-desk-create-agentSkill
- deal-desk-create-pluginSkill
- deal-desk-devSkill
- deal-desk-outreachSkill
- diagnose-why-work-stoppedSkill
- para-memory-filesSkill
- terminal-bench-loopSkill
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
- Distinctive: line 18
Use this skill for DealDesk domain work.
- Distinctive: line 22
Every action should improve one of these outcomes:
- Distinctive: line 25
Keep target records clean, deduplicated, cited, and scored.
- Distinctive: line 32
Before doing work, identify:
- Distinctive: line 40
If context is missing, ask for the smallest missing piece.
- Distinctive: line 44
Never create duplicate targets.
- Distinctive: line 45
Every factual claim needs a source URL or a clear note that it came from user-provided context.
- Distinctive: line 47
Leave unknown fields blank or null.
- Distinctive: line 49
Keep partner-facing summaries concise: what changed, why it matters, and what should happen next.
- Distinctive: line 53
Use the application’s DealDesk API surface where available:
- Very specific: line 58
Use GET .../tools/targets (listTargets) before create or update tools.
- Very specific: line 59
Use PATCH .../tools/targets/:targetId (updateTarget) to move deals through pipeline stages or update notes and fit scores.
- Distinctive: line 60
Prefer structured updates to prose-only comments when the app has a first-class field for the data.
- Very specific: line 61
Prefer updating dd_targets records over issue labels alone — the pipeline board reads from structured targets.
- Distinctive: line 63
When a tool or endpoint is unavailable, report the gap and provide the exact proposed record update for a human or developer to apply.
- Distinctive: line 71
Search for candidate companies.
- Distinctive: line 72
Check whether each company already exists in the pipeline.
- Distinctive: line 73
Add only qualified targets with source citations, fit score, rationale, and next action.
- Distinctive: line 80
Add name, title, LinkedIn, email if available, confidence, and source.
- Distinctive: line 88
Keep drafts under 150 words unless asked otherwise.
- Distinctive: line 94
Read thesis and pipeline health.
- Distinctive: line 98
Do not personally source every company unless the team is missing capacity.
- Distinctive: line 102
Every update should include:
- Distinctive: line 109
If blocked, say exactly what is missing and who should provide it.
“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.
Files
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_targetsrecords 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
- Read the thesis.
- Define a narrow sourcing slice: sector, geography, size, and ownership signal.
- Search for candidate companies.
- Check whether each company already exists in the pipeline.
- Add only qualified targets with source citations, fit score, rationale, and next action.
- Stop before outreach.
Contact Enricher
- Find targets missing a primary contact.
- Research owner, CEO, founder, broker, banker, or relevant decision-maker.
- Add name, title, LinkedIn, email if available, confidence, and source.
- Mark uncertain email addresses as unverified.
- Escalate when the best contact is ambiguous.
Intermediary Coverage
- Review intermediaries by next touch due and thesis relevance.
- Draft check-ins that reference recent deals and the fund’s mandate.
- Keep drafts under 150 words unless asked otherwise.
- Save or present drafts for approval. Do not send.
- Suggest new intermediaries when a coverage gap appears.
Head Of BD
- Read thesis and pipeline health.
- Decompose sourcing work into mandates.
- Assign or recommend work by specialty.
- Summarize coverage, conversion, bottlenecks, and next partner decisions.
- 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.
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
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.

