[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DBMEGDK6TNXPE3TE7SC8EX":3,"skill-same:01M6DBMEGDK6TNXPE3TE7SC8EX":97},{"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":28,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6DBMEGDK6TNXPE3TE7SC8EX","global-think-tank-analyst",null,"Strategic-risk analysis skill for AI agents producing decision-ready memos on geopolitics, sanctions, trade, regulation, and strategic risk with explicit evidence boundaries, uncertainty, scenarios, actor incentives, trade-offs, and watch-next indicators. Use for a country risk brief, policy memo, sanctions or export-control exposure assessment, trade or regulatory implications memo, geopolitical scenario brief, strategic implications note for leadership, stakeholder and incentives analysis, a red-team challenge to an existing policy or risk view, or a decision briefing pack for founders, operators, investors, NGOs, compliance teams, policy teams, or leadership. Do not use for a simple news recap, encyclopedia-style overview, academic literature review, legal advice, intelligence-style certainty, decorative analysis, or unsupported quantitative forecasting.","vassiliylakhonin\u002Fglobal-think-tank-analyst","vassiliylakhonin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260414237?v=4","01M6DBKD7AP8ZEAA2ZMYP2XMJ2","Vassiliy Lakhonin","01M6DBKDBKWNP9EM6X52DPXHXK",7,"MIT","https:\u002F\u002Fgithub.com\u002Fvassiliylakhonin\u002Fglobal-think-tank-analyst\u002Fblob\u002Fmain\u002Fsrc\u002Fgtta\u002Fskills\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"think tank","global","global think tank analyst","think","analyst","do","trade-offs","for","incentives","investors","literature","strategic risk","scenario","watch","operators","news","policy","legal","ready","use","view","challenge","team","brief","assessment","2026-11-10 10:12:30",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":59,"description":60},"contract-and-proposal-writer","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.","main","510dd2917e051cc953dc55f56fd6ef442aa01b38","src\u002Fgtta\u002Fskills",2,"https:\u002F\u002Fgithub.com\u002Fvassiliylakhonin\u002Fglobal-think-tank-analyst","https:\u002F\u002Fgithub.com\u002Fvassiliylakhonin\u002Fglobal-think-tank-analyst\u002Fblob\u002Fmain\u002FSKILL.md","https:\u002F\u002Fgithub.com\u002Fvassiliylakhonin","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fvassiliy-lakhonin\u002F","Building tools that help AI agents verify evidence, respect permissions, and get human approval before acting.","2026-11-10 01:49:46",{"source":8,"skillName":59,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add vassiliylakhonin\u002Fglobal-think-tank-analyst --skill contract-and-proposal-writer",{"tool":77,"command":78},"bunx","bunx skills add vassiliylakhonin\u002Fglobal-think-tank-analyst --skill contract-and-proposal-writer",{"tool":80,"command":81},"pnpm","pnpm dlx skills add vassiliylakhonin\u002Fglobal-think-tank-analyst --skill contract-and-proposal-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvassiliylakhonin\u002Fglobal-think-tank-analyst\u002Fblob\u002Fmain\u002Fsrc\u002Fgtta\u002Fskills\u002FSKILL.md",true,[85,91],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"__init__.py","SCRIPT","脚本",65,"https:\u002F\u002Fgithub.com\u002Fvassiliylakhonin\u002Fglobal-think-tank-analyst\u002Fblob\u002Fmain\u002Fsrc\u002Fgtta\u002Fskills\u002F__init__.py",{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"SKILL_RU.md","REFERENCE","参考文档",54397,"https:\u002F\u002Fgithub.com\u002Fvassiliylakhonin\u002Fglobal-think-tank-analyst\u002Fblob\u002Fmain\u002Fsrc\u002Fgtta\u002Fskills\u002FSKILL_RU.md",[98,104,119],{"skillNo":99,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":103,"publishedAt":54},"01M6DBMC3B4JJH1T0XYCZBR5WZ","https:\u002F\u002Fgithub.com\u002Fvassiliylakhonin\u002Fglobal-think-tank-analyst\u002Fblob\u002Fmain\u002Fskills\u002Fglobal-think-tank-analyst\u002FSKILL.md",[102],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[31,29,30,32,33],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":112,"publishedAt":54},"01M6DBM7W2YA6T681HZWX8808X","policy-risk-memo-architect-codex","Codex-ready strategic-risk analysis skill for AI agents producing decision-ready memos on geopolitics, sanctions, trade, regulation, and strategic risk with explicit evidence boundaries, uncertainty, scenarios, actor incentives, trade-offs, and watch-next indicators. Use for a country risk brief, policy memo, sanctions or export-control exposure assessment, trade or regulatory implications memo, geopolitical scenario brief, strategic implications note for leadership, stakeholder and incentives analysis, a red-team challenge to an existing policy or risk view, or a decision briefing pack for founders, operators, investors, NGOs, compliance teams, policy teams, or leadership. Do not use for a simple news recap, encyclopedia-style overview, academic literature review, legal advice, intelligence-style certainty, decorative analysis, or unsupported quantitative forecasting.","https:\u002F\u002Fgithub.com\u002Fvassiliylakhonin\u002Fglobal-think-tank-analyst\u002Fblob\u002Fmain\u002Fcodex\u002FSKILL.md",[110,111],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[113,114,45,115,116,117,53,50,49,48,118,47,46,34,44,43,42,41,40,39,38,37,35,51,52],"memo","codex","policy risk memo architect codex","risk","architect","decision",{"skillNo":120,"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":121,"sourceHtmlUrl":66,"categories":122,"keywords":125,"publishedAt":54},"01M6DBKGDMVBEWEY9FB5S0Y75H","https:\u002F\u002Fgithub.com\u002Fvassiliylakhonin\u002Fglobal-think-tank-analyst\u002Fblob\u002Fmain\u002FLICENSE",[123,124],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[31,33,32,30,29,43,53,52,51,118,50,49,48,47,46,34,44,42,41,40,39,38,37,36,35,45]]