# Draft License Renewal Submission > Agents produce renewal packages that address required disclosures of prior non-compliances with a corrective-action narrative, include biographical affidavit requirements for newly appointed officers and directors, and frame adverse financial ratios in a way that supports regulator review of solvency and operational condition. - Skill: `finchipaiorg/draft-license-renewal-submission` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/draft-license-renewal-submission` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/draft-license-renewal-submission/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/draft-license-renewal-submission --- # Skill: State Insurance License Renewal Submission Package ## 1. Subject-matter triage - Treat the filing as a renewal-package drafting exercise, not a pure legal memo. - Identify the jurisdiction, license type, renewal cycle, filing deadline, and the exact agency to which the package is addressed. - Confirm whether the source set contains the current renewal form, supplemental schedules, signatures, exhibits, and any jurisdiction-specific certification language. - Separate mandatory filing components from explanatory attachments; do not assume a cover letter can substitute for a required form or schedule. - If the source set spans multiple reporting periods or multiple entities, enumerate each period or entity first and draft to each one separately. ## 2. Failure modes the skill is correcting - The package omits a required component of the renewal submission and leaves the filing facially incomplete. - The package gives a blanket compliance certification even though the source documents show prior non-compliance that requires disclosure and a corrective-action narrative. - The package omits biographical affidavits or equivalent disclosures for officers or directors added since the prior renewal. - The narrative ignores financial-condition facts that regulators expect to see explained, including adverse underwriting or capital signals. - The draft cites regulatory identifiers, order numbers, permit numbers, or docket references incorrectly, undermining credibility. - The package fails to disclose a material cybersecurity event or other operational incident that the source documents show must be addressed. - The submission reads like a generic form-fill rather than a regulator-facing package that anticipates review questions and answers them cleanly. ## 3. Legal frameworks / domain conventions that apply - **Renewal filing mechanics:** State insurance departments commonly require a cover letter, application narrative, certification, and supporting exhibits; each item should be complete on its own terms. - **Compliance certification:** If any prior non-compliance appears in the source set, the certification should not be drafted as an unqualified blanket statement; it should track the disclosed exception and corrective steps under the applicable renewal instructions or department form. - **Biographical disclosure requirements:** Newly appointed or elected officers and directors are often subject to biographical affidavits or equivalent personal-history forms under state licensing rules or department instructions. - **Solvency and operational condition review:** A renewal narrative should address capital adequacy, underwriting performance, reserve posture, and other indicators the regulator may use in evaluating fitness to continue licensure. - **Ratio-based supervision conventions:** Combined ratio, premium-to-surplus ratio, and similar indicators should be presented only if supported by the source documents and tied to the applicable regulatory concern threshold or supervisory expectation. - **Cyber incident disclosure:** Where the source documents show a material cybersecurity incident during the renewal period, the filing should include a concise disclosure and remediation summary consistent with the department’s instructions and applicable state insurance cybersecurity requirements. - **Accuracy of cited authorities and identifiers:** Any cited statute, regulation, order, permit, or filing reference should be checked against the source set before it is reproduced in the package. ## 4. Analytical scaffolds - **Package completeness check:** List every document the renewal instructions or source materials call for; confirm whether each is present, current, signed if required, and internally consistent. - **New-personnel inventory:** Identify every officer or director added since the prior renewal; verify whether a biography form, affidavit, or equivalent disclosure is required for each; flag any omission. - **Non-compliance mapping:** Pull every prior non-compliance, deficiency, late filing, or regulator comment from the source documents; match each to a corrective action, current status, and residual risk. - **Authority and reference verification:** Check all cited regulatory references, order numbers, form numbers, filing numbers, and similar identifiers for internal consistency and transcription accuracy. - **Financial-condition narrative:** Translate the financial statements into regulator-facing prose that addresses performance trends, capital structure, and operational developments without overclaiming or inventing unsupported metrics. - **Incident-disclosure review:** Scan the source set for cybersecurity events, control failures, or other operational incidents that require disclosure or contextual explanation; draft the disclosure only if the source supports it. - **One-issue-one-pass rule:** If more than one officer, incident, non-compliance, period, or entity is implicated, handle each separately rather than merging them into a single generic narrative. ## 5. Vertical / structural / temporal relationships - Tie each narrative section to the renewal period at issue and avoid drifting into prior periods unless the prior period is needed to explain a continuing condition. - Distinguish between historical events, current conditions, and forward-looking remediation so the regulator can see what has been fixed and what remains open. - When describing related items, preserve their hierarchy: filing instructions first, then required forms, then explanatory narrative, then supporting exhibits. - If a ratio, trend, or incident appears in more than one source document, reconcile the sources before drafting and use the most authoritative version available. - Where a disclosure depends on a changed role or appointment date, anchor the obligation to the date of appointment or election and the relevant renewal cycle. - When multiple documents reference the same fact differently, do not average them; identify the controlling source and note the discrepancy for client review. ## 6. Output structure conventions - **Renewal cover letter:** Address the correct state insurance commissioner or department official; identify the insurer, license, renewal period, and a clean enclosure list. - **Renewal application narrative:** Provide a regulator-facing summary of business operations, organizational changes, governance changes, new officers and directors, prior non-compliances with corrective actions, and relevant financial developments. - **Compliance certification:** Use the form language required by the source materials; if prior non-compliance exists, include the required disclosure and corrective-action schedule rather than a bare certification. - **Supporting biographies / affidavits:** Include the required biographical materials for every newly appointed officer or director identified in the source set. - **Counsel memorandum to client:** Flag open items, verification gaps, inconsistent references, and any pre-submission fixes needed before filing. - Keep the package internally consistent: names, dates, titles, license numbers, renewal periods, and cited references must match across all documents. - Draft in a tone that is concise, factual, and regulator-ready; avoid advocacy that sounds argumentative or speculative. - If a required item cannot be confirmed from the source documents, state the gap plainly and mark it for client follow-up rather than guessing.