Acquisition and launches
Integration marketing
Explain and distribute a verified joint workflow, with clear compatibility, data flow and support ownership.
Open-source skill · format validated
When this is useful
Build integration positioning, technical landing pages, ecosystem listings, joint examples, and partner launch plans for developer tools and data products. Use when two products solve a concrete workflow together; not for unverified connector pages or claiming an unauthorized partnership.
What to bring
Products and supported interfaces, shared user task, verified integration behavior, versions, access and data scope, support ownership, and partner authorization if any.
What you can work toward
A verified workflow brief, integration page or listing, example and evidence notes, support boundary, distribution drafts, and maintenance plan.
Developer-tool version
Verify the SDK/CLI/plugin/CI/API workflow, versions, permissions, expected result, artifact storage, secrets handling, maintenance, and support ownership. Distinguish a custom example from an officially supported partner integration.
Data-product version
Verify source, transformation, destination, schema/update semantics, credentials, reconciliation, freshness, partial failures, and recovery. Connectivity alone does not prove correct operation; distinguish a tested supported connector from a custom example.
How to use it
Choose the version for your product type and follow its repository installation instructions. Keep the skill folder, references and any assets together. Each skill works on its own; reuse a shared brief when helpful rather than repeating a full intake.
The source follows the open Agent Skills format and is MIT licensed. Live research and execution depend on the tools and permissions available in your host. Preparing a plan or draft does not itself authorize publishing, messaging, spending or production changes.
A starting prompt
Use the integration marketing skill for our developer tool or data product. Our task is [specific task], our supported environment is [environment], and the decision is [decision]. Use these facts and sources: [evidence]. Produce the requested artifact, label unknowns, and do not invent results or perform external actions beyond my authorization.
How to judge the result
Do not generate a directory of unsupported product pairs, use restricted brand assets, or imply endorsement because an API is public.
Check that the product-specific version changes the recommendation, the requested deliverable is complete, and proposed tests are distinguished from observed results. Format validation does not establish how a model will perform on your product.
From input to reviewed output
Put it to work
- Choose the collection for your product type and install the relevant skill with its bundled references and assets.
- Supply the task, supported behavior, existing evidence and constraints that affect the decision. Reuse context already available.
- Ask for the concrete deliverable, distinguishing facts, hypotheses, unknowns and any untested instructions.
- Check the product-specific acceptance criteria, source claims and next steps before using or publishing the output.
Limits and tradeoffs
Do not generate a directory of unsupported product pairs, use restricted brand assets, or imply endorsement because an API is public. No fresh-host model performance is claimed; verify output against your product, evidence and authorized environment.