clickmax-packs
Use when the user wants to inspect, create, edit, snapshot, publish (share), or import Clickmax packs — shareable bundles of funnels, pages, flows, and affiliated offers — including funnels4 snapshot/drift/gate handling and import remap resolution.
How do I install this agent skill?
npx skills add https://docs.clickmax.io --skill clickmax-packsIs this agent skill safe to install?
No partner audit is available yet. Read the source before installing.
What does this agent skill do?
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; funnels4 activation needs a published snapshot (see lifecycle) |
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;
driftmeans 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
validorwarningssnapshots become the importable (shared) version - order for funnels4: new version (the
snapshotreturned bypacks_append, orpacks_resnapshotwhen nothing was appended) →packs_snapshot_publish→ pollpacks_snapshot_getuntilvalid/warnings(promoted to the published version) → THENpacks_updatewithisActive: true; activating before a published version returns 409 - imports read ONLY the published version (never a newer draft); no published version → import returns 409 "Este pacote ainda não foi publicado pelo produtor"
- the gate runs asynchronously; reach the status by polling (
packs_snapshot_get), not synchronously
Import resolution (funnels4 snapshot import)
- the import preview (
packs_import_preview) lists what the importer must (or may) remap, because some references point to the author's workspace and cannot be cloned; for funnels4 it reads only the published snapshot (no published version → error) - 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_listREQUIRESprojectId(no default/workspace-wide mode) — resolve the project first (clickmax-projects) before listing.packs_snapshot_getandpacks_snapshot_publishboth take{packId, version}—versionis NOT optional/latest-implied. Source it fromsnapshot.versionof the lastpacks_append, the{id, version}of the lastpacks_resnapshot, or frompacks_snapshot_drift'slatestVersion. Never guess a version number.packs_createtakesprojectId+name(required);description/category/level/funnelsEngineoptional (cover →packs_cover_set;funnelsEngineomitted =funnels4;funnels3only for funnels3 funnels —packs_appendrejects other-engine funnels with 409). Add contents afterward withpacks_append— creation itself is always empty.packs_appendfunnelModes(full|skeleton= structure only, no pages/automations/offers) is stored per funnel and reused by every later version; re-send a funnel already in the pack with the other mode to switch it, omit it to keep its mode.packs_import's dependency resolution is FIVE separate maps, not one — pass the one matching what the preview flagged, not the generic-sounding one:valueMap— automation dependencies (previewdependencies[]):{[kind]: {[originId]: ownId | null}}; one choice per author resource, applied to every step + trigger using it. Missing ornull→ the copy gets the field empty (never the author's id).resolutions— per automation (keyed by preview automationid):{type: 'automation', skip: true}= don't create it.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) andoverrideFlowsIds([{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 backpartial.
Rules
- list + get only return non-deleted packs
packs_append(funnels4) already generates the new draft version and returns it assnapshot→ publish THAT version; don'tpacks_resnapshotagain.packs_removerequirespacks_resnapshotbefore the shared version reflects the change- a funnel deleted at the source leaves the pack automatically (on delete and on the next version)
- an inactive offer affiliation blocks sharing — the gate reports it as an error
- funnels4: never activate (
isActive: true) before the published snapshot reachesvalid/warnings; content changes reach importers only after a new version is published - 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), orfailed - any own resource the importer supplies for a remap (channel, offer, list, form) must belong to the importer
Consumer tips
- check drift (
packs_snapshot_drift) 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
partialresult - 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
warningssnapshot is still importable; read the warnings to set expectations - track an in-flight import by its returned id (
packs_imported_get) rather than assuming it completed - importing workspaces stay PINNED to whichever snapshot version they imported — a later
packs_resnapshot/packs_snapshot_publishon the source pack does NOT automatically propagate to already-imported workspaces; they pick it up withpacks_imported_update_get→packs_imported_update_apply(see "Updating an imported pack")
After import: "Conecte para ativar"
An import only finishes setup when its account slots are resolved; the imported automations stay without an account until then. importId = id from packs_imported_list (not the packId).
packs_imported_slots_list→ for eachopenslot withfillable: true, fill it withpacks_imported_slots_updateusing one of itscandidates[].id(pre-picksuggestedId); several slots of the sameentity→applyToSameEntity: trueonce. No candidate → the importer must connect that account first (route them to the integration);resolvedId: nullskips the slot instead.fillable: falseslots are configured inside the automation editor — tell the user which automations (locations) instead of trying to fill them.gupshupTemplateslots: the importer needs their own approved WhatsApp templates. Withtemplate.replicable: trueand an official number inwhatsappNumbers, confirm the list with the user, thenpacks_imported_slots_templates_create(channelInstanceId+slotIds). Slots gopendinguntil Meta approves and fill themselves; reportfailedentries and re-read the list later to seereview.status/reason.
Updating an imported pack
Imports stay pinned to the version they imported. When the author publishes a new one: packs_imported_update_get → if not upToDate, show the items; for each ask: true item ask the user keep or take (changed) / keep or delete (removed), warning when edited (their changes are lost on take) or live → packs_imported_update_apply with decisions keyed kind:sourceId. Never decide for the user. New automations can open new slots → re-run the slots flow above.
Author: sharing, extra assets and cover
- Before appending funnels/pages,
packs_checkout_offers_preview(funnels/pagesids) shows which offers their checkouts sell and whether each is shared; tell the user which products go along. packs_offer_sharing_update(packId+offerId+isShared) decides if importers sell the author's offer (true) or must bring their own (false, blocking in their import preview). Gated: changes what every importer sells. Needs the affiliation-packs feature.packs_snapshot_assets_list(packId+version) lists the extra assets a version carries (quiz, custom fields…) — use it to answer "what goes with the pack".- Cover: ask the user to upload the image in the chat (an
imagequestion), thenpacks_cover_setwithpackId+ the uploadedimageUrl;packs_cover_removeclears it.packs_create/packs_updatedo not take a cover URL, and images from other sites are refused.
Clickmax skill revision: 23f2b5440092
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/docs.clickmax.io/clickmax-packs">View clickmax-packs on skillZs</a>