Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/agreement-generator

@820dfc8
Run it yourself

Draft a business agreement from the selected relationship type, confirmed party and commercial facts, and explicit proposed choices with provenance. Use when preparing a service, partnership, licensing or other business agreement. Trigger with "agreement-generator" or "create a freelancer agreement".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/agreement-generator

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesagreement-decisions.md

≈1k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Agreement decisions and provenance

Ten relationship types

Type Establish before drafting
Freelancer Actual scope, deliverables/acceptance, payment, IP choices and working-fact questions.
Partnership Purpose, contributions, ownership/economics, authority, governance and exit decisions.
NDA Disclosure direction, permitted purpose, protected information and explicit duration/handling choices.
Licensing Identified rights, grant scope, territory, exclusivity, fees and sublicense/use restrictions.
Consulting Services/deliverables, responsibilities, fee base, expenses, acceptance and changes.
SOW Master agreement/precedence, deliverables, milestones, dependencies, acceptance and change process.
MSA Actual service framework, SOW incorporation, responsibilities and requested risk/operational allocation.
Joint venture Actual form/purpose, contributions, control, economics and wind-down; no entity formation inferred.
Distribution Products, territory, channels, exclusivity, ordering, inventory and support choices.
Referral Qualification, commission base, attribution, payment trigger, reporting and reversals/exclusions.

The type routes questions; it does not make every confidentiality, payment, indemnity, IP, non-compete or liability clause mandatory. Select relevant sections and identify missing decisions. A multiparty deal requires actual role/obligation mapping, not just adding more signature columns.

Decision record

For each material choice record the supplied fact or proposed option, source, party/obligation affected, units/dates, dependencies and unresolved review question. Reuse known decisions. If the user delegates choosing options, keep them labeled as proposals until their status actually changes.

Do not invent party names, entity types, notice contacts, effective dates, fees, benchmarks, remedies, arbitration or rights transfers to make a document look complete. A notice address does not establish incorporation or governing law.

Check definitions, reciprocal obligations, payment/acceptance, termination/survival, IP/licenses, data handling, schedules and precedence together. Preserve relevant requirements rather than optimizing for a round clause count.

Sources, licensing and benchmarking

Inspect the actual selected template before relying on it. Record its source, version/text, license and applicable attribution; distinguish direct copying, adaptation and original proposed wording. A repository/tool license does not by itself establish the license of every document it distributes.

Common Paper standard agreements and its editing guidance are source/provenance starting points. Its published materials identify CC BY 4.0 licensing; verify the actual selected asset and preserve attribution. Do not call modified text the unchanged standard or claim an unperformed benchmark or author approval. Free availability is not evidence of suitability for the user's deal.

If legal adjustments are requested, identify the current jurisdiction, actual facts and primary authority used. A short state/country label or industry name cannot establish which worker-status, consumer, tax or dispute rule applies. Unsupported assertions remain questions for qualified review.

Draft and review artifacts

Keep the requested agreement copy separate from assumptions, source notes and plain-language explanations unless the user asks for an annotated draft. Mark unresolved material decisions and actual draft status. Do not invent signatures, party acceptance or execution. Sending, signing, filing or implementing a deal is a distinct authorized action, not an implicit generation step.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill acts as a guided wizard for generating professional business agreement templates. It collects necessary transaction details from the user and outputs a structured markdown document based on industry-standard benchmarking, including a legal disclaimer.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 weeks ago
What it can do
Reads files Edits files
version
1.2.0
author
Intent Solutions <jeremy@intentsolutions.io>
compatibility
Designed for Claude Code
All 4 allowed tools
ReadWriteGlobGrep
Other metadata
tags
[
  "legal",
  "agreements",
  "contracts",
  "business",
  "document-generation"
]

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/agreement-generator