casemark/incorporator-written-consent
skills/legal/incorporator-written-consent/SKILL.md
Drafts an Action by Written Consent of Incorporator for newly formed U.S. corporations. Trigger when the user needs to formalize post-incorporation organizational actions (adopting bylaws, appointing initial directors) by written consent in lieu of an organizational meeting.
$ install --global
skillsauthnpx skillsauth add casemark/skills incorporator-written-consentInstall 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: Apr 4, 2026, 3:43 AM102.3s1 file scanned
SKILL.md
- name:
- incorporator-written-consent
- description:
- >-
Action by Written Consent of Incorporator
Formalizes the incorporator's organizational actions after Articles of Incorporation are filed, transferring authority to the initial board of directors.
Required Inputs
- Corporation legal name — must match Articles exactly
- State of incorporation — determines statutory citation
- Articles filing date — date filed with Secretary of State
- Incorporator name(s) — full legal name of each incorporator
- Initial director names — full legal names of all appointees
- Bylaws — attach as Exhibit A or note if pending
Quick Start
- Collect all required inputs above.
- Identify the governing statute for the state (see State Variance below).
- Draft per the output structure; include optional resolutions only if client requests.
- Attach bylaws as Exhibit A or add placeholder.
- Replace all bracketed placeholders before delivery.
Output Structure
Header — Title with corporation name and effective date.
Preamble — Identifies incorporator, corporation name, state, and Articles filing date.
Resolutions (numbered):
| # | Action | Notes | |---|--------|-------| | 1 | Adopt Bylaws | "RESOLVED, that the Bylaws attached hereto as Exhibit A are hereby adopted…" | | 2 | Appoint Initial Directors | List each director by full legal name; serve until successors elected and qualified | | 3 | (Optional) Set fiscal year | Calendar year or specified end date | | 4 | (Optional) Authorize bank accounts | Name designated institutions | | 5 | (Optional) Ratify prior acts | Ratify actions taken before this consent |
Role Conclusion — Explicit statement that incorporator duties are complete and authority transfers to the board.
Execution Block — Signature line for each incorporator with printed name and title "Incorporator."
Exhibit A — Executed bylaws or placeholder if pending.
State Variance
- Delaware: DGCL § 108
- California: Corp. Code § 210
- MBCA states: MBCA § 2.05 (most other states)
- Default: When state is unspecified, draft to MBCA standards
- Always verify the specific statutory citation for the target state
Checks
- Corporation name, state, and filing date must be consistent throughout and match the filed Articles
- Director count must comply with minimums/maximums in Articles or state statute
- Multiple incorporators: all must sign unless statute or Articles permit majority action
- Notarization is typically not required; flag if state law mandates it
- Remind client: executed consent goes into corporate minute book with Bylaws and Articles
- Never deliver with unfilled bracketed placeholders
Related Skills
casemark/skills/legal/automated-contract-summary
development
VerifiedTrustedCommunity
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
21SKILL.mdUpdated May 26, 2026
casemark/obligation-mapping
tools
VerifiedTrustedCommunity
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
21SKILL.mdUpdated May 25, 2026
casemark/horizon-scanning
development
VerifiedTrustedCommunity
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
21SKILL.mdUpdated May 25, 2026
casemark/gap-analysis
testing
VerifiedTrustedCommunity
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.
21SKILL.mdUpdated May 25, 2026