micro-offer-forge

Convert a workflow, skill, or capability into a sellable micro-offer with positioning, pricing, packaging, and launch assets.

Security Scan

The skill's instructions, inputs, and metadata are coherent with its stated purpose and request no extra installs, credentials, or system access.

Purpose & Capability

The name/description match the SKILL.md: the skill is a packaging/marketing guide for turning a workflow into a micro-offer. It does not request unrelated binaries, env vars, or config paths.

Instruction Scope

SKILL.md contains step-by-step marketing/packaging guidance and lists the inputs it needs from the user. It does not instruct the agent to read files, access environment variables, call external endpoints, or collect system data.

Install Mechanism

No install spec and no code files (instruction-only). This is the lowest-risk model: nothing is written to disk and no external artifacts are fetched.

Credentials

The skill requires no credentials, env vars, or config paths. The inputs are user-provided business context and are appropriate for the stated function.

Persistence & Privilege

always:false (no forced inclusion). disable-model-invocation is false (agent may call the skill autonomously), which is platform-normal; the skill does not request elevated privileges or modify other skills or system settings.

Assessment

This is an instruction-only marketing/packaging helper and appears internally consistent. Before using: (1) avoid pasting secrets or sensitive business data into the prompts — provide only the contextual information necessary; (2) review and vet any generated launch copy, pricing, or legal claims before publishing; (3) if you prefer manual control, disable autonomous invocation for the agent so the skill only runs when you explicitly invoke it; (4) treat suggestions as draft guidance (validate feasibility and compliance).

Use this skill to package something small but useful into a product people will pay for quickly.

Inputs

• Capability/workflow (what is being sold)
• Audience/niche
• Pain solved
• Delivery format (doc, template, script, audit, mini-service)

Process

1. Define the outcome promise in one sentence.
2. Select buyer persona + purchase trigger.
3. Build offer stack:
   • core deliverable
   • bonus(s)
   • turnaround/format
4. Price ladder:
   • entry price
   • standard
   • premium/add-on
5. Risk reducer:
   • guarantee, preview, sample, or proof
6. Launch assets:
   • landing copy draft
   • 5 post ideas
   • 3 DM/outreach lines

Output format

• Offer one-liner
• Who buys and why now
• Deliverables list
• Pricing table
• Objection handling bullets
• 7-day launch checklist

Constraints

• Avoid vague outcomes
• Keep scope small enough for fast delivery
• Focus on one painful problem only
• Make first version shippable in <=48h

Example

"Turn a Reddit research workflow into a €19 downloadable playbook + €99 done-with-you setup add-on."