Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Written Consent Of Incorporator

ASecurity

Drafts a U.S. corporate Action by Written Consent of Incorporator for post-formation organizational actions (adopting bylaws, appointing directors, transitioning authority to board). Use when the prompt mentions "written consent," "incorporator," "formation filing," "adopt bylaws," "appoint initial directors," or "organize corporation."

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
documentationgoaws

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill written-consent-of-incorporator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Written Consent Of Incorporator?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Written Consent Of Incorporator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-written-consent-of-incorporator/badge)](https://www.skillsdirectory.com/skills/lev-os-written-consent-of-incorporator)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: written-consent-of-incorporator
description: Drafts a U.S. corporate Action by Written Consent of Incorporator for post-formation organizational actions (adopting bylaws, appointing directors, transitioning authority to board). Use when the prompt mentions "written consent," "incorporator," "formation filing," "adopt bylaws," "appoint initial directors," or "organize corporation."
tags:
  - agreement
  - corporate
  - drafting
---

# Action by Written Consent of Incorporator

Generates an execution-ready incorporator written-consent resolution for post-formation organizational actions and minute-book filing.

## Required Inputs

Collect before drafting:

1. Corporation legal name (must match Articles exactly)
2. State of incorporation
3. Articles of Incorporation filing date
4. Incorporator(s) full legal name(s)
5. Initial directors' full legal names
6. Bylaws text or instruction to attach separately
7. Any nonstandard actions (bank authorization, fiscal year, stock issuance, etc.)
8. Whether multiple incorporators consent jointly

## Quick Start

1. Validate all inputs against formation documents.
2. Draft the consent using the structure below.
3. Run quality checks before delivering.

## Document Structure

Draft sections in this order:

1. **Title**: `ACTION BY WRITTEN CONSENT OF INCORPORATOR of [Corporation Name], a [State] Corporation`
2. **Preamble**: Identify incorporator(s), cite corporation name/state/filing date, state purpose under applicable corporation law.
3. **Resolutions** (numbered):
   - Adopt bylaws (reference as Exhibit A or note separate attachment)
   - Appoint/elect initial directors
   - Additional organizational actions only if requested
4. **Transition clause**: Incorporator confirms completion of duties; authority transfers to board.
5. **Execution block**: Minute-book filing instruction, signature line per incorporator (printed name / title / date).

### Template

```text
ACTION BY WRITTEN CONSENT OF INCORPORATOR
of [Corporation Name], a [State] Corporation

[Effective Date]

The undersigned [sole incorporator / incorporators], [name(s)],
hereby adopt this written consent on behalf of [Corporation Name],
a [State] corporation, pursuant to filing of its Articles of
Incorporation on [Filing Date].

RESOLVED THAT:
1. [Adopt Bylaws as Exhibit A ...]
2. [The following persons are appointed as initial directors: ...]
3. [Additional organizational action(s) as requested.]

RESOLVED FURTHER THAT the undersigned incorporator(s) has completed
all acts of an incorporator and all authority is transferred to the
board of directors.

Executed this [Date].

_________________________________
[Incorporator Printed Name]   Signature
```

## Quality Checks

- [ ] No bracketed placeholders remain
- [ ] Corporation name, state, filing date, incorporator identity consistent throughout
- [ ] Director count aligns with charter/state requirements
- [ ] Numbered resolutions, clear headings, execution-ready format

## Pitfalls

- **Multiple incorporators**: Use a separate subsection to clarify consent authority per incorporator.
- **Jurisdiction gaps**: Tag unconfirmed state-specific rules with `[VERIFY]`. Default to MBCA-style conventions but check governing state law.
- **Statutory neutrality**: Keep language generic unless a specific state rule is provided.
- **Notarization**: Usually not required for written consent; flag if jurisdiction or filing office requires it.
- **No legal advice**: Draft the governance instrument only — never imply attorney-client advice.

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Caveman Help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

1023330 votes

How It Works

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".

929660 votes
View all in documentation →