leveling-up-content-engine
Diagnose and transform any authorized video URL, upload, recording, transcript, podcast, interview, presentation, screen recording, webinar, ad, or published video into the strongest justified content portfolio.
Install / Use
npx skills add ericosiu/ai-marketing-skills --skill leveling-up-content-engineInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of leveling-up-content-engine
leveling-up-content-engine scores 92/100 on our quality scale, 885th of 4,700 Development & Engineering skills we index (top 19%).
Its SKILL.md is 8.8 KB long, well organised into 17 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.
With 3,573 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so leveling-up-content-engine is actively maintained.
- Our last check on 2026-10-27 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
leveling-up-content-engine compared with similar skills
All 4 of these similar skills score higher than leveling-up-content-engine; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| leveling-up-content-engine (this skill)by ericosiu | 92 | 3.6k | 55d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install leveling-up-content-engine?
- Run
npx skills add ericosiu/ai-marketing-skills --skill leveling-up-content-engine. The install tabs above show the steps for each supported agent. - Which AI agents does leveling-up-content-engine work with?
- It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is leveling-up-content-engine safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is leveling-up-content-engine still maintained?
- The repository was last updated about 2 months ago, so leveling-up-content-engine is actively maintained.
Skill content
View source on GitHubname: leveling-up-content-engine description: "Diagnose and transform any authorized video URL, upload, recording, transcript, podcast, interview, presentation, screen recording, webinar, ad, or published video into the strongest justified content portfolio. Use for video audits, format recommendations, long-form editing, mid-form explainers, Shorts and Reels, teasers, tutorials, case studies, paid cutdowns, captions, packaging, delivery, or publication preparation."
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.
Unless production is requested, return a brief with the source score, recommended editorial and operating modes, opportunity counts, first release wave, repairs and dependencies, production complexity, portfolio jobs, and approval required to begin.
Inventory the source
- Record path or URL, size, duration, streams, and SHA-256 when available.
- Produce a speaker-aware timestamped transcript. Correct names, products, and numbers against the source.
- Build:
- a claim ledger separating results, estimates, anecdotes, forecasts, and targets;
- a rights ledger for third-party media, logos, consent, embargoes, and sponsors;
- a content-atom inventory with timestamps, viewer, promise, proof, tension, framework, payoff, visuals, caveats, and dependencies.
- Read references/opportunity-routing.md, score viable atoms, and record selected and rejected opportunities.
The opportunity inventory is the source of truth. Recommend how many assets the source supports; do not default to a quota.
Choose the transformation
Read references/quality-gates.md. Score hook, clarity, proof, pacing, and payoff from 0–20 each.
Choose the least destructive editorial mode:
- Polish — remove errors, dead air, and technical distractions.
- Tighten — remove repetition and tangents while preserving structure.
- Re-architect — rebuild the cold open, move proof, reorder sections, and bridge gaps.
- Rebuild — add pickups, narration, demonstrations, or graphics to create a materially new product.
For Tighten, Re-architect, or Rebuild, create an exact-source word- or sentence-level timestamped transcript before final cuts. Memo timestamps are section guides, never literal cut points.
Read references/format-modes.md. Select one primary mode and justified secondary modules. When no mode is named, default to Portfolio Audit and recommend the smallest useful release wave.
Lock the portfolio spine
Write:
[Viewer] should believe [verdict] because [proof], then use [framework] to reach [outcome].
Give each selected asset one promise, viewer, platform, job, payoff, parent, destination, and packaging intent. Reject repeated promises, incomplete excerpts, unsupported claims, and assets that cannot stand alone.
Produce selected modules
Long-form
Create a cut/reorder map and EDL before rendering. Resolve clips against the exact transcript and begin and end on complete thoughts. Run:
python3 scripts/audit_edit_boundaries.py \
--transcript <exact-source-transcript.json> \
--clips <retained-clips.json> \
--output <boundary-audit.json>
After rendering, transcribe the master and review every join. Record the left tail, right head, transition, verdict, and repair. Technical decoding does not replace semantic review. Preserve previous renders as versioned files.
Mid-form
Create self-contained 3–12 minute videos around one framework, case study, question, argument, or demonstration. Give each an independent hook, context, proof, payoff, package, and destination.
Short-form and micro
Create 15–90 second vertical assets only from complete atoms. Start on the hook, preserve claim context, render at 1080×1920, include burned captions plus SRT, and end on a payoff or useful question.
Create 6–20 second teasers, hook tests, story units, paid cutdowns, or quote motion only when they route truthfully. Label promotional clips separately.
Captions and opening treatment
Default masters to readable burned-in captions plus matching SRT unless the user opts out. Validate monotonic non-overlapping cues, at most two lines, mobile-safe margins, and cue end at or before the master.
Default the opening three to four seconds to a designed hook overlay unless the brief requires a clean opening. Reinforce the spoken promise without strengthening the claim. Check collisions with captions, lower thirds, chapter cards, and qualifiers. Claim qualifiers take priority.
Carousels and written derivatives
Produce a swipe narrative, newsletter, article, post, thread, show notes, checklist, or summary when the format improves comprehension or distribution. Require supplied brand assets or use a neutral system; never reconstruct a person, mascot, logo, or identity from memory.
Package every asset
- Long-form: title, thumbnail brief, cold open, first-30-second promise, description, chapters, pinned comment, and end screen.
- Mid-form: browse/search title, cover, opening line, series label, description, and parent route.
- Short-form/micro: first-frame visual, spoken hook, headline, cover, post copy, comment prompt, and CTA.
- Carousel: cover promise, swipe progression, caption, CTA, final slide, sources, and alt text.
Create promise hypotheses, not cosmetic variants. Reject packaging whose promise is not paid off.
Plan distribution and control side effects
Inventory justified B-roll, screenshots, citations, diagrams, lower thirds, qualifiers, chapter cards, overlays, captions, punch-ins, music, sound design, pickups, narration, sponsor placement, and end-screen bridges. Define which visual layer yields when elements collide.
When requested, produce a release map with order, spacing, platform, routes, timely versus evergreen status, cannibalization warnings, and recut windows.
Never publish, schedule, upload, change sharing, spend quota, or activate a campaign without explicit approval and authoritative readback.
Converge, deliver, and learn
Apply references/quality-gates.md. Confirm source integrity, portfolio alignment, media decode and timing, edit boundaries, rendered joins, captions, overlays, claims, rights, packaging, and delivery files.
technical integrity does not equal a coherent edit
Read references/delivery-contract.md, produce its modular folder and manifest, then run:
python3 scripts/validate_delivery.py --root <delivery-folder>
Return scores, mode, opportunity counts, portfolio map, runtimes, packages, sources, outputs, QC, verified destination, publication status, and a 24-hour, 72-hour, and seven-day measurement plan. Promote a lesson only after repeated comparable results.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
