produce-asset

Generate per-slot render-ready prompts and an asset manifest from marketing briefs.

14|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/hungv47/meta-skills --skill produce-asset
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: produce-asset
Source: https://github.com/hungv47/meta-skills/tree/main/skills/marketing/produce-asset
Command: npx skills add https://github.com/hungv47/meta-skills --skill produce-asset

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Turn briefs into structured, render-ready prompts and a canonical asset manifest, enabling tool-agnostic production workflows without API keys or rendering engines.

Core Features & Use Cases

  • Generate per-slot render-ready prompts tailored to the target image engine or designer workflow.
  • Emit a manifest at docs/forsvn/artifacts/marketing/produced-assets/[slug]/manifest.md that traces inputs and outputs.
  • Enforce brand fidelity by preserving verbatim copy slots and applying placeholder rules when logos are missing.

Quick Start

Use the produce-asset skill to transform a design brief into prompts and a manifest for downstream rendering.

Frequently Asked Questions about produce-asset

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn design briefs into render-ready marketing prompts?

You can turn design briefs into render-ready marketing prompts by processing multi-slot briefs to emit per-slot prompts and validation rules. This generates outputs ready for downstream rendering and asset management without needing API keys.

What is an asset manifest and how does it trace marketing asset production?

An asset manifest traces inputs and outputs for marketing asset production by recording per-slot prompts and validation data. It is emitted as a canonical markdown file to structure downstream verification and asset management workflows.

Do I need an API key to generate prompts for an image engine?

You do not need an API key to generate prompts for an image engine. The process operates tool-agnostically by transforming briefs into structured text prompts and an asset manifest without connecting directly to rendering APIs.

How do I enforce brand fidelity when generating prompts from multi-slot briefs?

To enforce brand fidelity when generating prompts from multi-slot briefs, the system preserves verbatim copy slots and applies placeholder rules when logos are missing. This ensures brand consistency across all produced assets.

What is the best way to structure outputs for downstream asset verification?

The best way to structure outputs for downstream asset verification is emitting a canonical manifest file alongside per-slot prompts. This traces all inputs and outputs, enabling direct verification without additional API connections.