AI Marketing Skills is a collection of open-source workflows that help AI coding agents handle marketing and sales work, including growth experiments, pipeline management, content operations, outbound outreach, SEO, and finance analysis. It is intended for marketing and sales teams that want reusable agent-driven processes. The catalogue entries package these workflows as skills for compatible coding agents.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ericosiu/ai-marketing-skillsnpx agentmods add skills/ericosiu/ai-marketing-skills/leveling-up-content-engineWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ericosiu/ai-marketing-skills/leveling-up-content-engine)<a href="https://agentmods.dev/skills/ericosiu/ai-marketing-skills/leveling-up-content-engine"><img src="https://agentmods.dev/badge/skills/ericosiu/ai-marketing-skills/leveling-up-content-engine/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ericosiu/ai-marketing-skills/leveling-up-content-engine"><img src="https://agentmods.dev/badge/skills/ericosiu/ai-marketing-skills/leveling-up-content-engine.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00088 | $0.01844 |
| Opus 5.5 | $0.00035 | $0.00738 |
| Sonnet 5.5 | $0.00018 | $0.00369 |
| Haiku 4.5 | $0.00009 | $0.00184 |
Grade A, and why
leveling-up-content-engine scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 29d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
92% identical to video-content-engine — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Leveling Up Content Engine
Turn one grounded source into the strongest justified portfolio. Do not manufacture a fixed number of derivatives. Find distinct promises, select formats that can pay them off, and give every asset a portfolio job.
Preamble
Run the repository's privacy-preserving version check and telemetry initializer when available:
python3 telemetry/version_check.py 2>/dev/null || true
python3 telemetry/telemetry_init.py 2>/dev/null || true
Remote telemetry is opt-in. Never log content, URLs, paths, credentials, names, or business data.
Updated editorial and release workflow
Read the current workflow updates before selection, editing, packaging, review, or release planning. These rules supplement the bundled format, opportunity, quality, and delivery contracts.
Use the source's actual show and brand. A derivative retains its parent show even if only one speaker appears. Obtain the authorized brand brief and assets; this package includes no private channel access or internal recording history.
State the operating contract
Before work, state the exact source, owner, channel, destination, requested modules, delivery format, this turn's artifact, stop condition, and known blocker class.
Preserve the source read-only. Never claim a render, upload, preview, publication, or QC pass without fresh evidence. Treat performance targets as experiments, not forecasts.
Accept any grounded source
Accept a public or authorized URL, uploaded file, local file, transcript, audio recording, or source folder. A bare request such as run this skill on this video defaults to diagnose and recommend, not automatic production.
For a link:
- Resolve the exact page, owner, channel, title, duration, and accessible media or transcript.
- Prefer the original file, then an authorized downloadable master, then the published stream.
- Never substitute a mirror, alternate upload, account, episode, or transcript.
- If authentication, permissions, DRM, missing media, or an unavailable transcript prevents grounded analysis, request an accessible source. Do not make editorial recommendations from metadata alone.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 317 B
- README.md 2.4 KB
- references/delivery-contract.md 1.3 KB
- references/editorial-and-release-updates.md 6.8 KB
- references/format-modes.md 1.5 KB
- references/opportunity-routing.md 1.1 KB
- references/quality-gates.md 2.4 KB
- requirements.txt 63 B
- scripts/audit_edit_boundaries.py 2.9 KB runs code
- scripts/validate_delivery.py 3.7 KB runs code
- tests/test_scripts.py 2.3 KB runs code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 29d ago First seen · 146 lines · 88 tokens per session scan A 090bb4b8b144
leveling-up-content-engine is a skill published in the GitHub repository ericosiu/ai-marketing-skills (3,678 stars, last pushed 29d ago), licensed MIT. It adds 88 tokens to every session and 1,844 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to video-content-engine, differing in 27 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…