Agency setup

Apply ../00-lead-generation-guardrails/SKILL.md first. Nothing this skill provisions sends a message to anyone, so no recipient, channel, or jurisdiction resolution happens here — but every downstream skill that eventually sends from infrastructure this skill provisions still owes that resolution before it sends.

Scope: the agency's own identity, not the sending domain

This skill provisions the agency's own first-party business identity: the domain a prospect looks up to check the agency is a real business, the business email address a prospect replies to or a contract references, and a landing page a proposal or cold-email footer can link to. This is deliberately narrow and deliberately separate from skill 04's secondary cold-email sending domain(s) and mailboxes — mixing the two defeats the reason 04's chain exists in the first place: a secondary sending domain absorbs deliverability risk from cold volume so the agency's own domain, email, and reputation stay clean. Never provision the agency's own domain as a cold-email sending domain, and never treat this skill's output as satisfying skill 04's requirements.

What this skill covers

Three independent capability abstractions, each provisioned separately:

• domain_registration — the agency's own domain name.
• business_email — a mailbox on that domain the agency actually uses for its own correspondence (proposals, contracts, replies), not a sending-volume mailbox.
• landing_page_hosting — a simple page a proposal, signature block, or cold-email footer can point to, hosted at (or behind) the agency's own domain.

None of these three capabilities implies or requires the others from the same provider — a domain registrar, a business-email provider, and a landing-page host are three separate provider selections, not one bundled purchase.

Provider selection: capability match, never a hardcoded name