How do I install the Payment Terms General skill?

Run npx skillmds@latest add scholarly360/payment-terms-general in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Payment Terms General safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Payment Terms General?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Payment Terms General free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Payment Terms General?

scholarly360 (@scholarly360) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Payment Terms General by scholarly360

Name: Payment Terms General
Author: scholarly360

Payment Terms General

Analyze, draft, and review Payment Terms clauses for General contracts. Use when the user mentions payment terms, invoicing, net-30, payment schedule, or asks to review, redline, or generate this clause type. Returns structured risk assessment, plain-language summary, and suggested alternative language.

scholarly360 e47c26a 2 files · 3.8 KB Updated Sep 17, 2026

File contents

Payment Terms Clause -- General

This skill provides expert-level analysis and drafting assistance for Payment Terms clauses in General contracts.

When to Activate

Activate this skill when the user:

Uploads or pastes a contract containing a Payment Terms clause
Asks to draft, redline, or improve a Payment Terms clause
Asks for a risk assessment of an existing Payment Terms provision
Mentions keywords: payment terms, invoicing, net-30, payment schedule

Workflow

Step 1 -- Intake

Ask the user (if not already provided):

Which party are you representing? (e.g., vendor, client, buyer, seller)
Jurisdiction governing the contract? (e.g., New York, California, England & Wales)
Is this a draft for review or should I generate fresh language?

Step 2 -- Analysis

If reviewing existing language, output the following structure:

## Payment Terms Clause Analysis

### Plain-Language Summary
[2-3 sentence plain-English description of what the clause does]

### Key Provisions Identified
- [Provision 1]
- [Provision 2]

### Risk Assessment
| Item | Risk Level | Notes |
|------|-----------|-------|
| [item] | High / Medium / Low | [explanation] |

### Recommended Redlines
[Specific suggested changes with rationale]

### Market Standard Comparison
[How this clause compares to typical General market standard]

Step 3 -- Drafting

If generating new language, produce:

Balanced version (neither party-favored)
Favorable to client version
Negotiation notes -- what the other side will likely push back on

Payment Terms Playbook -- General

See scripts/playbook.md for detailed clause-specific guidance, fallback positions, jurisdiction-specific notes, and precedent language.

Important Notes

Always caveat that output is not legal advice and should be reviewed by qualified counsel.
Flag any provisions that may be unenforceable or jurisdiction-specific.
When jurisdiction is unknown, apply general common-law principles and note assumptions.

---name: payment-terms-generaldescription: Analyze, draft, and review Payment Terms clauses for General contracts. Use when the user mentions payment terms, invoicing, net-30, payment schedule, or asks to review, redline, or generate this clause type. Returns structured risk assessment, plain-language summary, and suggested alternative language.---# Payment Terms Clause -- GeneralThis skill provides expert-level analysis and drafting assistance for**Payment Terms** clauses in **General** contracts.---## When to ActivateActivate this skill when the user:- Uploads or pastes a contract containing a Payment Terms clause- Asks to **draft**, **redline**, or **improve** a Payment Terms clause- Asks for a **risk assessment** of an existing Payment Terms provision- Mentions keywords: *payment terms, invoicing, net-30, payment schedule*---## Workflow### Step 1 -- IntakeAsk the user (if not already provided):1. **Which party** are you representing? *(e.g., vendor, client, buyer, seller)*2. **Jurisdiction** governing the contract? *(e.g., New York, California, England & Wales)*3. **Is this a draft for review or should I generate fresh language?**### Step 2 -- AnalysisIf reviewing existing language, output the following structure:```## Payment Terms Clause Analysis### Plain-Language Summary[2-3 sentence plain-English description of what the clause does]### Key Provisions Identified- [Provision 1]- [Provision 2]### Risk Assessment| Item | Risk Level | Notes ||------|-----------|-------|| [item] | High / Medium / Low | [explanation] |### Recommended Redlines[Specific suggested changes with rationale]### Market Standard Comparison[How this clause compares to typical General market standard]```### Step 3 -- DraftingIf generating new language, produce:1. **Balanced version** (neither party-favored)2. **Favorable to client** version3. **Negotiation notes** -- what the other side will likely push back on---## Payment Terms Playbook -- General> See `scripts/playbook.md` for detailed clause-specific guidance,> fallback positions, jurisdiction-specific notes, and precedent language.---## Important Notes- Always caveat that output is not legal advice and should be reviewed by qualified counsel.- Flag any provisions that may be unenforceable or jurisdiction-specific.- When jurisdiction is unknown, apply general common-law principles and note assumptions.

Frequently asked questions