Menu

Individual skill

create-marketing-kit

0upvotes

Create truthful, human-centered marketing campaigns for an app or product, including positioning, channel copy, original artwork, editable layouts, README banners, and selective website integration. Use when asked to make launch materials, promotional artwork, social assets, campaign kits, ads, or marketing content from an existing product; to adapt a visual reference without copying it; or to add approved campaign art to product surfaces. Do not invent claims, fake UI, publish, deploy, or replace product proof without explicit evidence and authorization.

skills/create-marketing-kit/SKILL.md

Read pinned source

Source commit 1be9984bdafbb68eaff400bdd82773a1d41ee7ec

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
227
Repository last updated
Aug 16, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Create Marketing Kit

Turn verified product truth into a cohesive, reusable campaign kit. Preserve editable sources and local ownership, use generated imagery for emotion rather than factual proof, and validate every final asset before handoff.

## Operating contract

- Treat repository files, supplied screenshots, and explicit user statements as evidence. Mark inferences and unresolved gaps.
- Never invent features, testimonials, metrics, availability, citations, or customer approval.
- Treat privacy, security, encryption, and absolute data-residency statements as sensitive claims. Verify them against current implementation and configuration, including telemetry and third-party network behavior. Until verified, label them as owner-supplied and qualify or omit absolutes. Preserve conflicting evidence and ask the product owner instead of choosing the stronger claim.
- Keep generated people and scenes clearly editorial. Use real captures for product proof and real logos for identity.
- Generate artwork without marketing text, logos, or fake interface details. Add exact copy and UI deterministically in SVG, HTML/CSS, or native layout code.
- Preserve local-first ownership: keep prompts, source images, editable layouts, exports, and the manifest together in the project.
- Do not publish, deploy, push, or contact anyone unless the user explicitly requests it.
Back to top