clickmax-packs

As tools abaixo aparecem com os nomes que o MCP da Clickmax registra. Se o seu cliente de IA prefixar nomes de tool (mcp<servidor>, mcp<servidor>, ou outro), use o nome já prefixado que aparecer na sua lista de tools.

When this applies

Use this skill for the pack lifecycle: a pack is a shareable bundle of funnels, pages, flows, and affiliated offers that a creator publishes for other workspaces to import. A pack belongs to one workspace and project. funnelsEngine is funnels3 (legacy) or funnels4 (snapshot-based sharing).

Not this skill:

• offer-level pricing/checkout control → use the offers tools
• standalone funnel/page/flow editing outside a pack → use the funnels/pages/flows tools

Entity model

|field|meaning| |-|-| |id|Pack UUID| |name|Display name| |description|Author-facing summary| |category / level|Catalog classification| |isActive|Whether the pack is listed/importable| |funnelsEngine|funnels3 or funnels4; snapshot/drift apply only to funnels4| |funnels / pages / flows|Contents referenced by the pack| |offers|Affiliated offers with commission and affiliation active state| |shareCount|How many times the pack has been imported| |publishedAt|When the pack became publicly shareable (null = unpublished)|

Snapshot lifecycle (funnels4 only)

• editing a pack's contents changes its source; drift means the source moved past the latest snapshot
• a snapshot is an immutable, versioned copy of the contents taken for sharing
• a snapshot version carries a gate status: draft (not validated) | validating (gate running) | valid (clean) | warnings (publishable, with caveats) | blocked (errors, not shareable)
• only valid or warnings snapshots become the importable (shared) version
• the gate runs asynchronously; reach the status by polling (packssnapshotget), not synchronously

Import resolution (funnels4 snapshot import)

• the import preview (packsimportpreview) lists what the importer must (or may) remap, because some references point to the author's workspace and cannot be cloned
• blocking: provider channels (webchat) and non-shared offers — the importer must supply their own before import; otherwise import is rejected
• optional: pages may embed lists/forms (the preview surfaces them per page); the importer can map each embedded list/form to one of their own, or leave it unmapped to keep the original reference (does not block import)
• external pages cannot be cloned — the importer supplies a URL per external page

Execute guide (exact params — avoid live tool-discovery)

• packs_list REQUIRES projectId (no default/workspace-wide mode) — resolve the project first (clickmax-projects) before listing.
• packssnapshotget and packssnapshotpublish both take {packId, version} — version is NOT optional/latest-implied. Source it from the {id, version} returned by the last packsresnapshot call, or from packssnapshot_drift's latestVersion. Never guess a version number.
• packscreate takes projectId + name (required); description/category/level/thumbnailUrl/funnelsEngine optional. Add contents afterward with packsappend — creation itself is always empty.
• packs_import's dependency resolution is FOUR separate maps, not one — pass the one matching what the preview flagged as blocking, not the generic-sounding one:

- resolutions — automation/flow STEP dependencies only (keyed by step, {type: 'automation', stepsDependencies: [...]}). - offerResolutions — non-shared offer remap (keyed by the pack's offer reference, {offerId} = the importer's own offer). - channelResolutions — blocking provider channel remap (keyed by the pack's channel reference, {channelId} = the importer's own channel). - pageResolutions — per-page list/form remap (keyed by page, {listIdMap, formIdMap}). - Plus externalPageUrls (map of external-page ref → URL) and overrideFlowsIds ([{originFlowId, importedFlowId}]) for flow-id overrides. - Stuffing a channel/offer remap into resolutions (the automation-only map) silently does nothing for that dependency — it stays unresolved and the import comes back partial.

Rules

• list + get only return non-deleted packs
• changing contents (packsappend/packsremove) requires a new snapshot (packs_resnapshot) before the shared version reflects the change
• an inactive offer affiliation blocks sharing — the gate reports it as an error
• deleting a pack stops it being importable but does not delete the underlying funnels/pages/flows
• importing is asynchronous and may finish success, partial (some offers unresolved), or failed
• any own resource the importer supplies for a remap (channel, offer, list, form) must belong to the importer

Consumer tips

• check drift (packssnapshotdrift) before sharing an edited pack; re-snapshot when the source changed
• resolve the blocking preview items (provider channels, own offers for non-shared ones, external page URLs) before importing to avoid rejection or a partial result
• page list/form remap is optional — map them to keep imported pages wired to the importer's own audience, or skip to leave the original references
• a published pack with a warnings snapshot is still importable; read the warnings to set expectations
• track an in-flight import by its returned id (packsimportedget) rather than assuming it completed
• importing workspaces stay PINNED to whichever snapshot version they imported — a later packsresnapshot/packssnapshot_publish on the source pack does NOT automatically propagate to already-imported workspaces; they'd need to re-import to pick up the change