An officer's closing certificate should separately address each applicable bring-down standard, use the company's actual officer titles, confirm that any good-standing evidence is current under the transaction agreement, and verify that board authorization timing is consistent with the certification date.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill draft-officers-closing-certificate --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Draft Officers Closing Certificate?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-draft-officers-closing-certificate)More formats (shields.io, HTML) on the badges page.
---
name: ecvc-draft-officers-closing-certificate
task_id: emerging-companies-venture-capital/draft-officers-closing-certificate
description: An officer's closing certificate should separately address each applicable bring-down standard, use the company's actual officer titles, confirm that any good-standing evidence is current under the transaction agreement, and verify that board authorization timing is consistent with the certification date.
activates_for: [planner, solver, checker]
---
# Skill: Draft Officers' Closing Certificate
## 2. Failure modes the skill is correcting
- The certificate collapses distinct bring-down standards into one blended statement instead of tracking each standard the financing documents require.
- The certificate uses placeholder or inferred officer titles rather than the signatories’ actual corporate titles.
- The certificate cites good-standing evidence without checking that the evidence is dated within the contractual freshness window.
- The certificate treats board approval as effective without aligning the approval method and timing to the certification date.
- The closing package is incomplete because the draft certificate is prepared without a companion issue-spotting memo that explains any qualification or unresolved closing item.
## 3. Legal frameworks / domain conventions that apply
- Follow the exact bring-down mechanics in the financing agreement and related closing documents; draft separate certification prongs for each distinct standard instead of merging them.
- Use the company’s actual officer titles as shown in organizational records and signing authority materials.
- Confirm current good standing by reference to the evidence’s date, the governing certificate’s freshness requirement, and the applicable jurisdiction’s issuance practice.
- Confirm board authorization under the governing corporate statute and the company’s constitutional documents, including whether approval was by meeting or written consent and whether it remained effective as of signing.
- Align all closing certifications with the signing date and closing date so the certificate does not imply facts that were not yet true.
- If the source materials identify controlling authority for a representation, condition, or signing requirement, cite it by name and section in the certificate notes or issues memo.
## 4. Analytical scaffolds
- Identify every closing certification topic the transaction documents require, then map each topic to its own paragraph and standard.
- For each paragraph, check whether the certificate should state knowledge-qualified, absolute, or bring-down language based on the governing document.
- Verify the signatories’ actual titles, names, and authority path before drafting signature blocks.
- Review the good-standing evidence against the contractual timing requirement and flag any stale or mismatched evidence.
- Review board approvals, written consents, and officer resolutions for timing, form, and consistency with the certification date.
- Where the source set presents more than one relevant closing condition, treat each as a separate item in the analysis rather than using a representative sample.
- If an issue remains open, capture it in the memo with the legal basis, the affected closing condition, and the practical consequence for closing.
## 5. Vertical / structural / temporal relationships
- Separate the certificate’s factual attestations from the memo’s issue discussion; do not embed open-ended analysis inside the certificate text.
- Keep the sequence of the closing package aligned: executed certificate first, issues memo second, and any supporting exhibits referenced consistently by name.
- Match temporal references carefully: board action date, good-standing issuance date, signing date, and closing date must not be used interchangeably.
- If multiple officers sign, ensure each signature block corresponds to an actual office and that the certification language supports all signatories.
- If any exhibit is referenced, the exhibit description should make clear what it proves and when it was issued.
## 6. Output structure conventions
- Draft the closing certificate as a standalone transaction document with numbered certification paragraphs.
- Use separate paragraphs for each distinct bring-down standard and any separate corporate authorization or status confirmations.
- Include a signature block using the officers’ actual titles.
- Include an exhibit or schedule reference for board authorization and good-standing evidence where those items are relied on.
- Prepare a separate closing issues memo that identifies each unresolved or qualification-worthy item, states why it matters to closing, and gives a concise recommended next step.
- In the memo, use an explicit severity scale applied consistently across issues, and state the basis for each severity in one line.
- End the memo with an actionable recommendations section that assigns the next step to the relevant officer, counsel, or business lead and ties it to the closing timeline.
- Ensure the primary document is fully drafted and ready for execution before treating the memo as complete.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!