Acquisition and launches
Community distribution
Prepare useful technical contributions for relevant communities, maintainers and product ecosystems.
Open-source skill · format validated
When this is useful
Plan community and ecosystem distribution for developer tools and data products through relevant discussions, maintainers, technical events, newsletters, and partners. Use for contribution-led distribution and channel-specific drafts; not for bulk promotion or unauthorized posting.
What to bring
Audience task, relevant communities or ecosystem, rules and access, affiliation, useful technical asset, and available participation capacity.
What you can work toward
A channel-fit map, useful contribution drafts, affiliation and rule checks, reply ownership, and a proportionate measurement plan.
Developer-tool version
Choose stack-specific communities, maintainers, or package ecosystems where the task is relevant. Offer a reproducible answer and disclose affiliation. Respect project governance and maintain the example rather than turning issue trackers into promotion channels.
Data-product version
Choose source/warehouse ecosystems and practitioner communities where the workload is relevant. Contribute a synthetic reconciliation example, operational lesson, or transparent methodology; never expose private customer queries or records.
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 community distribution 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 post, open promotional issues, contact maintainers, or send messages without authorization. No fake accounts, astroturfing, or unsolicited bulk outreach.
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 post, open promotional issues, contact maintainers, or send messages without authorization. No fake accounts, astroturfing, or unsolicited bulk outreach. No fresh-host model performance is claimed; verify output against your product, evidence and authorized environment.