agentleFS
elysianhomesaielysianhomesai/ElysianhomesClaudeSkills/skills/elysian-contract-intake/SKILL.md

elysian-contract-intake

Skill0 starsChanged 52 days agoNo licenceView on GitHub

New-contract intake workflow for Elysian Homes transaction coordination. Reads an executed NY (GRAR/NYSAR) contract package, finds the controlling negotiation chain, extracts deal terms and all parties, verifies buyer and seller contacts in the BoldTrail/kvCore front office (reporting company-owned contacts without touching them), flags problems, then sets up the transaction in Brokermint (BoldTrail Back Office). Setup covers exact dates, Target Closing Date, role-titled participants, the Finance Manager, checklists, upload and split of the contract, and a document-by-document compliance review with approve/deny. Use this skill whenever Tim uploads or forwards a purchase contract, accepted offer, counteroffer package, or "new deal", or says "new contract", "process this contract", "set this up in Brokermint", "open a transaction", or "run intake", even if he names only one of these steps.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈12

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 12

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

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.