Marketing Tools / Creative Ops

Utility Campaign Concept Designer

Convert a campaign brief into useful interventions that help people, shift behavior, or solve a real friction before generating messages.

DocumentationAgent instructionsRequirements & limits

Use when a team wants campaign concepts that do something useful rather than only communicate a message.

Inputs

  • Brand and category
  • Business objective
  • Audience tension or friction
  • Product/service capabilities
  • Available surfaces: app, site, store, CRM, packaging, data, customer service, creators
  • Constraints: legal, budget, timing, markets

Outputs

  • Utility-led concept territories
  • Behavioral hypothesis
  • Proof and feasibility notes
  • Risk flags

Before you begin

  • Reading and copying the procedure require no terminal setup. Check requirements for any packaged programs separately.

Try this first

Read the procedure and supply its documented inputs. Use the full text in an agent app or chat that supports pasted instructions, following that host's guidance.

Limits for this step
  • Instruction package only; it does not provide or authorize an executable runtime capability.
  • Safe for concepting; require brand, legal, and operations approval before production or public use.
Read full instructionsHide full instructionsSKILL.md · v0.1.0

Utility Campaign Concept Designer

When to use

Use this skill when the brief risks becoming another message-first campaign and the team wants ideas that help people or change behavior.

Inputs required

  • Brand and category
  • Business objective
  • Audience tension or friction
  • Product/service capabilities
  • Available surfaces: app, site, store, CRM, packaging, data, customer service, creators
  • Constraints: legal, budget, timing, markets

Workflow

  1. Restate the human friction behind the brief.
  2. Convert the brief from what do we want to say? to what can we help people do?.
  3. Generate 5-7 utility territories, each with a behavioral hypothesis.
  4. Score each territory for usefulness, brand fit, cultural timing, feasibility, and risk.
  5. Select the strongest 2-3 and describe execution paths.

Output format

Return:

  • human_friction
  • utility_territories
  • score_table
  • recommended_concepts
  • required_proof
  • operational_dependencies
  • risk_notes

Guardrails

  • Do not present a message as utility unless it changes what someone can do.
  • Avoid manipulative urgency, false scarcity, or exploitative emotional triggers.
  • Call out when the product cannot credibly deliver the proposed help.
  • Prefer simple useful interventions over complex stunts.
View file metadata
---
name: utility-campaign-concept-designer
description: Design campaign concepts that provide real utility: protection, help, proof, simplification, safety, learning, belonging, or behavior change.
---

Summary sources · Catalogue metadata, skill.yaml, SKILL.md, examples/output.json · v0.1.0 · Release package

Install instruction files

These commands copy guidance into the selected runtime directories. Confirm that your agent app discovers it. Any packaged programs need separate setup and verification.

Install (Codex)

./bin/skills-hub install marketing/[email protected] --runtime codex

Install (Claude)

./bin/skills-hub install marketing/[email protected] --runtime claude

Install (Generic)

./bin/skills-hub install marketing/[email protected] --runtime generic --target ./my-agent/skills

How You Can Use This

Documentation

Resource form: Agent instructions

Read or copy the guidance. Any packaged programs have separate execution requirements and evidence.

First run: Read SKILL.md and follow the documented workflow.

Current limits

  • Instruction package only; it does not provide or authorize an executable runtime capability.
What installation and verification mean
File installation
Places package files and generated configuration in the selected directories.
Native discovery
Your agent app finds and accepts the instructions, tools or plugin registrations.
Mock execution
Exercises sample fixtures. Connected data and provider effects need a separate check.
Connected operation
Requires current configuration, provider authentication, scoped permissions and a successful operation in your intended environment.

Declared compatibility

Compatibility unknown: versions and capabilities have not been declared.

Classification: declared

Technical details and release files

Operational Summary

Execution mode: analysis-only

Approval boundary: Safe for concepting; require brand, legal, and operations approval before production or public use.

Review and lifecycle

Review maturity: Experimental

Security review declaration: Not declared

Lifecycle: Active

These release declarations are separate from evidence that a workflow operates in your environment.

Runtime & Dependencies

ID: marketing/utility-campaign-concept-designer

Tags: utility, creative-concepts, empowerment, cannes-2026, anti-slop

Runtimes: codex, claude, generic

Tool dependencies: 0

API dependencies: 0

Dependencies

Tools: Not documented

APIs: Not documented

Outputs

  • Utility-led concept territories
  • Behavioral hypothesis
  • Proof and feasibility notes
  • Risk flags