Skip to content
Back to skills

Mk 111

ASecurity

Plan multi-item bundles around purchase quantity, usage scenarios, and benefits. Use for increasing average order value while addressing concerns that bundling could reduce a premium product's perceived value. Propose conditional candidates using real products and variable costs; verify sources separately for examples and platform data

  • 259 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 23, 2026
ai-agentsgo

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned October 23, 2026

npx -y skills add backtrue/thinkwithblack-skill --skill mk-111 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mk 111?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Mk 111
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/backtrue-mk-111/badge)](https://www.skillsdirectory.com/skills/backtrue-mk-111)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: mk-111
description: "Plan multi-item bundles around purchase quantity, usage scenarios, and benefits. Use for increasing average order value while addressing concerns that bundling could reduce a premium product's perceived value. Propose conditional candidates using real products and variable costs; verify sources separately for examples and platform data"
---

# MK-111 | Multi-item bundle design

For a regular chat, upload `packs/mk-111.md`. It includes the shared rules, this method, and required references

## Purpose

This skill delivers: **Purchase quantity, usage scenarios, and benefit explanations**

Do not fabricate discounts, gift inventory, countdown deadlines, limited quantities, or testimonials

## Required inputs

Raw inputs: actual baskets, valid single/bundle purchases, usage needs/cycles, SKU stock, discounted revenue, payment/fulfillment/packaging costs and recipient eligibility

## Method

1. Separate new/member tasks and usage situations for singles/bundles; specify quantities, contents, prices and delivery. Shared roles suggest hypotheses, while actual baskets/next needs support bundle use
2. Calculate net bundle revenue minus product, payment, shipping, packaging, gift and service costs. Count shared order costs once and retain per-item charges/stock limits. Check contribution and usage duration, not just order value
3. Omit/shrink bundles with unsupported need, unreasonable use quantities, nonpositive contribution or unavailable supply. Compare valid orders and same-period total contribution for supported singles/small/large bundles
4. Expand bundles with comparable demand and incremental contribution evidence. Bringing later purchases forward or subsidizing existing demand requires showing transfer/cost and shrinking/observing. Without bundle outcomes use a capped candidate test and retain a single-item choice
5. Deliver usage, eligibility, supply, costs, order/period contribution and conditions. Rechoose after costs/refunds/needs/stock corrections. Higher order value with lower total contribution does not retain expansion priority

## Calculations and interpretation

Total contribution is valid orders × matched average order contribution, or a per-order sum when costs differ. Include the later window from which demand may be pulled forward

Hypothetical check: singles give 100 orders × 100 = 10,000; bundles give 60 × 140 = 8,400. Higher bundle order value does not support replacing all singles. Correcting to 80 valid orders gives 11,200, then check transferred demand and supply before expansion

Decision rules authored by ThinkWithBlack on 2026-10-14; original course sources are retained below

## Required output fields

| Order | Field | How to complete |
|---:|---|---|
| 1 | Goal | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 2 | Audience | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 3 | Plan/task | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 4 | Evidence and assumptions | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 5 | Prerequisites | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 6 | Resources | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 7 | Deliverables and acceptance | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 8 | Open issues | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |

## Verification cases

**MK-111-C05 | The budget is unknown, but materials can be organized first**

Expected: Deliver the parts of the plan that do not depend on the budget first; do not require a complete questionnaire

## Method sources

Source file: 行銷策略實戰學程Day4-佈局獲利 × 節奏變現 × 轉單收割

Location: Campaign

Source basis: extracted from course materials

Source URL: https://docs.google.com/presentation/d/1dq3xqYVUnWvUCpzZKI91yDDOzvkyG0uHy3EOsOjtItA/edit

English translation of source excerpt:

> Consider consumers with active needs each month and bring campaign traffic to the campaign page for prompt conversion

Files in this skill

  • SKILL.md4.3 KB
  • assets/check-context.py14.6 KB
  • assets/context-contract.json19.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.