[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78H75FFFQ6Y4PEBAT3BM8MB":3,"skill-same:01M78H75FFFQ6Y4PEBAT3BM8MB":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M78H75FFFQ6Y4PEBAT3BM8MB","contract-and-proposal-writer",null,"Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting points. Use when drafting a freelance contract, preparing a client proposal, writing an SOW for a new engagement, or producing an NDA before sharing sensitive material.","aneeba-pixel\u002Fclaude-skills","aneeba-pixel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F218186338?v=4","01M78GRXBTG70217SH410P543Y","Aneeba Saeed","01M78GRXCDZ6TA0F8H2CZMDGSS",0,"MIT","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fbusiness-growth\u002Fskills\u002Fcontract-and-proposal-writer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"contract-and-proposal-writer\"\ndescription: \"Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting points. Use when drafting a freelance contract, preparing a client proposal, writing an SOW for a new engagement, or producing an NDA before sharing sensitive material.\"\n---\n\n# Contract & Proposal Writer\n\n**Tier:** POWERFUL  \n**Category:** Business Growth  \n**Domain:** Legal Documents, Business Development, Client Relations\n\n---\n\n## Overview\n\nGenerate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Outputs structured Markdown with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions.\n\n**Not a substitute for legal counsel.** Use these templates as strong starting points; review with an attorney for high-value or complex engagements.\n\n---\n\n## Core Capabilities\n\n- Freelance development contracts (fixed-price & hourly)\n- Project proposals with timeline\u002Fbudget breakdown\n- Statements of Work (SOW) with deliverables matrix\n- NDAs (mutual & one-way)\n- Master Service Agreements (MSA)\n- Jurisdiction-specific clauses (US\u002FEU\u002FUK\u002FDACH)\n- GDPR Data Processing Addenda (EU\u002FDACH)\n\n---\n\n## Key Clauses Reference\n\n| Clause | Options |\n|--------|---------|\n| Payment terms | Net-30, milestone-based, monthly retainer |\n| IP ownership | Work-for-hire (US), assignment (EU\u002FUK), license-back |\n| Liability cap | 1x contract value (standard), 3x (high-risk) |\n| Termination | For cause (14-day cure), convenience (30\u002F60\u002F90-day notice) |\n| Confidentiality | 2-5 year term, perpetual for trade secrets |\n| Warranty | \"As-is\" disclaimer, limited 30\u002F90-day fix warranty |\n| Dispute resolution | Arbitration (AAA\u002FICC), courts (jurisdiction-specific) |\n\n---\n\n## When to Use\n\n- Starting a new client engagement and need a contract fast\n- Client asks for a proposal with pricing and timeline\n- Partnership or vendor relationship requiring an MSA\n- Protecting IP or confidential information with an NDA\n- EU\u002FDACH project requiring GDPR-compliant data clauses\n\n---\n\n## Workflow\n\n### 1. Gather Requirements\n\nAsk the user:\n\n    1. Document type? (contract \u002F proposal \u002F SOW \u002F NDA \u002F MSA)\n    2. Jurisdiction? (US-Delaware \u002F EU \u002F UK \u002F DACH)\n    3. Engagement type? (fixed-price \u002F hourly \u002F retainer)\n    4. Parties? (names, roles, business addresses)\n    5. Scope summary? (1-3 sentences)\n    6. Total value or hourly rate?\n    7. Start date \u002F end date or duration?\n    8. Special requirements? (IP assignment, white-label, subcontractors)\n\n### 2. Select Template\n\n| Type | Jurisdiction | Template |\n|------|-------------|----------|\n| Dev contract fixed | Any | Template A |\n| Consulting retainer | Any | Template B |\n| SaaS partnership | Any | Template C |\n| NDA mutual | US\u002FEU\u002FUK\u002FDACH | NDA-M |\n| NDA one-way | US\u002FEU\u002FUK\u002FDACH | NDA-OW |\n| SOW | Any | SOW base |\n\n### 3. Generate & Fill\n\nFill all [BRACKETED] placeholders. Flag missing data as \"REQUIRED\".\n\n### 4. Convert to DOCX\n\n```bash\n# Install pandoc\nbrew install pandoc        # macOS\napt install pandoc         # Ubuntu\n\n# Basic conversion\npandoc contract.md -o contract.docx \\\n  --reference-doc=reference.docx \\\n  -V geometry:margin=1in\n\n# With numbered sections (legal style)\npandoc contract.md -o contract.docx \\\n  --number-sections \\\n  -V documentclass=article \\\n  -V fontsize=11pt\n\n# With custom company template\npandoc contract.md -o contract.docx \\\n  --reference-doc=company-template.docx\n```\n\n---\n\n## Jurisdiction Notes\n\n### US (Delaware)\n- Governing law: State of Delaware\n- Work-for-hire doctrine applies (Copyright Act 101)\n- Arbitration: AAA Commercial Rules\n- Non-compete: enforceable with reasonable scope\u002Ftime\n\n### EU (GDPR)\n- Must include Data Processing Addendum if handling personal data\n- IP assignment requires separate written deed in some member states\n- Arbitration: ICC or local chamber\n\n### UK (post-Brexit)\n- Governed by English law\n- IP: Patents Act 1977 \u002F CDPA 1988\n- Arbitration: LCIA Rules\n- Data: UK GDPR (post-Brexit equivalent)\n\n### DACH (Germany \u002F Austria \u002F Switzerland)\n- BGB (Buergerliches Gesetzbuch) governs contracts\n- Written form requirement for certain clauses (para 126 BGB)\n- IP: Author always retains moral rights; must explicitly transfer Nutzungsrechte\n- Non-competes: max 2 years, compensation required (para 74 HGB)\n- Jurisdiction: German courts (Landgericht) or DIS arbitration\n- DSGVO (GDPR implementation) mandatory for personal data processing\n- Kuendigungsfristen: statutory notice periods apply\n\n---\n\n## Template A: Web Dev Fixed-Price Contract\n\n```markdown\n# SOFTWARE DEVELOPMENT AGREEMENT\n\n**Effective Date:** [DATE]\n**Client:** [CLIENT LEGAL NAME], [ADDRESS] (\"Client\")\n**Developer:** [YOUR LEGAL NAME \u002F COMPANY], [ADDRESS] (\"Developer\")\n\n---\n\n## 1. SERVICES\n\nDeveloper agrees to design, develop, and deliver:\n\n**Project:** [PROJECT NAME]\n**Description:** [1-3 sentence scope]\n\n**Deliverables:**\n- [Deliverable 1] due [DATE]\n- [Deliverable 2] due [DATE]\n- [Deliverable 3] due [DATE]\n\n## 2. PAYMENT\n\n**Total Fee:** [CURRENCY] [AMOUNT]\n\n| Milestone | Amount | Due |\n|-----------|--------|-----|\n| Contract signing | 50% | Upon execution |\n| Beta delivery | 25% | [DATE] |\n| Final acceptance | 25% | Within 5 days of acceptance |\n\nLate payments accrue interest at 1.5% per month.\nClient has [10] business days to accept or reject deliverables in writing.\n\n## 3. INTELLECTUAL PROPERTY\n\nUpon receipt of full payment, Developer assigns all right, title, and interest in the\nWork Product to Client as a work made for hire (US) \u002F by assignment of future copyright (EU\u002FUK).\n\nDeveloper retains the right to display Work Product in portfolio unless Client\nrequests confidentiality in writing within [30] days of delivery.\n\nPre-existing IP (tools, libraries, frameworks) remains Developer's property.\nDeveloper grants Client a perpetual, royalty-free license to use pre-existing IP\nas embedded in the Work Product.\n\n## 4. CONFIDENTIALITY\n\nEach party keeps confidential all non-public information received from the other.\nThis obligation survives termination for [3] years.\n\n## 5. WARRANTIES\n\nDeveloper warrants Work Product will substantially conform to specifications for\n[90] days post-delivery. Developer will fix material defects at no charge during\nthis period. EXCEPT AS STATED, WORK PRODUCT IS PROVIDED \"AS IS.\"\n\n## 6. LIABILITY\n\nDeveloper's total liability shall not exceed total fees paid under this Agreement.\nNeither party liable for indirect, incidental, or consequential damages.\n\n## 7. TERMINATION\n\nFor Cause: Either party may terminate if the other materially breaches and fails\nto cure within [14] days of written notice.\n\nFor Convenience: Client may terminate with [30] days written notice and pay for\nall work completed plus [10%] of remaining contract value.\n\n## 8. DISPUTE RESOLUTION\n\nUS: Binding arbitration under AAA Commercial Rules, [CITY], Delaware law.\nEU\u002FDACH: ICC \u002F DIS arbitration, [CITY]. German \u002F English law.\nUK: LCIA Rules, London. English law.\n\n## 9. GENERAL\n\n- Entire Agreement: Supersedes all prior discussions.\n- Amendments: Must be in writing, signed by both parties.\n- Independent Contractor: Developer is not an employee of Client.\n\n---\n\nCLIENT: _________________________ Date: _________\n[CLIENT NAME], [TITLE]\n\nDEVELOPER: _________________________ Date: _________\n[YOUR NAME], [TITLE]\n```\n\n---\n\n## Template B: Monthly Consulting Retainer\n\n```markdown\n# CONSULTING RETAINER AGREEMENT\n\n**Effective Date:** [DATE]\n**Client:** [CLIENT LEGAL NAME] (\"Client\")\n**Consultant:** [YOUR NAME \u002F COMPANY] (\"Consultant\")\n\n---\n\n## 1. SERVICES\n\nConsultant provides [DOMAIN, e.g., \"CTO advisory and technical architecture\"] services.\n\n**Monthly Hours:** Up to [X] hours\u002Fmonth\n**Rollover:** Unused hours [do \u002F do not] roll over (max [X] hours banked)\n**Overflow Rate:** [CURRENCY] [RATE]\u002Fhr for hours exceeding retainer\n\n## 2. FEES\n\n**Monthly Retainer:** [CURRENCY] [AMOUNT], due on the 1st of each month.\n**Payment Method:** Bank transfer \u002F Stripe \u002F SEPA direct debit\n**Late Payment:** 2% monthly interest after [10]-day grace period.\n\n## 3. TERM AND TERMINATION\n\n**Initial Term:** [3] months starting [DATE]\n**Renewal:** Auto-renews monthly unless either party gives [30] days written notice.\n**Immediate termination:** For material breach uncured after [7] days notice.\n\nOn termination, Consultant delivers all work in progress within [5] business days.\n\n## 4. INTELLECTUAL PROPERTY\n\nWork product created under this Agreement belongs to [Client \u002F Consultant \u002F jointly].\nAdvisory output (recommendations, analyses) are Client property upon full payment.\n\n## 5. EXCLUSIVITY\n\n[OPTION A - Non-exclusive:]\nThis Agreement is non-exclusive. Consultant may work with other clients.\n\n[OPTION B - Partial exclusivity:]\nConsultant will not work with direct competitors of Client during the term\nand [90] days thereafter.\n\n## 6. CONFIDENTIALITY AND DATA PROTECTION\n\nEU\u002FDACH: If Consultant processes personal data on behalf of Client, the parties\nshall execute a Data Processing Agreement (DPA) per Art. 28 GDPR.\n\n## 7. LIABILITY\n\nConsultant's aggregate liability is capped at [3x] the fees paid in the [3] months\npreceding the claim.\n\n---\n\nSignatures as above.\n```\n\n---\n\n## Template C: SaaS Partnership Agreement\n\n```markdown\n# SAAS PARTNERSHIP AGREEMENT\n\n**Effective Date:** [DATE]\n**Provider:** [NAME], [ADDRESS]\n**Partner:** [NAME], [ADDRESS]\n\n---\n\n## 1. PURPOSE\n\nProvider grants Partner [reseller \u002F referral \u002F white-label \u002F integration] rights to\nProvider's [PRODUCT NAME] (\"Software\") subject to this Agreement.\n\n## 2. PARTNERSHIP TYPE\n\n[ ] Referral: Partner refers customers; earns [X%] of first-year ARR per referral.\n[ ] Reseller: Partner resells licenses; earns [X%] discount off list price.\n[ ] White-label: Partner rebrands Software; pays [AMOUNT]\u002Fmonth platform fee.\n[ ] Integration: Partner integrates Software via API; terms in Exhibit A.\n\n## 3. REVENUE SHARE\n\n| Tier | Monthly ARR Referred | Commission |\n|------|---------------------|------------|\n| Bronze | \u003C $10,000 | [X]% |\n| Silver | $10,000-$50,000 | [X]% |\n| Gold | > $50,000 | [X]% |\n\nPayout: Net-30 after month close, minimum $[500] threshold.\n\n## 4. INTELLECTUAL PROPERTY\n\nEach party retains all IP in its own products. No implied licenses.\nPartner may use Provider's marks per Provider's Brand Guidelines (Exhibit B).\n\n## 5. DATA AND PRIVACY\n\nEach party is an independent data controller for its own customers.\nJoint processing requires a separate DPA (Exhibit C - EU\u002FDACH projects).\n\n## 6. TERM\n\nInitial: [12] months. Renews annually unless [90]-day written notice given.\nTermination for Cause: [30]-day cure period for material breach.\n\n## 7. LIMITATION OF LIABILITY\n\nEach party's liability capped at [1x] fees paid\u002Freceived in prior [12] months.\nMutual indemnification for IP infringement claims from own products.\n\n---\n\nSignatures, exhibits, and governing law per applicable jurisdiction.\n```\n\n---\n\n## GDPR Data Processing Addendum (EU\u002FDACH Clause Block)\n\n```markdown\n## DATA PROCESSING ADDENDUM (Art. 28 GDPR)\n\nController: [CLIENT NAME]\nProcessor: [CONTRACTOR NAME]\n\n### Subject Matter\nProcessor processes personal data on behalf of Controller solely to perform services\nunder the main Agreement.\n\n### Categories of Data Subjects\n[e.g., end users, employees, customers]\n\n### Categories of Personal Data\n[e.g., names, email addresses, usage data]\n\n### Processing Duration\nFor the term of the main Agreement; deletion within [30] days of termination.\n\n### Processor Obligations\n- Process data only on Controller's documented instructions\n- Ensure persons authorized to process have committed to confidentiality\n- Implement technical and organizational measures per Art. 32 GDPR\n- Assist Controller with data subject rights requests\n- Not engage sub-processors without prior written consent\n- Delete or return all personal data upon termination\n\n### Sub-processors (current as of Effective Date)\n| Sub-processor | Location | Purpose |\n|--------------|----------|---------|\n| [AWS \u002F GCP \u002F Azure] | [Region] | Cloud hosting |\n| [Other] | [Location] | [Purpose] |\n\n### Cross-border Transfers\nData transfers outside EEA covered by: [ ] SCCs  [ ] Adequacy Decision  [ ] BCRs\n```\n\n---\n\n## Common Pitfalls\n\n1. **Missing IP assignment language** - \"work for hire\" alone is insufficient in EU; need explicit assignment of Nutzungsrechte in DACH\n2. **Vague acceptance criteria** - Always define what \"accepted\" means (written sign-off, X days to reject)\n3. **No change order process** - Scope creep kills fixed-price projects; add a clause for out-of-scope work\n4. **Jurisdiction mismatch** - Choosing Delaware law for a German-only project creates enforcement problems\n5. **Missing limitation of liability** - Without a cap, one bug could mean unlimited damages\n6. **Oral amendments** - Contracts modified verbally are hard to enforce; always require written amendments\n\n---\n\n## Best Practices\n\n- Use **milestone payments** over net-30 for projects >$10K - reduces cash flow risk\n- For EU\u002FDACH: always check if a DPA is needed (any personal data = yes)\n- For DACH: include a **Schriftformklausel** (written form clause) explicitly\n- Add a **force majeure** clause for anything over 3 months\n- For retainers: define response time SLAs (e.g., 4h urgent \u002F 24h normal)\n- Keep templates in version control; track changes with `git diff`\n- Review annually - laws change, especially GDPR enforcement interpretations\n- For NDAs: always specify the return\u002Fdestruction of confidential materials on termination\n","# Contract & Proposal Writer\n\n**Tier:** POWERFUL  \n**Category:** Business Growth  \n**Domain:** Legal Documents, Business Development, Client Relations\n\n---\n\n## Overview\n\nGenerate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Outputs structured Markdown with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions.\n\n**Not a substitute for legal counsel.** Use these templates as strong starting points; review with an attorney for high-value or complex engagements.\n\n---\n\n## Core Capabilities\n\n- Freelance development contracts (fixed-price & hourly)\n- Project proposals with timeline\u002Fbudget breakdown\n- Statements of Work (SOW) with deliverables matrix\n- NDAs (mutual & one-way)\n- Master Service Agreements (MSA)\n- Jurisdiction-specific clauses (US\u002FEU\u002FUK\u002FDACH)\n- GDPR Data Processing Addenda (EU\u002FDACH)\n\n---\n\n## Key Clauses Reference\n\n| Clause | Options |\n|--------|---------|\n| Payment terms | Net-30, milestone-based, monthly retainer |\n| IP ownership | Work-for-hire (US), assignment (EU\u002FUK), license-back |\n| Liability cap | 1x contract value (standard), 3x (high-risk) |\n| Termination | For cause (14-day cure), convenience (30\u002F60\u002F90-day notice) |\n| Confidentiality | 2-5 year term, perpetual for trade secrets |\n| Warranty | \"As-is\" disclaimer, limited 30\u002F90-day fix warranty |\n| Dispute resolution | Arbitration (AAA\u002FICC), courts (jurisdiction-specific) |\n\n---\n\n## When to Use\n\n- Starting a new client engagement and need a contract fast\n- Client asks for a proposal with pricing and timeline\n- Partnership or vendor relationship requiring an MSA\n- Protecting IP or confidential information with an NDA\n- EU\u002FDACH project requiring GDPR-compliant data clauses\n\n---\n\n## Workflow\n\n### 1. Gather Requirements\n\nAsk the user:\n\n    1. Document type? (contract \u002F proposal \u002F SOW \u002F NDA \u002F MSA)\n    2. Jurisdiction? (US-Delaware \u002F EU \u002F UK \u002F DACH)\n    3. Engagement type? (fixed-price \u002F hourly \u002F retainer)\n    4. Parties? (names, roles, business addresses)\n    5. Scope summary? (1-3 sentences)\n    6. Total value or hourly rate?\n    7. Start date \u002F end date or duration?\n    8. Special requirements? (IP assignment, white-label, subcontractors)\n\n### 2. Select Template\n\n| Type | Jurisdiction | Template |\n|------|-------------|----------|\n| Dev contract fixed | Any | Template A |\n| Consulting retainer | Any | Template B |\n| SaaS partnership | Any | Template C |\n| NDA mutual | US\u002FEU\u002FUK\u002FDACH | NDA-M |\n| NDA one-way | US\u002FEU\u002FUK\u002FDACH | NDA-OW |\n| SOW | Any | SOW base |\n\n### 3. Generate & Fill\n\nFill all [BRACKETED] placeholders. Flag missing data as \"REQUIRED\".\n\n### 4. Convert to DOCX\n\n```bash\n# Install pandoc\nbrew install pandoc        # macOS\napt install pandoc         # Ubuntu\n\n# Basic conversion\npandoc contract.md -o contract.docx \\\n  --reference-doc=reference.docx \\\n  -V geometry:margin=1in\n\n# With numbered sections (legal style)\npandoc contract.md -o contract.docx \\\n  --number-sections \\\n  -V documentclass=article \\\n  -V fontsize=11pt\n\n# With custom company template\npandoc contract.md -o contract.docx \\\n  --reference-doc=company-template.docx\n```\n\n---\n\n## Jurisdiction Notes\n\n### US (Delaware)\n- Governing law: State of Delaware\n- Work-for-hire doctrine applies (Copyright Act 101)\n- Arbitration: AAA Commercial Rules\n- Non-compete: enforceable with reasonable scope\u002Ftime\n\n### EU (GDPR)\n- Must include Data Processing Addendum if handling personal data\n- IP assignment requires separate written deed in some member states\n- Arbitration: ICC or local chamber\n\n### UK (post-Brexit)\n- Governed by English law\n- IP: Patents Act 1977 \u002F CDPA 1988\n- Arbitration: LCIA Rules\n- Data: UK GDPR (post-Brexit equivalent)\n\n### DACH (Germany \u002F Austria \u002F Switzerland)\n- BGB (Buergerliches Gesetzbuch) governs contracts\n- Written form requirement for certain clauses (para 126 BGB)\n- IP: Author always retains moral rights; must explicitly transfer Nutzungsrechte\n- Non-competes: max 2 years, compensation required (para 74 HGB)\n- Jurisdiction: German courts (Landgericht) or DIS arbitration\n- DSGVO (GDPR implementation) mandatory for personal data processing\n- Kuendigungsfristen: statutory notice periods apply\n\n---\n\n## Template A: Web Dev Fixed-Price Contract\n\n```markdown\n# SOFTWARE DEVELOPMENT AGREEMENT\n\n**Effective Date:** [DATE]\n**Client:** [CLIENT LEGAL NAME], [ADDRESS] (\"Client\")\n**Developer:** [YOUR LEGAL NAME \u002F COMPANY], [ADDRESS] (\"Developer\")\n\n---\n\n## 1. SERVICES\n\nDeveloper agrees to design, develop, and deliver:\n\n**Project:** [PROJECT NAME]\n**Description:** [1-3 sentence scope]\n\n**Deliverables:**\n- [Deliverable 1] due [DATE]\n- [Deliverable 2] due [DATE]\n- [Deliverable 3] due [DATE]\n\n## 2. PAYMENT\n\n**Total Fee:** [CURRENCY] [AMOUNT]\n\n| Milestone | Amount | Due |\n|-----------|--------|-----|\n| Contract signing | 50% | Upon execution |\n| Beta delivery | 25% | [DATE] |\n| Final acceptance | 25% | Within 5 days of acceptance |\n\nLate payments accrue interest at 1.5% per month.\nClient has [10] business days to accept or reject deliverables in writing.\n\n## 3. INTELLECTUAL PROPERTY\n\nUpon receipt of full payment, Developer assigns all right, title, and interest in the\nWork Product to Client as a work made for hire (US) \u002F by assignment of future copyright (EU\u002FUK).\n\nDeveloper retains the right to display Work Product in portfolio unless Client\nrequests confidentiality in writing within [30] days of delivery.\n\nPre-existing IP (tools, libraries, frameworks) remains Developer's property.\nDeveloper grants Client a perpetual, royalty-free license to use pre-existing IP\nas embedded in the Work Product.\n\n## 4. CONFIDENTIALITY\n\nEach party keeps confidential all non-public information received from the other.\nThis obligation survives termination for [3] years.\n\n## 5. WARRANTIES\n\nDeveloper warrants Work Product will substantially conform to specifications for\n[90] days post-delivery. Developer will fix material defects at no charge during\nthis period. EXCEPT AS STATED, WORK PRODUCT IS PROVIDED \"AS IS.\"\n\n## 6. LIABILITY\n\nDeveloper's total liability shall not exceed total fees paid under this Agreement.\nNeither party liable for indirect, incidental, or consequential damages.\n\n## 7. TERMINATION\n\nFor Cause: Either party may terminate if the other materially breaches and fails\nto cure within [14] days of written notice.\n\nFor Convenience: Client may terminate with [30] days written notice and pay for\nall work completed plus [10%] of remaining contract value.\n\n## 8. DISPUTE RESOLUTION\n\nUS: Binding arbitration under AAA Commercial Rules, [CITY], Delaware law.\nEU\u002FDACH: ICC \u002F DIS arbitration, [CITY]. German \u002F English law.\nUK: LCIA Rules, London. English law.\n\n## 9. GENERAL\n\n- Entire Agreement: Supersedes all prior discussions.\n- Amendments: Must be in writing, signed by both parties.\n- Independent Contractor: Developer is not an employee of Client.\n\n---\n\nCLIENT: _________________________ Date: _________\n[CLIENT NAME], [TITLE]\n\nDEVELOPER: _________________________ Date: _________\n[YOUR NAME], [TITLE]\n```\n\n---\n\n## Template B: Monthly Consulting Retainer\n\n```markdown\n# CONSULTING RETAINER AGREEMENT\n\n**Effective Date:** [DATE]\n**Client:** [CLIENT LEGAL NAME] (\"Client\")\n**Consultant:** [YOUR NAME \u002F COMPANY] (\"Consultant\")\n\n---\n\n## 1. SERVICES\n\nConsultant provides [DOMAIN, e.g., \"CTO advisory and technical architecture\"] services.\n\n**Monthly Hours:** Up to [X] hours\u002Fmonth\n**Rollover:** Unused hours [do \u002F do not] roll over (max [X] hours banked)\n**Overflow Rate:** [CURRENCY] [RATE]\u002Fhr for hours exceeding retainer\n\n## 2. FEES\n\n**Monthly Retainer:** [CURRENCY] [AMOUNT], due on the 1st of each month.\n**Payment Method:** Bank transfer \u002F Stripe \u002F SEPA direct debit\n**Late Payment:** 2% monthly interest after [10]-day grace period.\n\n## 3. TERM AND TERMINATION\n\n**Initial Term:** [3] months starting [DATE]\n**Renewal:** Auto-renews monthly unless either party gives [30] days written notice.\n**Immediate termination:** For material breach uncured after [7] days notice.\n\nOn termination, Consultant delivers all work in progress within [5] business days.\n\n## 4. INTELLECTUAL PROPERTY\n\nWork product created under this Agreement belongs to [Client \u002F Consultant \u002F jointly].\nAdvisory output (recommendations, analyses) are Client property upon full payment.\n\n## 5. EXCLUSIVITY\n\n[OPTION A - Non-exclusive:]\nThis Agreement is non-exclusive. Consultant may work with other clients.\n\n[OPTION B - Partial exclusivity:]\nConsultant will not work with direct competitors of Client during the term\nand [90] days thereafter.\n\n## 6. CONFIDENTIALITY AND DATA PROTECTION\n\nEU\u002FDACH: If Consultant processes personal data on behalf of Client, the parties\nshall execute a Data Processing Agreement (DPA) per Art. 28 GDPR.\n\n## 7. LIABILITY\n\nConsultant's aggregate liability is capped at [3x] the fees paid in the [3] months\npreceding the claim.\n\n---\n\nSignatures as above.\n```\n\n---\n\n## Template C: SaaS Partnership Agreement\n\n```markdown\n# SAAS PARTNERSHIP AGREEMENT\n\n**Effective Date:** [DATE]\n**Provider:** [NAME], [ADDRESS]\n**Partner:** [NAME], [ADDRESS]\n\n---\n\n## 1. PURPOSE\n\nProvider grants Partner [reseller \u002F referral \u002F white-label \u002F integration] rights to\nProvider's [PRODUCT NAME] (\"Software\") subject to this Agreement.\n\n## 2. PARTNERSHIP TYPE\n\n[ ] Referral: Partner refers customers; earns [X%] of first-year ARR per referral.\n[ ] Reseller: Partner resells licenses; earns [X%] discount off list price.\n[ ] White-label: Partner rebrands Software; pays [AMOUNT]\u002Fmonth platform fee.\n[ ] Integration: Partner integrates Software via API; terms in Exhibit A.\n\n## 3. REVENUE SHARE\n\n| Tier | Monthly ARR Referred | Commission |\n|------|---------------------|------------|\n| Bronze | \u003C $10,000 | [X]% |\n| Silver | $10,000-$50,000 | [X]% |\n| Gold | > $50,000 | [X]% |\n\nPayout: Net-30 after month close, minimum $[500] threshold.\n\n## 4. INTELLECTUAL PROPERTY\n\nEach party retains all IP in its own products. No implied licenses.\nPartner may use Provider's marks per Provider's Brand Guidelines (Exhibit B).\n\n## 5. DATA AND PRIVACY\n\nEach party is an independent data controller for its own customers.\nJoint processing requires a separate DPA (Exhibit C - EU\u002FDACH projects).\n\n## 6. TERM\n\nInitial: [12] months. Renews annually unless [90]-day written notice given.\nTermination for Cause: [30]-day cure period for material breach.\n\n## 7. LIMITATION OF LIABILITY\n\nEach party's liability capped at [1x] fees paid\u002Freceived in prior [12] months.\nMutual indemnification for IP infringement claims from own products.\n\n---\n\nSignatures, exhibits, and governing law per applicable jurisdiction.\n```\n\n---\n\n## GDPR Data Processing Addendum (EU\u002FDACH Clause Block)\n\n```markdown\n## DATA PROCESSING ADDENDUM (Art. 28 GDPR)\n\nController: [CLIENT NAME]\nProcessor: [CONTRACTOR NAME]\n\n### Subject Matter\nProcessor processes personal data on behalf of Controller solely to perform services\nunder the main Agreement.\n\n### Categories of Data Subjects\n[e.g., end users, employees, customers]\n\n### Categories of Personal Data\n[e.g., names, email addresses, usage data]\n\n### Processing Duration\nFor the term of the main Agreement; deletion within [30] days of termination.\n\n### Processor Obligations\n- Process data only on Controller's documented instructions\n- Ensure persons authorized to process have committed to confidentiality\n- Implement technical and organizational measures per Art. 32 GDPR\n- Assist Controller with data subject rights requests\n- Not engage sub-processors without prior written consent\n- Delete or return all personal data upon termination\n\n### Sub-processors (current as of Effective Date)\n| Sub-processor | Location | Purpose |\n|--------------|----------|---------|\n| [AWS \u002F GCP \u002F Azure] | [Region] | Cloud hosting |\n| [Other] | [Location] | [Purpose] |\n\n### Cross-border Transfers\nData transfers outside EEA covered by: [ ] SCCs  [ ] Adequacy Decision  [ ] BCRs\n```\n\n---\n\n## Common Pitfalls\n\n1. **Missing IP assignment language** - \"work for hire\" alone is insufficient in EU; need explicit assignment of Nutzungsrechte in DACH\n2. **Vague acceptance criteria** - Always define what \"accepted\" means (written sign-off, X days to reject)\n3. **No change order process** - Scope creep kills fixed-price projects; add a clause for out-of-scope work\n4. **Jurisdiction mismatch** - Choosing Delaware law for a German-only project creates enforcement problems\n5. **Missing limitation of liability** - Without a cap, one bug could mean unlimited damages\n6. **Oral amendments** - Contracts modified verbally are hard to enforce; always require written amendments\n\n---\n\n## Best Practices\n\n- Use **milestone payments** over net-30 for projects >$10K - reduces cash flow risk\n- For EU\u002FDACH: always check if a DPA is needed (any personal data = yes)\n- For DACH: include a **Schriftformklausel** (written form clause) explicitly\n- Add a **force majeure** clause for anything over 3 months\n- For retainers: define response time SLAs (e.g., 4h urgent \u002F 24h normal)\n- Keep templates in version control; track changes with `git diff`\n- Review annually - laws change, especially GDPR enforcement interpretations\n- For NDAs: always specify the return\u002Fdestruction of confidential materials on termination\n",{"name":5,"description":7},"claude\u002Fopen-prs-review-Of9HK","a48d8438efe8e36550acc4c2006bdcddf62911db","business-growth\u002Fskills\u002Fcontract-and-proposal-writer","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002Faneeba-pixel","Student at University of Gujrat","2026-07-14 21:41:17",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add aneeba-pixel\u002Fclaude-skills --skill contract-and-proposal-writer",{"tool":37,"command":38},"bunx","bunx skills add aneeba-pixel\u002Fclaude-skills --skill contract-and-proposal-writer",{"tool":40,"command":41},"pnpm","pnpm dlx skills add aneeba-pixel\u002Fclaude-skills --skill contract-and-proposal-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fbusiness-growth\u002Fskills\u002Fcontract-and-proposal-writer\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M78K120A3JKH3NH8GC19YG4M","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M78K0QS9AGDJ43CPQYEHM5S0","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M78K0FV3HMJ94SK965CWMNNP","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M78K04E77B04KYBB6M01EV3J","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M78JZW8XEFZP6HSF53M8D4M1","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M78JZHX45S2Y0GPY9Z5V6TQ3","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002Faneeba-pixel\u002Fclaude-skills\u002Fblob\u002Fclaude\u002Fopen-prs-review-Of9HK\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]