feat(package): add voc-data-pull, auto-installed on VoC platform connect

[Eric Smith (motionBuilderEric)]

What this is

voc-data-pull is an installer package that pulls raw voice-of-customer data - product reviews, support conversations, and ad comments - from a connected platform into standardized files in the org brain: one file per review/ticket/comment, flat metadata header + body, with the untouched platform payload preserved in every file. Creative strategy packages build on these files. Tracking: PDEC-9193.

Contents

• voc-data-pull/skill/SKILL.md - the pull workflow: resolve the connection path (Pipedream OAuth / stored secret / Motion native), follow the platform recipe, write files under /agent/brain/data-sources/<platform>/, report. Hard boundaries: read-only against platforms, bounded pulls, never write into /agent/brain/integrations/<source>/ (the guide spec forbids raw dumps), author_contact stays null pending the PII policy call.
• voc-data-pull/skill/references/platform-recipes.md - per-platform endpoints, pagination, discovery steps, and unified-template field mappings with evidence levels. Judge.me/Gorgias/Intercom endpoints are live-verified; Trustpilot/Yotpo are doc-grounded pending first connects; Junip is blocked on a dead key; Okendo/Stamped are secrets-path (customer API key + secure-fetch, no Pipedream app exists); Meta ad comments ride motion meta creative-comments.
• voc-data-pull/skill/templates/ - copyable file skeletons for the review and support-conversation shapes (the support shape follows the Ramy Brook Gorgias precedent: daily/<date>/ticket-<id>.md, metadata top, full conversation below).
• voc-data-pull/package.json - installer manifest: one directory resource installing the skill to agent_skills/voc-data-pull. installPolicy: auto so intent matches install without a manual step; updatePolicy: auto so recipe fixes roll out.
• package-index.json - the first indexed package. Categories list one integration:<slug> per VoC platform (judge_me, trustpilot, yotpo, junip, gorgias_oauth, intercom, okendo, stamped) because the VM reconciler matches literal connected slugs - no invented family category.
• scripts/validate-runneth-package-index.mjs - aligned with the current package-manager contract (package.json manifests, installPolicy, packageManagerVersion 1|2, manifest v2 tasks/workflows, backend-github sources). Same content as fix(package-index): validate current package contract #152; whichever merges first, the other rebases clean.
• Card files (use-case.json, README.md, marketing.md) exist for review; the slug is in catalog excluded[] - this is not a public-site use case.

How it installs

Connected-integration package intent (package intent add-integration <slug>, or the connect-time dispatch shipping in agent-builder) selects this package via its integration:<slug> categories; the desired-state installer installs it. Manual demo path works today with package intent add-integration <slug> in a sandbox.

Open items (surfaced, not solved here)

• Unified metadata template is proposed pending Eric/Rachel sign-off; built to it as the contract.
• PII: author_contact is nulled in output files pending policy. The raw payload section is spec'd untouched/never-lossy, which still carries contact emails - flagging for the same policy call.
• Folder convention pending Rachel's confirmation; the skill defers to any existing org data-sources/ convention.
• Post-install auto-run is deliberately not built; CSM prompt is the accepted v1 (routine triggers land separately).

CI note

The fleet-approval gate fires (new auto-installable package) - needs the runneth-fleet-change-approved label after core engineering approval.

Made with Cursor

[Eric Smith (motionBuilderEric)]

Opened prematurely - closing.