Agent skill · affaan-m
master-agreement-generator
Generate review drafts of counterparty master agreements from one template plus a JSON spec, with role-selected clauses and a Schedule A workflow limited to the executed agreement's notice authority. Use when you need reproducible drafting and separately reviewed execution preparation.
What it needs
About 6k tokens when loaded.
What this skill does
Master Agreement Generator One master template, one small spec per counterparty, one draft build step. The generator always labels output DRAFT, including documents generated from a completed template. A successful conversion proves artifact generation, not legal completeness, authority to contract, or readiness to send or sign. An executed agreement may permit designated opportunities to be added by notice; that authority must be established before using the Schedule A workflow. When to Use You issue a framework agreement (NDA, referral or sourcing fee, non-circumvention, master services) to many counterparties with the same terms and a few party-specific fields. Deals are added over time and re-papering each one is the bottleneck. Documents must be reproducible from tracked source, diffable, and free of hand edits. Signature fields are placed by automation and need a stable page layout. How It Works Template A single markdown template with {{PLACEHOLDER}} fields. Every party-specific value is a placeholder; everything else is fixed text. A skeleton lives at references/master-template.example.md. Replace its generic sentences with your counsel-approved clauses. Placeholders the reference script fills: Placeholder Source --- --- {{DATE}} spec.date, default today {{CPSHORT}} spec.short {{CPLEGAL}}, {{CPJURIS}}, {{CPADDR}} spec fields, or a blank line when the counterparty completes them at signing {{ROLECLAUSE}}, {{FEETITLE}}, {{FEECLAUSE}} selected by spec.role from the role table {{SCHEDULEROWS}} spec.schedule, or one "no entries at signing" row {{SUPPLEMENTCLAUSE}} spec.supplement, rendered with a trailing separator or empty {{CPSIGBLOCK}}, {{CPSIGNER}}, {{CPTITLE}}, {{CPEMAIL}} signature block fields, blanks when unknown Spec One JSON file per counterparty: Only file, short, and role are required for a draft. Missing signature fields render as blank lines for review and completion. See references/spec.example.json. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/master-agreement-generator--344c5b