Marketing Plugins / Creative

Creative Operating System Plugin

Bundle the Creative Operating System workflow into one installable package with audit, concepting, creator, timing, evaluation, and first-run operational templates.

Not verifiedComponent bundleRequirements & limits

Inputs

The released example shows these fields. Check the guide for which are required.

  • brand
  • objective
  • approval_owner

Outputs

  • An ordered workflow with an approval owner

Before you begin

  • Node.js 22 for the packaged sample. Public launch remains approval-gated.

Try this first

Inspect the packaged offline sample before running it. After file installation, use the stated runtime from the installed package directory.

Limits for this step
  • Launch and product-surface changes remain human-approved; packaged Markdown hooks are advisory on runtimes without native enforcement mappings.
  • Packaged programs have independent setup and verification requirements. Reading or copying this procedure does not verify their execution.
Inspect offline sampleHide offline sampleSynthetic example

Runtime · Node.js 22. Run from the installed package directory after file installation.

node scripts/first_use.mjs examples/first-use-input.json

Expected result · An ordered workflow and approval owner. The sample does not authorize launch.

This is the release’s documented sample, separate from evidence of operation in your environment.

Sample input
{
  "brand": "Example Studio",
  "objective": "Prepare a governed concept for a product launch.",
  "approval_owner": "campaign-owner"
}

Summary sources · Catalogue metadata, plugin.yaml, README.md, examples/first-use-input.json · v0.2.0 · Release package

View package contentsHide package contentsv0.2.0

Bundled skills

Bundled agents

Packaged hooks

require-memory-before-ideation

Require Memory Before Ideation

Trigger before concept generation.

Intent

  • stop the workflow if approved memory or claims evidence is missing
  • require the team to fill the brand-memory intake before creative ideation
  • distinguish facts, assumptions, and unverified preferences
require-launch-gate-review

Require Launch Gate Review

Trigger before anything externally visible ships.

Intent

  • require completion of the launch gate checklist
  • confirm claims evidence, approvals, and rollback owner
  • block launch if product-surface, creator, or cultural-risk reviews are incomplete

Install plugin files

These commands install package files and generate runtime configuration where supported. Confirm discovery in your agent app, then check configuration, authentication and a first useful operation.

Install (Codex)

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

Install (Claude)

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

Install (Generic)

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

Bundled skills, agents and tools are placed in the selected runtime directories. Hooks stay inside the plugin directory. Codex and Claude targets also receive a generated plugin manifest.

No security review is declared for this release. Review bundled components, required secrets and approval rules before live use.

  • Approval rules: human-review-before-public-launch, human-review-before-product-surface-change

How You Can Use This

Not verified

Resource form: Component bundle

Current operational evidence for your environment is not shown here. Check the implementation, installation requirements and limits before use.

First run: Run `node scripts/first_use.mjs examples/first-use-input.json` after installation to generate a first-run operating-system checklist.

Current limits

  • Launch and product-surface changes remain human-approved; packaged Markdown hooks are advisory on runtimes without native enforcement mappings.

Packaged executable helpers

Each program has its own setup requirements and operational evidence. Reading or copying the instructions does not verify these programs.

scripts/first_use.mjs · Not verified · Local program

First run: node scripts/first_use.mjs examples/first-use-input.json

  • Requires a declared Node.js 22 execution capability; it never authorizes launch.
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: inferred

Technical details and release files

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.

Metadata

ID: marketing/creative-operating-system-plugin

Tags: creative-operating-system, anti-slop, creator-ops, product-as-media, cultural-timing, governance

Latest: 0.2.0

Runtimes: codex, claude, generic

Requirements

Secrets: 0

Approvals: 2

Approval rules: human-review-before-public-launch, human-review-before-product-surface-change