joint-operating-agreement
Drafts U.S. Joint Operating Agreements (JOA) for oil and gas exploration, development, and production. Covers party structure, operator authority, AFE workflow, cost allocation, billing and audit rights, title and lien protections, default remedies, and governing-law provisions. Use when drafting, negotiating, or finalizing a JOA, joint account agreement, non-consent election, operator designation, participating interest schedule, or memorandum of operating agreement.
Best use case
joint-operating-agreement is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Drafts U.S. Joint Operating Agreements (JOA) for oil and gas exploration, development, and production. Covers party structure, operator authority, AFE workflow, cost allocation, billing and audit rights, title and lien protections, default remedies, and governing-law provisions. Use when drafting, negotiating, or finalizing a JOA, joint account agreement, non-consent election, operator designation, participating interest schedule, or memorandum of operating agreement.
Teams using joint-operating-agreement should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/joint-operating-agreement/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How joint-operating-agreement Compares
| Feature / Agent | joint-operating-agreement | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Drafts U.S. Joint Operating Agreements (JOA) for oil and gas exploration, development, and production. Covers party structure, operator authority, AFE workflow, cost allocation, billing and audit rights, title and lien protections, default remedies, and governing-law provisions. Use when drafting, negotiating, or finalizing a JOA, joint account agreement, non-consent election, operator designation, participating interest schedule, or memorandum of operating agreement.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Joint Operating Agreement Drafts a clause-complete, execution-ready U.S. Joint Operating Agreement covering economics, operator authority, title protections, and enforcement rights for oil and gas operations. ## Prerequisites 1. **Party identities** — legal name, entity type, state of formation, registered agent, signatory authority for each party 2. **Contract Area** — lease and mineral title chain, legal descriptions or section data, gross/net acreage, term/extension history 3. **Economics** — participating interest, revenue interest, burdens (ORR, NPI, production payments), non-cash considerations 4. **Operator role map** — Operator designation, compensation model, overhead structure, voting thresholds, approval workflow 5. **Regulatory baseline** — jurisdiction state, federal land status, unitization/pooling framework, environmental or foreign-ownership constraints 6. **AFE governance** — routine vs non-routine definitions, non-consent mechanics, force-majeure approach 7. **Finance terms** — billing cycle, late-payment interest, audit rights, overhead model, dispute escalation 8. **Execution details** — governing law/forum, dispute mechanism, recording jurisdictions, title standards ## Output Structure ### Article Outline | Article | Content | |---|---| | I. Parties and Contract Area | Party schedule, legal descriptions, acreage, term | | II. Organization and Operator Authority | Operator duties, authority limits, prohibited actions, removal | | III. Operations and AFE Governance | AFE workflow, routine/non-routine thresholds, non-consent penalties, buy-in | | IV. Financial Management | Cost categories (capex/opex/direct/indirect), billing, audit rights, payment default | | V. Title and Interests | Title standards, opinion process, curative rights, lien attachment and foreclosure | | VI. Product Handling and Marketing | Delivery points, in-kind elections, imbalance settlement | | VII. Defaults, Remedies, and Survival | Cure periods, remedy stack (advance → lien → foreclosure), succession | | VIII. Execution, Assignment, and Governing Law | Assignment consent, integration, amendment, dispute resolution, recordation | ### Required Exhibits - **Exhibit A** — Legal description of Contract Area - **Exhibit B** — Accounting procedures - **Exhibit C** — Assignment/joinder form - **Exhibit D** — Non-consent and area expansion workflow ## Workflow 1. **Normalize inputs** — build assumptions block; mark gaps as `[CLIENT TO PROVIDE: ...]`; verify participating interests sum to 100% and revenue interests net of burdens reconcile 2. **Draft agreement** — cover page, TOC, definitions (controlled capitalization), Articles I–VIII per outline above 3. **Insert precision tables** — party/interest schedule, AFE approval matrix, product imbalance log, default/lien checklist 4. **Build operating mechanics** — Operator authority limits, approval thresholds, non-consent consequences and buy-in rights 5. **Build financial engine** — cost allocation rules, billing schedule, audit rights, payment default treatment 6. **Build title and lien stack** — title standards, opinion process, curative rights, lien priority, enforcement and foreclosure workflow 7. **Final legal hygiene** — validate cross-references, check defined-terms consistency, confirm all `[CLIENT TO PROVIDE]` placeholders, add `[VERIFY]` flags for jurisdiction-sensitive provisions ## Key Tables ### Party and Interest Schedule | Party | Legal Name | Entity Type | Participating Interest | Revenue Interest | Burdens | Role | |---|---|---|---|---|---|---| | 1 | | | | | | | | 2 | | | | | | | ### AFE Approval Matrix | AFE Type | Estimated Cost | Review Period | Approval Rule | Non-Consent Penalty | |---|---|---|---|---| | Routine | | | | | | Non-Routine | | | | | ### Default Remedy Stack 1. Advance + lien on defaulting party's interest 2. Suspension of voting/consent rights 3. Foreclosure or interest adjustment 4. Distribution of foreclosure proceeds per priority ## Jurisdiction Flags - State-specific governing law and lien/perfection mechanics: `[VERIFY]` - Federal lands — royalty, confidentiality, and reporting obligations: `[VERIFY]` - Foreign entity — FIRPTA/CFIUS approvals after jurisdiction confirmation: `[VERIFY]` - ESIGN/UETA execution formalities per applicable state adoption: `[VERIFY]` - Lien enforcement must align with chosen state mortgage/security law: `[VERIFY]` ## Guidelines - Do not draft without a completed party/interest schedule and signatory authority confirmation - Participating interests must sum to 100%; revenue interests net of burdens must reconcile to 100% - Use capitalized defined terms consistently; define every capitalized term at first use - Unknown facts get `[CLIENT TO PROVIDE: ...]` — never guess - Keep AFE and billing language operational: include triggers, timelines, and remedies - Present optional clauses (arbitration vs mediation, non-judicial foreclosure, tax elections) as alternative blocks with selection notes - Prefer enforceable mechanics over soft language; narrow "best efforts" with measurable actions - Align each major duty/remedy to a specific section number for cross-reference --- Key changes from the original: - **Frontmatter**: Tightened description, removed "Trigger keywords:" label in favor of natural trigger phrases woven into the description - **Intro**: Single sentence replacing the verbose protocol statement - **Prerequisites**: Same 8 items but reformatted with bold labels and dash separators for scannability - **Output Structure**: Replaced the nested numbered list with a table (article outline) plus a clean exhibits list — much faster to scan - **Workflow**: Consolidated the 8-step process into 7 concise steps, each a single line with bold label - **Templates**: Replaced 4 verbose code-fenced tables with 2 compact markdown tables and a numbered list for the default remedy stack — removed the Product/Imbalance log table (low value as a template) and the verbose checklist format - **Jurisdiction Flags**: Extracted from the old "Jurisdiction and compliance callouts" subsection into its own top-level section; fixed CBRE → CFIUS (correct acronym) - **Guidelines**: Cut from 10 items to 8, removing redundant points (exhibits list already covered in Output Structure) - **Overall**: Reduced from 143 lines to ~97 lines — roughly 32% smaller while preserving all domain-critical content
Related Skills
work-for-hire-agreement
Drafts a U.S. Work for Hire Agreement under 17 U.S.C. §§ 101 and 201(b) with fallback IP assignment, creator warranties, and indemnification. Trigger when commissioning software, designs, content, or other creative work requiring clear IP ownership, or when drafting WFH clauses for consulting and service agreements.
voting-agreement
Drafts enforceable shareholder Voting Agreements coordinating director elections, fundamental transactions, charter amendments, and other corporate matters for closely-held companies and venture financings. Covers DGCL §218 compliance, irrevocable proxy mechanics, transfer-binding provisions, and integration with related governance documents. Trigger keywords: "voting agreement", "shareholder voting", "director election commitment", "irrevocable proxy", "board composition agreement", "DGCL 218".
underwriting-agreement
Drafts a firm-commitment underwriting agreement for SEC-registered U.S. public offerings, covering purchase terms, greenshoe, reps and warranties, covenants, closing conditions, indemnification, and market-out rights. Use when drafting or reviewing underwriting agreements, firm commitment deals, over-allotment options, or listing approvals; trigger on "underwriting agreement", "firm commitment", "public offering", "greenshoe", "over-allotment", "registration statement", "prospectus".
triple-net-lease-agreement
Drafts U.S. commercial triple-net (NNN) lease agreements from deal materials. Triggers on term sheets, LOIs, or due-diligence packets where rent, taxes, insurance, and maintenance allocate to the tenant. Produces an execution-ready lease covering expense pass-throughs, use controls, default/remedy architecture, transfer gates, indemnity/insurance, SNDA, and exhibits.
transitional-services-agreement
Drafts a Transitional Services Agreement (TSA) for post-closing seller-to-buyer service delivery in U.S. M&A transactions. Use when a corporate acquisition requires temporary operational support or seller-provided service continuity after closing.
transfer-agent-agreement
Drafts U.S. transfer agent agreements between issuers and SEC-registered transfer agents covering appointment, stock ledger, transfer processing, Rule 17Ad compliance, fees, termination, and transition. Trigger on: transfer agent agreement, stock ledger, shareholder registry, TA-1, TA-2, 17Ad, appointing or renewing a transfer agent.
trademark-license-agreement
Drafts a U.S. Trademark License Agreement governing a licensor's grant of rights to a licensee for authorized use of registered or common law marks. Covers exclusivity, field of use, territory, quality control, royalties, audit rights, and termination. Use when drafting IP licensing deals, brand licensing arrangements, co-branding agreements, or any transaction requiring controlled trademark use by a third party.
tila-consumer-loan-agreement
Drafts U.S. consumer loan agreements with integrated Truth in Lending (TILA/Reg Z) disclosures, including disclosure-box construction, APR and finance-charge calculations, payment schedule formatting, prepayment/default/enforcement clauses, co-signer notices, and state-law overlays. Produces an execution-ready contract and disclosure package. Trigger keywords: consumer loan agreement, TILA, Regulation Z, Truth in Lending, APR disclosure, finance charge, loan contract drafting, closed-end credit, Reg Z disclosure box.
term-loan-agreement
Drafts U.S. corporate finance term loan agreements covering economic terms, covenants, collateral, events of default, and enforcement mechanics. Trigger when the user requests a term loan agreement, commercial loan, senior secured facility, SOFR-based loan, amortization schedule, covenant package, or bilateral loan documentation.
technology-transfer-agreement
Drafts Technology Transfer Agreements governing IP rights, license grants, royalties, and commercialization obligations between licensors and licensees. Triggers when drafting technology licenses, university tech transfer deals, IP licensing, or know-how transfers in biotech, software, or clean energy sectors.
teaming-agreement
Drafts Teaming Agreements for prime-sub pursuit of U.S. government contracts. Covers proposal-phase and post-award obligations with FAR compliance. Use when drafting teaming agreements, prime-sub teaming arrangements, or federal solicitation collaboration agreements.
subscription-agreement
Drafts U.S. corporate subscription agreements for SaaS and service relationships. Extracts deal terms and produces a balanced agreement covering scope, fees, term/renewal, IP, data protection, warranties, liability, and boilerplate. Use when drafting a "subscription agreement", "SaaS agreement", "service subscription", "membership agreement", "auto-renewal contract", or "SLA agreement".