casemark/interconnection-agreement
skills/legal/interconnection-agreement/SKILL.md
Drafts U.S. telecommunications Interconnection Agreements (ICAs) under 47 U.S.C. §§ 251-252 and FCC Part 51, covering POIs, traffic classification, reciprocal compensation, access charges, LNP, E911, signaling, and dispute resolution. Use when drafting or revising an ICA, negotiating Section 251/252 terms, defining POI/transport arrangements, structuring ILEC/CLEC or VoIP interconnection, or preparing state PUC filings.
$ install --global
skillsauthnpx skillsauth add casemark/skills interconnection-agreementInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Aug 8, 2026, 4:39 AM371.3s1 file scanned
SKILL.md
- name:
- interconnection-agreement
- language:
- en
- description:
- >-
Interconnection Agreement
Drafts a complete ICA suitable for execution and state PUC filing under the Communications Act framework.
Quick Start
Gather before drafting:
- Parties — Legal names, entity types, FCC FRNs, carrier classification (ILEC/CLEC/CMRS/VoIP)
- Scope — Geographic area, traffic types, desired POIs, interconnection method (direct/indirect), anticipated volumes
- Technical — Switch locations, interface standards, signaling (SS7/SIP), LNP/CNAM/E911 needs
- Commercial — Rate elements, billing format, payment terms, existing tariffs/commission orders
- Regulatory — Section 252 status, filing jurisdiction(s), prior ICA or arbitration history
Agreement Structure
| Section | Content | |---|---| | Title + Effective Date | Agreement name; execution/approval effective date clause | | Parties + Recitals | Legal names, carrier types, FRNs, statutory basis (47 U.S.C. § 251/252) [VERIFY] | | Definitions | See Key Definitions below | | Interconnection | POI details, transport/trunking, technical specs, signaling, testing | | Traffic Classification | Local, intraLATA, interLATA, wireless, VoIP — definitions and billing treatment | | Numbering + Databases | LNP procedures, CNAM, routing, NPAC access | | E911 | PSAP routing, ANI/ALI responsibilities, priority handling | | Performance | KPIs (ASR/NER/PND), thresholds, remediation | | Rates + Billing | Rate tables, invoices, records, audits, disputes | | Term + Termination | Initial term, renewal, termination for cause/convenience, transition | | Dispute Resolution | Tiered process — regulatory vs commercial paths | | Regulatory Compliance | FCC/state law, filing/approval mechanics, change-in-law | | Standard Terms | Confidentiality, indemnity, liability limits, force majeure, notices, assignment | | Signatures | Authorized signatories, optional notary, e-signatures |
Key Definitions
Define each term precisely:
| Term | Requirements | |---|---| | Point of Interconnection (POI) | Physical address, logical demarcation, meet-point vs end office vs tandem, interface standard (DS-1/DS-3/OC-x/Ethernet) | | Local Traffic | Origination/termination within local calling area; cite tariff/PUC designation | | IntraLATA Toll / InterLATA | Within-LATA outside local area / crosses LATA boundary | | Wireless Traffic | CMRS-originated/terminated; classification method | | VoIP Traffic | IP-enabled voice; jurisdictional treatment and interim compensation | | UNEs / Interconnection Facilities | Distinguish § 251(c)(3) vs § 251(c)(2) [VERIFY] | | Transport / Tandem / End Office | Technical definitions tied to network topology | | Busy Hour / CCS / MOU / PIU / PLU | Measurement and apportionment terms | | Reciprocal Compensation | § 251(b)(5) obligation [VERIFY] |
Technical Specs Checklist
- [ ] POI inventory: address, floor/bay/cage, equipment IDs
- [ ] Trunking: one-way/two-way, initial capacity, augmentation thresholds
- [ ] Signaling: SS7 point codes or SIP profile + headers
- [ ] Testing: ATIS/TIA protocols, acceptance criteria
- [ ] Forecasts: cadence and format for traffic projections
- [ ] Performance reporting: ASR/NER/PND metrics and remedies
Rate and Billing Tables
Populate three rate schedules:
A. Reciprocal Compensation — Traffic type, rate, symmetric/asymmetric, jurisdictional basis
B. Transport / Tandem / Entrance Facilities — Element, NRC, MRC, order interval
C. Access Charges — Traffic type, tariff/rate reference, conditions
Billing workflow: specify invoice timing/format (EMR/EDI/CSV), records retention and audit rights, dispute window, and undisputed-amount payment terms.
Dispute Resolution Ladder
| Stage | Timeframe | Scope | |---|---|---| | Operational Negotiation | X business days | Technical/billing issues | | Executive Escalation | X days | Unresolved operational disputes | | Mediation | X days | Non-binding commercial disputes | | Regulatory Complaint | As needed | § 251/252 compliance, rates, traffic classification | | Arbitration | Final step | Purely commercial contract disputes |
Regulatory Filing
- Filing deadline after execution: [VERIFY]
- Effective date: execution vs PUC approval vs filing
- PUC rejection: amendment process and interim performance obligations
Pitfalls and Checks
- Never invent rates, POIs, FRNs, or regulatory approvals — use placeholders if missing
- Tie traffic classification to specific jurisdictional rules and tariffs; flag VoIP treatment uncertainty
- Cite federal framework: Communications Act §§ 251-252 and 47 C.F.R. Part 51 [VERIFY]
- Include "continue to perform" during disputes to prevent service disruption
- Add jurisdiction addendum for known state PUC rules; otherwise include a state-law non-preemption clause
- Use defined terms consistently; verify all internal cross-references
- Move POIs, technical specs, and rate tables to exhibits when the agreement exceeds 10 pages
Related Skills
casemark/medical-records-gap-analysis
tools
VerifiedTrustedCommunity
Audits the complete in-scope medical-record universe in a litigation matter and produces an attorney-facing, Bates-cited analysis of treatment gaps, missing records or providers, baseline coverage, material billing or production mismatches, and complaint evolution. Use when asked to find missing medical records, analyze treatment gaps or first-care timing, identify absent providers, assess whether a production is complete, or prepare a records-request target list. Use medical-record-chronology instead when the primary request is a chronological clinical narrative.
40SKILL.mdUpdated Sep 3, 2026
casemark/private-placement-memo
development
VerifiedTrustedCommunity
Drafts a legally compliant Private Placement Memorandum for Regulation D offerings (Rule 506(b)/506(c)), covering full disclosure framework including risk factors, capitalization, securities terms, use of proceeds, and investor qualification requirements. Enforces SEC anti-fraud compliance under Section 10(b)/Rule 10b-5, blue sky law considerations, and accredited investor verification under Rule 501. Use this skill when drafting PPMs, offering memorandums, Reg D disclosure documents, or private offering circulars for issuers raising capital from sophisticated investors. Also trigger when the user mentions private placement disclosure, offering memorandum, Reg D fundraising, or accredited investor verification. Even if the user just says "PPM" or "draft our offering memo," use this skill.
40SKILL.mdUpdated Apr 17, 2026
casemark/privacy-law-updates
data-ai
VerifiedTrustedCommunity
Generates structured privacy and data protection law briefings across US, EU, UK, and other jurisdictions. Organizes by jurisdiction with compliance deadlines, enforcement actions, and legislative changes. Use when preparing privacy law briefings, compliance updates, regulatory change summaries, or data protection landscape reviews.
40SKILL.mdUpdated Apr 17, 2026
casemark/prior-art-summary
testing
VerifiedTrustedCommunity
Generates structured summaries of prior art references for patent prosecution, validity analysis, and freedom-to-operate assessments. Maps disclosures to claim elements with precise citations. Use when summarizing prior art, analyzing patent landscapes, mapping references to claims, or preparing office action responses.
40SKILL.mdUpdated Apr 17, 2026