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

deal-desk-create-agent

Skill1 starsChanged 6 months agoMITView on GitHub

Hire or configure DealDesk employees such as Sector Sourcers, Contact Enrichers, Intermediary Coverage Analysts, Heads of BD, and custom PE analysts. Use when creating a DealDesk agent, choosing a role template, drafting AGENTS.md instructions, or applying DealDesk skills to a new hire.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user asks to hire, create, or configure a DealDesk employee.

    line 15
  2. Distinctive:

    Prefer an existing DealDesk role template when possible:

    line 33
  3. Distinctive:

    Custom Employee: use when the role is fund-specific or outside the defaults.

    line 39
  4. Distinctive:

    If the requested role does not match a template, state the closest template and what you changed.

    line 41
  5. Distinctive:

    Leave scheduled heartbeats off unless the role truly needs recurring work.

    line 56
  6. Distinctive:

    Every DealDesk agent instruction bundle should include:

    line 60
  7. Distinctive:

    Avoid broad platform-maintenance instructions unless the role is explicitly a DealDesk app developer/operator.

    line 70
  8. Distinctive:

    When creating a DealDesk agent through the app/API, include:

    line 74
  9. Very specific:

    Use role: "general" for PE employees when the app’s authorization path expects non-CEO operational roles.

    line 102
  10. Distinctive:

    Before creating the hire, confirm:

    line 106

≈ “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.

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

DealDesk Create Agent Skill

Use this skill when the user asks to hire, create, or configure a DealDesk employee.

The output should be a PE-relevant agent with clear role boundaries, DealDesk skills attached, and instructions that update the application records rather than producing disconnected prose.

Default Skill Set

DealDesk hires should receive these skills unless the user asks for a narrower configuration:

  • dealdesk
  • dealdesk-converting-plans-to-tasks
  • dealdesk-create-agent
  • dealdesk-create-plugin
  • dealdesk-dev

These keys are intentionally preserved for compatibility, but their content is DealDesk-specific.

Role Selection

Prefer an existing DealDesk role template when possible:

  • Sector Sourcer: finds and scores acquisition targets.
  • Contact Enricher: identifies owners, CEOs, founders, bankers, brokers, and advisors.
  • Intermediary Coverage Analyst: maps and drafts relationship touches.
  • Head of BD: decomposes mandates, delegates work, and summarizes pipeline health.
  • Custom Employee: use when the role is fund-specific or outside the defaults.

If the requested role does not match a template, state the closest template and what you changed.

Hiring Inputs

Collect or infer conservatively:

  • Name and title.
  • Reporting line, if the company has an org structure.
  • Role mandate and boundaries.
  • Adapter type and execution settings.
  • Monthly budget.
  • Whether scheduled heartbeats are needed.
  • Which DealDesk skills to attach.
  • Instructions bundle content.

Leave scheduled heartbeats off unless the role truly needs recurring work. Sourcing and enrichment roles often do; one-off analysts often do not.

Instruction Requirements

Every DealDesk agent instruction bundle should include:

  • The active fund/thesis context if known.
  • The exact DealDesk records the agent may update.
  • Dedupe and citation rules.
  • Outreach approval boundary.
  • Fit scoring guidance.
  • Completion/reporting expectations.
  • The attached DealDesk skills and when to use each one.

Avoid broad platform-maintenance instructions unless the role is explicitly a DealDesk app developer/operator.

Quick Hire Payload Shape

When creating a DealDesk agent through the app/API, include:

{
  "name": "Atlanta HVAC Sourcer",
  "title": "Sector Sourcer",
  "role": "general",
  "adapterType": "claude_local",
  "adapterConfig": {
    "dangerouslySkipPermissions": true
  },
  "desiredSkills": [
    "dealdesk",
    "dealdesk-converting-plans-to-tasks",
    "dealdesk-create-agent",
    "dealdesk-create-plugin",
    "dealdesk-dev"
  ],
  "instructionsBundle": {
    "entryFile": "AGENTS.md",
    "files": {
      "AGENTS.md": "You are a senior PE sourcing analyst..."
    }
  },
  "budgetMonthlyCents": 5000
}

Use role: "general" for PE employees when the app’s authorization path expects non-CEO operational roles.

Quality Checklist

Before creating the hire, confirm:

  • The role has a specific PE mandate.
  • The agent knows which DealDesk records to read and update.
  • The desired skill list includes the converted DealDesk skills.
  • The instructions forbid duplicate targets and fabricated data.
  • Outreach is draft-only unless the user explicitly authorizes sending.
  • The budget and heartbeat cadence match the job.
  • The user can review or approve sensitive actions.

After Creation

Report:

  • Agent name and role.
  • Attached DealDesk skills.
  • Budget and heartbeat posture.
  • First recommended task or mandate.
  • Any missing thesis/context needed before useful work begins.

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.