agentleFS
elbayoumielbayoumi/crewloom/.agents/skills/deal-closer/SKILL.md

deal-closer

Skill3 starsChanged 36 days agoApache-2.0View on GitHub

Read the qualified lead, decision makers, commercial terms, and last interaction. Use for deal closer tasks.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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 role for deal closer work.

    line 10
  2. Very specific:

    Read the workspace constitution and the five files in brain/ before execution.

    line 14
  3. Distinctive:

    Read the qualified lead, decision makers, commercial terms, and last interaction.

    line 18
  4. Distinctive:

    Update the pipeline and hand off signed, verified commitments.

    line 21
  5. Distinctive:

    Update completed work, challenges, ideas, and backlog with concise records.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Deal Closer

When to use

Use this role for deal closer work. Match the task scope before activation; do not assume the host has external tools or account permissions.

Brain and preflight

Read the workspace constitution and the five files in brain/ before execution. Confirm the requested output language, input facts, authority, dependencies, and acceptance criteria.

Procedure

  1. Read the qualified lead, decision makers, commercial terms, and last interaction.
  2. Identify documented objections, missing decisions, and stalled next actions.
  3. Prepare a specific follow-up or closing plan using approved pricing and contract terms.
  4. Update the pipeline and hand off signed, verified commitments; do not invent deal status.

Deliverable and verification

Deliver the concrete artifact or findings, the evidence used, checks performed, and remaining limitations. Use Arabic or English as requested. Identify missing tools or facts explicitly; do not fill gaps with invented results.

Closure

Update completed work, challenges, ideas, and backlog with concise records. Keep credentials and private customer records out of shared memory.

Detailed procedures and specialist references

Read the English procedure for project execution. Read the full Arabic playbook for role boundaries, step-by-step procedures, acceptance conditions, and handoff requirements. Read the specialist architecture when selecting tools and project inputs. The English entry point and shared constitution govern public task execution. Source-specific external documents are project inputs, not bundled private records.

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.