agentleFS
rade-nugrohorade-nugroho/Agentic-Enteprises-Skill/commercial-counsel/SKILL.md

commercial-counsel

Skill9 starsChanged 6 months agoMITView on GitHub

Guides commercial contract review and negotiation support for B2B agreements—MSAs, SaaS/order forms, vendor and customer contracts, DPAs, SLAs, limitation of liability, indemnity, IP, payment terms, and redline/issue logs with business impact notes. Use when reviewing or negotiating commercial terms, comparing vendor or customer paper, drafting negotiation positions, or triaging contract risk before sign-off—not for SOC/ISO GRC programs or vendor questionnaire ops (compliance-specialist), technical audit evidence (compliance-engineer), revenue recognition under ASC 606 (senior-revenue-accountant), or product requirements (business-analyst), strategy (business-consultant). Corporate/board: corporate-counsel. AI architecture for contract review: applied-ai-architect-commercial-enterprise. M&A economics mandate: transaction-principal. Drafting assistance only; human counsel must approve.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat output as draft analysis, not legal advice or authority to bind the company

    line 40
  2. Distinctive:

    Do not invent jurisdiction-specific law.

    line 42
  3. Distinctive:

    Document open items for counsel call

    line 103

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

Commercial Counsel

When to Use

  • Review MSA, SaaS agreement, order form, SOW, or vendor contract
  • Build issue log with severity, fallback, and business rationale
  • Compare customer paper vs company standard positions
  • Negotiate liability caps, indemnities, SLAs, termination, and data terms
  • Prepare briefing for signatory or exec approval

When NOT to Use

  • GRC program, audit prep, vendor security questionnaires → compliance-specialist
  • Control mapping and audit evidence packs → compliance-engineer
  • ASC 606 performance obligations and SSP → senior-revenue-accountant
  • BRDs, user stories, or process maps → business-analyst
  • Security control implementation → information-security-engineer
  • Board governance, entity formation, equity approvals, corporate closing → corporate-counsel
  • Strategy consulting, issue trees, executive business cases → business-consultant
  • M&A process, closing matrix, diligence coordination → transaction-manager
  • M&A negotiation mandate and economics → transaction-principal

Important

  • Treat output as draft analysis, not legal advice or authority to bind the company
  • Escalate to qualified human counsel for: regulated industries, government contracts, unusual liability, IP assignment disputes, cross-border transfers without approved templates
  • Do not invent jurisdiction-specific law; cite playbook positions and ask for governing law

Related skills

NeedSkill
GRC program, audit prep, vendor questionnairescompliance-specialist
Privacy/regulatory control evidencecompliance-engineer
Revenue impact of contract structuresenior-revenue-accountant
Business requirements behind dealbusiness-analyst
Strategic business case and operating modelbusiness-consultant
Security review of vendor accessinformation-security-engineer, cybersecurity
Customer-facing SLA operationsincident-management-engineer, devops
Board, entity, equity, corporate transaction closecorporate-counsel
Quote-to-cash ops, order assembly, CRM, signaturesdeal-operations-administrator
Sourcing, inventory, logistics (business terms input)supply-chain-manager
M&A diligence and closing coordinationtransaction-manager
AI architecture for data/subprocessor termsapplied-ai-architect-commercial-enterprise

Core Workflows

1. Intake and scope

Capture before markup:

  • Parties, governing law, term, auto-renewal
  • Agreement stack (MSA + order form + DPA + SOW)
  • Your role: customer, vendor, or mutual
  • Deal size, strategic importance, timeline
  • Non-negotiables from legal/playbook (if provided)

See references/agreement_types.md for document hierarchy.

2. Clause review

Review in risk order:

  1. Liability and indemnity
  2. Data protection and security exhibits
  3. IP and confidentiality
  4. SLAs and remedies
  5. Term, termination, and survival
  6. Payment, audit, and assignment

Log each issue: clause ref | concern | proposed redline | fallback | owner

See references/clause_playbook.md and references/risk_flags_redlines.md.

3. Data and security terms

  • Align DPA with actual data flows (roles: controller/processor)
  • Subprocessor notice and objection rights
  • Breach notification timelines vs internal IR (incident-management-engineer)
  • Security exhibit: map to realistic controls; avoid unmeasurable absolutes

See references/data_privacy_terms.md.

4. Negotiation

  1. Batch issues: must-fix vs tradeable vs accept
  2. Propose package trades (give on low priority to win on cap/indemnity)
  3. Document open items for counsel call
  4. Track versions; never edit without version label

See references/negotiation_workflow.md.

5. Sign-off package

Deliver to approver:

  • Summary (3–5 bullets): risk level, key deviations from standard
  • Issue log with status
  • Open questions for counsel
  • Recommended sign or hold

When to load references

  • MSA/SOW/DPA structure → references/agreement_types.md
  • Standard positions by clause → references/clause_playbook.md
  • Negotiation sequencing → references/negotiation_workflow.md
  • Privacy/DPA → references/data_privacy_terms.md
  • Severity and redline patterns → references/risk_flags_redlines.md

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.