@myapihq/cli 2.4.0 → 2.4.2

package/dist/skills/my-audience-api/SKILL.md

@@ -0,0 +1,139 @@
+---
+name: my-audience-api
+version: 1.0.0
+description: >
+  Saved audiences = named Goldfox-filter snapshots over the people or company database. Build a target list once, name it, reuse it across campaigns, refresh to re-evaluate against current data. The persistence layer on top of my-people-api + my-company-api.
+triggers: [audience, segment, target list, saved filter, goldfox, lead list, abm list, refresh, members, prospect database]
+checksum: sha256-5d9a2731d587c476eff2955241001fecb8481bbc5e567f06b8e9e76a079eda92
+---
+
+# MyAudienceAPI
+
+A saved audience is a **named filter snapshot** over the Goldfox people or company database. Instead of repeating the same filter every time you run a campaign, save it once, reference the audience by id, and call `refresh` to re-evaluate against current data when the underlying dataset grows.
+
+## Capabilities
+<!-- llm:start -->
+Use when:
+
+- You'll target the same kind of list across multiple campaigns
+- You want a stable id to feed into email campaigns, workflows, or external tools
+- You need to know how many candidates match a filter without paging the whole result
+- You want to refresh a list as new rows are added to the Goldfox crawl
+
+Each audience has:
+- `name` and optional `description`
+- `source` — `"people"` or `"company"` (which database to filter against)
+- `filter` — the canonical Goldfox filter (same shape as `my-people-api` / `my-company-api`)
+- `member_count` — computed when filter is created or refreshed
+- An `id` for retrieving members, refreshing, deleting
+
+**Filter contract** (full Goldfox shape):
+
+```json
+{
+  "confidence":           ["high"],
+  "country":              ["US", "DE"],
+  "country_consistent":   true,
+  "seniority":            ["c_level", "vp_director"],   // people-source only
+  "email_type":           ["corporate"],                // people-source only
+  "tld_class":            ["cctld"],
+  "has_c_level":          true,
+  "has_decision_maker":   true,
+  "has_careers_page":     true,
+  "has_investors_page":   false,
+  "has_shop_page":        false,
+  "is_registered_entity": true,
+  "min_headcount":        5,
+  "min_source_count":     3,
+  "min_link_confidence":  0.8,                          // people-source only
+  "keyword":              "platform",
+  "limit":                100,
+  "offset":               0
+}
+```
+
+OR within an array; AND across fields. Empty filter = all rows with `confidence=high` (Goldfox's curated default tier).
+
+Allowed values:
+- **confidence**: `high` (default) / `low` / `very_low`
+- **seniority** (people only): `c_level`, `vp_director`, `manager`, `senior_ic`, `ic`
+- **email_type** (people only): `corporate`, `freemail`, `role_based`, `other_corporate`
+- **tld_class**: `cctld`, `generic`, `vanity`, `low_trust`, `other`
+- **country**: ISO 3166-1 alpha-2
+
+**Member fetch:** the response shape is `{ total, limit, offset, has_more, people?: […], companies?: […] }` — only one of `people` / `companies` is populated based on the audience's source. Use `--offset` to paginate.
+
+**Refresh delta:** `audience refresh` returns `{ total, previous, delta, refreshed_at }` — detect newly-matched rows.
+<!-- llm:end -->
+
+## Commands
+<!-- generated:start -->
+| Command | What it does |
+|---|---|
+| `myapi audience create <name> --source <people\|company> --filter '<json>' [--description <text>]` | Save a Goldfox filter as a named audience; returns id + initial member_count |
+| `myapi audience list` | List all audiences in the org |
+| `myapi audience get <id>` | Single audience (name, filter, member_count, timestamps) |
+| `myapi audience update <id> [--name <x>] [--description <y>] [--filter '<json>']` | Patch name/description/filter; member_count re-evaluates if filter changes |
+| `myapi audience delete <id>` | Remove an audience |
+| `myapi audience members <id> [--limit N] [--offset N]` | Paged member snapshot (people or companies depending on source) |
+| `myapi audience refresh <id>` | Re-evaluate filter against current data; returns delta vs previous count |
+<!-- generated:end -->
+
+## Examples
+<!-- llm:start -->
+```bash
+# 1. Create the audience
+AID=$(myapi audience create "EU decision makers w/ corporate emails" \
+  --source people \
+  --filter '{"seniority":["c_level","vp_director"],"country":["DE","FR","GB"],"email_type":["corporate"]}' \
+  --json | jq -r .id)
+
+# 2. Inspect members
+myapi audience members $AID --limit 20
+
+# 3. Refresh after new Goldfox data lands
+myapi audience refresh $AID
+# → Refreshed. 1247 → 1289 (+42)
+
+# 4. Update filter without losing the id
+myapi audience update $AID \
+  --filter '{"seniority":["c_level","vp_director"],"country":["DE","FR","GB","NL"],"email_type":["corporate"]}'
+
+# 5. Delete when done
+myapi audience delete $AID
+```
+
+### End-to-end recipe — outbound campaign driven by an audience
+
+```bash
+# Build with quality controls — definitive links + registered companies + careers signal
+AID=$(myapi audience create "EU growth-stage decision makers" \
+  --source people \
+  --filter '{"seniority":["c_level","vp_director"],"country":["DE","FR","GB"],"email_type":["corporate"],"min_link_confidence":0.9,"has_careers_page":true,"is_registered_entity":true}' \
+  --json | jq -r .id)
+
+# Pull all members as JSON
+myapi audience members $AID --limit 100 --json > targets.json
+
+# (later) Re-check before next batch
+myapi audience refresh $AID
+```
+
+### Company-source audience (ABM)
+
+```bash
+myapi audience create "EU growth-stage SaaS accounts" \
+  --source company \
+  --filter '{"country":["DE","FR","GB","NL"],"has_careers_page":true,"has_decision_maker":true,"is_registered_entity":true,"min_source_count":3}'
+```
+<!-- llm:end -->
+
+## Notes
+
+- The underlying dataset is the **Goldfox crawl** — multi-million-row corporate data with provenance signals. Defaults to `confidence=high` which is the curated tier.
+- `audience refresh` is cheap and idempotent; call it before any campaign run that depends on a current list.
+- `update --filter` REPLACES the whole filter (not merged). To shift one field, fetch the audience, merge in code, then update.
+- Audiences are per-org. Two orgs can have audiences with the same name; ids are globally unique.
+- Look before you delete: confirm the target with `myapi audience get <id>`, pass `--org` explicitly; delete verbs require `--yes` in non-interactive runs.
+
+Run `myapi audience --help` for full flag reference.

package/dist/skills/my-audience-api/claude/.claude-plugin/plugin.json

@@ -0,0 +1,7 @@
+{
+  "name": "my-audience-api",
+  "description": "Saved audiences = named filter snapshots over people/company database. Reuse across campaigns; refresh re-evaluates against current data.",
+  "version": "1.0.0",
+  "status": "preview",
+  "published": true
+}

package/dist/skills/my-auth-api/SKILL.md

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   Add authentication to apps you build on MyAPI — a managed OIDC identity provider for your app's END USERS (à la Kinde/Auth0). One auth tenant per org; register OIDC clients; sign users in with managed Google or the hosted login page; verify RS256 tokens against the tenant JWKS.
 triggers: [auth, authentication, login, sign-in, oidc, oauth, jwt, jwks, sso, google sign-in, user accounts, identity provider, kinde, auth0, clerk]
-checksum: sha256-pending
+checksum: sha256-11dac8e8da70bd6bbf63fe11fae5adc038584dc23a09350b9e7b977a669aed41
 ---
 
 # MyAuthAPI

package/dist/skills/my-auth-api/claude/.claude-plugin/plugin.json

@@ -2,5 +2,6 @@
   "name": "my-auth-api",
   "description": "Managed OIDC identity provider for the end users of apps built on MyAPI. Per-org auth tenant + OIDC clients, RS256/JWKS, hosted login, managed Google sign-in. A Kinde alternative.",
   "version": "1.0.0",
+  "status": "ga",
   "published": true
 }

package/dist/skills/my-company-api/README.md

@@ -0,0 +1,35 @@
+---
+# my-company-api
+
+Queryable company database for account-based targeting and B2B firmographics. Search companies by industry, size, country, revenue, or keyword.
+
+## What it does
+
+- Filter the company database by attributes (industry, employee_bucket, revenue_bucket, country, ...)
+- Fetch a single company, optionally with embedded people for one-call enrichment
+- Feed results into `my-audience-api` to save reusable account lists
+- Complement `my-people-api` for combined account-based + contact-based targeting
+
+## Quickstart
+
+```bash
+# Find target companies
+myapi company search --industry fintech --country GB,DE --employee-bucket 51-200
+
+# Single company with embedded people
+myapi company get company_06 --include-people 5
+```
+
+## Authentication
+
+```bash
+export MYAPI_KEY=mak_...
+```
+
+Requires `api_key` and `org_id` from **myapihq**.
+
+## Documentation
+
+Full filter contract and audience integration: see `SKILL.md`.
+
+Run `myapi company --help` for inline reference.

package/dist/skills/my-company-api/SKILL.md

@@ -0,0 +1,110 @@
+---
+name: my-company-api
+version: 1.0.0
+description: >
+  Company database backed by the Goldfox crawl. Filter companies by Goldfox confidence tier, country/TLD consistency, behavioral page signals (has_careers_page, has_investors_page, has_shop_page, has_c_level, has_decision_maker), legal-entity status, headcount, and source-URL count. Account-based targeting and B2B firmographics.
+triggers: [companies, accounts, firmographics, abm, search, filter, goldfox, careers signal, investors, c-level, shop, b2b targeting]
+checksum: sha256-67dd4b65a9b0cc7acf7c1e4262bc66d2b58ff11ed227a24299924e0b620712f0
+---
+
+# MyCompanyAPI
+
+A queryable company database for account-based targeting and B2B firmographics, sourced from the **Goldfox** crawl. Filter by confidence tier, country consistency, behavioral page signals, and quality thresholds — get back companies with rich signal data (headcount estimates, source count, careers/investors/shop presence, legal-entity flag).
+
+## Capabilities
+<!-- llm:start -->
+Use when:
+
+- Doing account-based targeting (pick companies first, find decision-makers second)
+- Researching market segments by behavioral signals ("companies in DE with a careers page AND a c-level present")
+- Combining with `my-audience-api` to save a company filter as a reusable audience
+
+Filter contract — shared with `my-people-api` and the `filter` field of `my-audience-api`, minus people-only fields (`seniority`, `email_type`, `min_link_confidence`). OR within an array; AND across fields. **Empty filter = all rows with default confidence=high.**
+
+```json
+{
+  "confidence":           ["high"],
+  "country":              ["US", "DE"],
+  "country_consistent":   true,
+  "tld_class":            ["cctld"],
+  "has_c_level":          true,
+  "has_decision_maker":   true,
+  "has_careers_page":     true,
+  "has_investors_page":   false,
+  "has_shop_page":        false,
+  "is_registered_entity": true,
+  "min_headcount":        5,
+  "min_source_count":     3,
+  "keyword":              "platform",
+  "include_people":       3,
+  "limit":                100,
+  "offset":               0
+}
+```
+
+Allowed values:
+- **confidence**: `high` (default) / `low` / `very_low`
+- **tld_class**: `cctld`, `generic`, `vanity`, `low_trust`, `other`
+- **country**: ISO 3166-1 alpha-2; consensus across TLD + address + phone
+- **keyword**: substring match on the company's domain
+- **include_people**: 0–10; embed up to N people per company in the result
+
+Behavioral signals (booleans):
+- `has_c_level` — row has ≥1 person with seniority = c_level
+- `has_decision_maker` — row has ≥1 person with seniority ∈ (c_level, vp_director)
+- `has_careers_page` — `/careers`, `/jobs`, `/stellen`, `/karriere` etc. (growth-stage proxy)
+- `has_investors_page` — `/investors`, `/ir/` (mature/public proxy)
+- `has_shop_page` — `/shop`, `/store`, `/products`, `/cart` (e-commerce proxy)
+- `is_registered_entity` — name has a recognized legal suffix (GmbH/Ltd/Inc/SARL/…)
+- `country_consistent` — TLD + address + phone all agree on country (highest-trust geo)
+<!-- llm:end -->
+
+## Commands
+<!-- generated:start -->
+| Command | What it does |
+|---|---|
+| `myapi company search [--confidence <csv>] [--country <csv>] [--country-consistent] [--tld-class <csv>] [--has-c-level] [--has-decision-maker] [--has-careers-page] [--has-investors-page] [--has-shop-page] [--is-registered-entity] [--keyword <text>] [--min-headcount N] [--min-source-count N] [--include-people N] [--limit N] [--offset N]` | Filter companies; returns id/domain/name/country/confidence/headcount/sources/signals table |
+| `myapi company get <company_id> [--include-people N]` | Get a single company, optionally with embedded people |
+<!-- generated:end -->
+
+The `signals` column in the search table compactly shows which behavioral booleans are true (e.g. `c-level,dm,careers`).
+
+## Examples
+<!-- llm:start -->
+```bash
+# 1. Registered DE companies with a careers page (growth signal)
+myapi company search --country DE --is-registered-entity --has-careers-page --limit 20
+
+# 2. E-commerce in FR/IT — companies with shop pages
+myapi company search --country FR,IT --has-shop-page --confidence high
+
+# 3. High-source-count companies (more validated rows) with embedded people
+myapi company search --min-source-count 5 --include-people 3 --json | jq '.companies[0]'
+
+# 4. Single company with up to 5 embedded people
+myapi company get auroracloud.com --include-people 5
+```
+
+### End-to-end recipe — ABM target account list
+
+```bash
+# Save filter as audience (companies)
+AID=$(myapi audience create "EU growth-stage SaaS" \
+  --source company \
+  --filter '{"country":["DE","FR","GB","NL"],"has_careers_page":true,"has_decision_maker":true,"min_source_count":3}' \
+  --json | jq -r .id)
+
+# Pull members for outreach planning
+myapi audience members $AID --limit 50 --json > accounts.json
+```
+<!-- llm:end -->
+
+## Notes
+
+- Goldfox confidence tiers matter: `high` (default) is the curated 96.4% of rows; widen with `low` only for spot-check work, and `very_low` rows usually get dropped.
+- `seniority`, `email_type`, and `min_link_confidence` are people-only — passing them on company search is silently ignored.
+- `include_people` only works on company search/get; people-source already embeds company by default.
+- `keyword` is a substring match on the company's **domain** — use `--keyword stripe` to find domains containing "stripe".
+- For a persistent account list, use `my-audience-api` with `--source company`.
+
+Run `myapi company --help` for full flag reference.

package/dist/skills/my-company-api/claude/.claude-plugin/plugin.json

@@ -0,0 +1,7 @@
+{
+  "name": "my-company-api",
+  "description": "Company database backed by the Goldfox crawl. Filter companies by confidence tier, country/TLD consistency, behavioral page signals (has_careers_page, has_investors_page, has_shop_page, has_c_level, has_decision_maker), legal-entity status, headcount, and source-URL count.",
+  "version": "1.0.0",
+  "status": "preview",
+  "published": true
+}

package/dist/skills/my-container-api/README.md

@@ -0,0 +1,34 @@
+---
+# my-container-api
+
+Run containers on demand — long-running services, background workers, and scheduled jobs. The heavier-duty sibling of edge functions, for native dependencies, long execution, and full dynamic apps.
+
+## What it does
+
+- Register a container and get a scoped API key (delivered to the runtime as `MYAPI_KEY`)
+- Deploy a pre-built image to managed cloud infrastructure
+- Three types: `service` (HTTP, scales to zero), `worker` (always-on), `job` (runs to completion, cron-capable)
+- **Bind a custom domain** — serve a dynamic app at `app.yourbrand.com` over HTTPS
+- Recent runtime logs
+
+## Quickstart
+
+```bash
+myapi container create --name api --type service --port 8080
+myapi container deploy <id> registry.example.com/my-app:v1
+myapi container domain <id> app.yourbrand.com
+```
+
+## Authentication
+
+```bash
+export MYAPI_KEY=mak_...
+```
+
+Requires `api_key` + `org_id` from **myapihq**. Custom domains require the parent domain registered via **mydomainapi**.
+
+## Documentation
+
+Full command reference, the custom-domain rules, and the container/funnel/function split: see `SKILL.md`.
+
+Run `myapi container --help` for inline reference.

package/dist/skills/my-container-api/SKILL.md

@@ -0,0 +1,77 @@
+---
+name: my-container-api
+version: 1.0.0
+description: >
+  Run containers on demand — long-running services, background workers, and scheduled jobs. The heavier-duty sibling of edge functions, for native deps and long execution.
+triggers: [container, cloud run, dynamic app, custom domain app, service, worker, scheduled job, deploy container, docker image]
+checksum: sha256-ce30765b31f9c29012dcfc13b538cf47bb90e21bc015b4cfc75c1e55b21b4d75
+---
+
+# MyContainerAPI
+
+A container runs a pre-built image on managed cloud infrastructure. Three types: a **service** (HTTP server, scales to zero), a **worker** (always-on background process), or a **job** (runs to completion — the only type that takes a cron schedule). Containers are the heavier-duty sibling of edge functions (`myapi fn`) — use them for native dependencies, long execution, or a full dynamic app.
+
+## Capabilities
+<!-- llm:start -->
+The lifecycle is **create → deploy → (optionally) bind a custom domain**.
+
+- `create` registers the container and issues a **scoped API key**, returned once. The running container receives it as the `MYAPI_KEY` env var, so your code calls other MyAPI slots with no token handling. Deploy rotates this key.
+- `deploy` ships a pre-built image reference to the runtime and makes the container live at a generated URL.
+- `domain` puts the container on a **custom domain** — how you serve a dynamic app at `app.yourbrand.com`.
+
+### Custom domains (dynamic apps)
+
+`myapi container domain <id> <domain>` binds a custom domain to a **deployed** container, served over HTTPS automatically. This is the path for a dynamic backend on a real domain — distinct from `my-funnel-api`, which serves static sites.
+
+Get it right:
+
+- **Deploy first.** Binding a domain to a container that has never deployed fails (422) — there is nothing running to route to.
+- **Register the parent domain first.** The domain's MyAPI-managed parent must already be registered via `my-domain-api`. Binding `app.synthesisdaily.com` requires `synthesisdaily.com` registered in MyAPI; otherwise 422.
+- **One domain per container.** Re-binding, or binding a hostname already taken, fails (409).
+- `--remove` unbinds. `myapi container get <id>` shows the bound `custom_domain`.
+<!-- llm:end -->
+
+## Commands
+<!-- generated:start -->
+| Command | What it does |
+|---|---|
+| `myapi container create --name <name> [--type service\|worker\|job] [--cron <expr>] [--cpu <n>] [--memory <size>] [--port <n>] [--env K=V,...]` | Register a container, get its scoped API key (once) |
+| `myapi container deploy <id> <image-ref>` | Ship a pre-built image and go live (rotates the scoped key) |
+| `myapi container list` | List containers in your org |
+| `myapi container get <id>` | Inspect a container (status, URL, custom domain) |
+| `myapi container logs <id> [--tail <n>]` | Recent runtime logs, newest first |
+| `myapi container domain <id> <domain>` | Bind a custom domain (`--remove` to unbind) |
+| `myapi container delete <id>` | Soft-delete and revoke its scoped API key |
+<!-- generated:end -->
+
+## Examples
+<!-- llm:start -->
+```bash
+# 1. Register a service container
+myapi container create --name api --type service --port 8080
+# → prints a scoped API key ONCE — save it if your code needs it
+
+# 2. Deploy a pre-built image
+myapi container deploy <id> registry.example.com/my-app:v1
+
+# 3. Serve it on a custom domain. The parent domain must already be
+#    registered: myapi domain register synthesisdaily.com
+myapi container domain <id> app.synthesisdaily.com
+# → app.synthesisdaily.com now serves the container over HTTPS
+
+myapi container get <id>          # shows status, URL, custom_domain
+myapi container logs <id> --tail 100
+
+# Unbind the custom domain
+myapi container domain <id> --remove
+```
+<!-- llm:end -->
+
+## Notes
+
+- The scoped API key is shown **once** at create, and again (rotated) on every deploy. Save it if your code needs it.
+- A `worker` is forced to ≥1 instance; a `service` scales to zero; only a `job` accepts `--cron`.
+- Custom domains need a deployed container **and** a MyAPI-registered parent domain — see `my-domain-api`.
+- Containers are for dynamic apps and native deps. For static sites use `my-funnel-api`; for edge functions use `my-function-api`.
+
+Run `myapi container --help` for the full flag reference.

package/dist/skills/my-container-api/claude/.claude-plugin/plugin.json

@@ -0,0 +1,7 @@
+{
+  "name": "my-container-api",
+  "description": "Run containers on demand — long-running services, background workers, and scheduled jobs. The heavier-duty sibling of edge functions, for native deps and long execution.",
+  "version": "1.0.0",
+  "status": "preview",
+  "published": true
+}

package/dist/skills/my-crm-api/SKILL.md

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   The canonical store of engaged contacts + companies for an org. Auto-ingests from inbound webhooks via a configurable dot-path. Fixed lifecycle_stage enum (cold | warm | qualified | customer | churned). Append-only event timeline with reserved kinds. Soft delete + restore. Promote-from-Goldfox closes the discovery → engagement loop.
 triggers: [crm, contact, company, lead, engagement, pipeline, lifecycle, qualified, customer, webhook ingest, promote]
-checksum: sha256-pending
+checksum: sha256-0ee12d579c51b300ff227a094c2082a2c6f3bf83d2d97ab16cb2f47ad3667fd6
 ---
 
 # MyCRMAPI
@@ -69,11 +69,11 @@ If a contact doesn't exist for the matched email, it's auto-created with `source
 
 ### Goldfox enrichment (deferred)
 
-A CRM contact promoted from Goldfox carries a `goldfox_person_id` reference. In v2 the GET response will join to Goldfox live, embedding the latest row inline as `goldfox_person`. Today that field is null until the BQ get-by-id helper lands. Search filters that hit Goldfox-only fields are not yet wired into CRM search.
+A contact promoted from Goldfox carries a `goldfox_person_id`. In v2 the GET response will join live, embedding the row as `goldfox_person`; today that field is null. Goldfox-only fields are not yet filterable in CRM search.
 
 ### Search filter — re-engagement semantics
 
-`--max-last-engagement-days N` returns contacts last engaged *more than* N days ago. This intentionally **includes contacts with no engagement at all** (promoted-but-never-emailed Goldfox leads), because those are exactly the natural targets of a re-engagement campaign. If you want to distinguish "never tried" from "tried and went cold," layer `--source goldfox` (never engaged after promotion) or post-filter the JSON.
+`--max-last-engagement-days N` returns contacts last engaged *more than* N days ago, and intentionally **includes contacts with no engagement at all** (promoted-but-never-emailed Goldfox leads) — the natural targets of a re-engagement campaign. To separate "never tried" from "tried and went cold," layer `--source goldfox` or post-filter the JSON.
 
 ### Failure modes
 

package/dist/skills/my-crm-api/claude/.claude-plugin/plugin.json

@@ -2,5 +2,6 @@
   "name": "my-crm-api",
   "description": "The canonical store of engaged people + companies. Auto-ingest from inbound webhooks (configurable dot-path). Fixed lifecycle_stage enum, soft delete, event timeline.",
   "version": "1.0.0",
+  "status": "ga",
   "published": true
 }

package/dist/skills/my-database-api/SKILL.md

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   Per-org KV store with named namespaces, JSON values up to 256 KB, prefix-scan listing, and compare-and-swap via etag. The substrate for any stateful agent-built app on MyAPI — user tables, session stores, idempotency keys, per-user lookup maps.
 triggers: [database, kv, key value, namespace, store, state, etag, cas, session, idempotency]
-checksum: sha256-pending
+checksum: sha256-247b0efe4af6d1eebc320a11b9b7ce3f5b1aa6a2f86fa80631bb3fec1e0a8d22
 ---
 
 # MyDatabaseAPI

package/dist/skills/my-database-api/claude/.claude-plugin/plugin.json

@@ -2,5 +2,6 @@
   "name": "my-database-api",
   "description": "Per-org KV store with namespaces + compare-and-swap. JSON values up to 256 KB. The substrate for stateful agent-built apps.",
   "version": "1.0.0",
+  "status": "ga",
   "published": true
 }

package/dist/skills/my-domain-api/SKILL.md

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   Register new domains and manage edge settings. Required before a funnel can go live on a custom URL.
 triggers: [domain, register domain, dns, custom domain, edge, cdn, security level, browser check, renew, namecheap]
-checksum: sha256-pending
+checksum: sha256-067ab2cc412c1f1f34aaeeec5890f9eb77f680f5b2d1c847e376336702cd8344
 ---
 
 # MyDomainAPI

package/dist/skills/my-domain-api/claude/.claude-plugin/plugin.json

@@ -2,5 +2,6 @@
   "name": "my-domain-api",
   "description": "Domain registration and check with automated DNS and email infrastructure.",
   "version": "1.0.0",
+  "status": "ga",
   "published": true
 }

package/dist/skills/my-email-api/SKILL.md

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   Send transactional and bulk email from your own domain. Create mailboxes, send/receive messages, generate AI templates, and manage warmup.
 triggers: [email, mailbox, send email, transactional email, template, warmup, inbox, outbox, ses, sender reputation]
-checksum: sha256-pending
+checksum: sha256-fa1eb6ee9e24935266643ceeecf7a748747b23377a0bfe256f76b71b62bd6349
 ---
 
 # MyEmailAPI

package/dist/skills/my-email-api/claude/.claude-plugin/plugin.json

@@ -2,5 +2,6 @@
   "name": "my-email-api",
   "description": "Send transactional and bulk email from your own domain. Mailboxes, AI templates, and warmup.",
   "version": "1.0.0",
+  "status": "ga",
   "published": true
 }

package/dist/skills/my-email-verify-api/SKILL.md

@@ -4,7 +4,7 @@ version: 1.0.0
 description: >
   Synchronous single-address email verification — syntax + DNS + Microsoft GetCredentialType probe. Returns a verdict in <1s for ~50% of inputs; the rest get verdict='unknown' with smtp_recommended=true. The pre-send quality gate for any outbound campaign.
 triggers: [email verify, email validation, deliverability, smtp, syntax check, dns mx, microsoft, mx lookup, bounce prevention]
-checksum: sha256-pending
+checksum: sha256-a8f4d3fa04436c997d02d1d33f262190166e59e3e890b1c40a877bbd49ad3f00
 ---
 
 # MyEmailVerifyAPI

package/dist/skills/my-email-verify-api/claude/.claude-plugin/plugin.json

@@ -2,5 +2,6 @@
   "name": "my-email-verify-api",
   "description": "Sync single-address email verification — syntax + DNS + Microsoft probe. Pre-send quality gate for outbound.",
   "version": "1.0.0",
+  "status": "ga",
   "published": true
 }