sure-scale/doc-haus/playbook-services-agreement
Claude Code and agent skill by sure-scale/doc-haus
- community
Checking that the SKILL.md file is still in the repository.
Firm playbook: positions, fallbacks, and approved clause text for US commercial services and consulting agreements, taken from the customer side. Do not apply to agreements governed by non-US law.
Install
npx vskill@latest install sure-scale/doc-haus/playbook-services-agreementSKILL.md
This is an executable firm playbook for US commercial services and consulting agreements, reviewed from the customer (services recipient) side. The contract-type and jurisdiction tags for every position below come from this header (commercial services/consulting agreement; US governing law).
Each ## section is one clause type, stated on a fixed schema so the redline tool can paste the firm text byte-exact, the deterministic lint can detect deviation, and document-reviewer can band each clause:
- Preferred — the firm's default opening position. Text inside an
``approved fence is the firm-approved replacement text — copy it byte-exact into the redline tool's replacement` arg.
- Fallbacks — acceptable rungs below Preferred, each introduced by the
"when" condition that justifies offering it (the "offer when" trigger). Text inside an ```approved-fallback fence is the firm's fallback text, to be used only when its stated condition is met.
- Unacceptable — the walk-away floor: the position the firm does not concede
below without a human decision.
- Rationale — why the position sits where it does.
These positions are firm-configurable defaults, calibrated to be market-balanced rather than aspirational. The matter's .dochaus/profile.md (see the firm-profile skill) overrides any Preferred, fallback, or floor here; where it is silent, these defaults apply. When a counterparty term sits at or below the Unacceptable floor, do not concede: escalate to the supervising lawyer for the matter, or to the contact named in the profile's Escalation Rules. The escalation is addressed to that role, not a named person, so the position outlasts any individual assignment.
Jurisdiction guard: The positions below reflect US commercial market practice and assume a US governing law. If the agreement's governing law is outside the United States, do not apply this playbook; flag the mismatch instead of adapting the clauses. Enforceability of particular terms varies by state — treat the positions as market reference points, not statements of law.
Scope of services and statements of work
Preferred: All services are performed under written statements of work that incorporate the agreement, with a written change-order process; neither party is obligated by, or pays for, work outside an executed SOW or change order.
Unacceptable: services defined only by a vague recital with no SOW mechanism; changes to scope or fees effective by email or by the provider's notice alone; an SOW permitted to override the agreement's liability, indemnity, or IP terms without expressly saying so.
Rationale: SOW discipline is the control surface for the whole agreement: it bounds fees, defines acceptance, and prevents the provider from converting informal requests into billable scope. Silent SOW-over-master precedence lets negotiated protections be undone in later paperwork that legal never sees.
Payment terms
Preferred: Invoices payable net thirty days, fees fixed for the SOW term, pre-approved expenses only, and a good-faith dispute right that suspends only the disputed portion.
Fallbacks: when the provider has genuine working-capital constraints and the engagement is short.
Unacceptable: payment due on receipt or in fewer than fifteen days; automatic late fees or interest accruing on disputed amounts; a provider right to suspend all services for nonpayment of a disputed invoice; uncapped or unapproved expense pass-through; rate increases during an SOW term.
Rationale: Net thirty with a carve-out for good-faith disputes is the US commercial baseline. The dispute mechanics matter more than the day count: if disputed amounts accrue interest or trigger suspension, the customer's only leverage over defective work disappears.
Intellectual property in deliverables
Preferred: Deliverables are owned by the customer on payment as work made for hire (with a backup assignment); the provider retains its pre-existing materials and general know-how but grants a broad license to whatever pre-existing materials are embedded in the deliverables.
Fallbacks: when the provider's business model depends on reusing deliverable components and the customer does not need exclusivity.
Unacceptable: provider ownership of deliverables with only a terminable or revocable license back; any assignment to the provider of the customer's pre-existing intellectual property or data; ownership conditioned on payment of amounts disputed in good faith; silence on embedded third-party or open-source components.
Rationale: The customer pays for the deliverables and should own them; the provider legitimately keeps its toolkit. The embedded-materials license is the clause that makes ownership real — owning a deliverable you cannot lawfully run or modify is worthless. Work-made-for-hire status depends on the work's category under US copyright law, which is why the express backup assignment is required rather than optional.
Warranties
Preferred: The provider warrants professional, workmanlike performance conforming to the SOW, non-infringement, and compliance with applicable law, with re-performance or refund as the first-line remedy for nonconforming services.
Fallbacks: when the provider insists that re-performance and refund be the exclusive remedy for the performance warranty.
Unacceptable: services provided entirely "as is"; a warranty period shorter than thirty days from delivery or acceptance; a disclaimer that also disclaims the express warranties given in the agreement; an exclusive remedy that swallows the indemnities.
Rationale: Professional-services warranties are about conformance and competence, not perfection. The re-performance ladder gives the provider a fair cure path while preserving refund and termination as the backstop; the fallback concedes exclusivity only for the performance warranty and expressly preserves the indemnity, which is the concession providers actually need.
Indemnification
Preferred: The provider indemnifies against third-party claims of IP infringement and claims arising from bodily injury, property damage, or the provider's gross negligence or willful misconduct, with a standard control-of-defense procedure and IP mitigation options.
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 96 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingdochaus/playbooks/playbook-services-agreement/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/sure-scale/doc-haus/playbook-services-agreement)