Skip to content
Back to skills

Mk 096

ASecurity

Dividing roles between ongoing and campaign traffic. Use when the task requires a task table for break-even traffic and campaign-driven additional volume. Apply this method to the specified inputs and verify the deliverable

  • 259 stars
  • 0 votes
  • 0 copies
  • 1 view
  • 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-096 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mk 096?

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

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

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-096
description: "Dividing roles between ongoing and campaign traffic. Use when the task requires a task table for break-even traffic and campaign-driven additional volume. Apply this method to the specified inputs and verify the deliverable"
---

# MK-096 | Dividing roles between ongoing and campaign traffic

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

## Purpose

This skill delivers: **A task table for break-even traffic and campaign-driven additional volume**

Historical seasonality can inform planning but does not guarantee recurrence; do not create paid schedules or publish without user approval

## Required inputs

Raw inputs: routine/event tasks, mature matched orders/costs, break-even requirements, organic/member purchases, stock/fulfillment, total budget and cash reserve requirements

## Method

1. Separate routine operations, education, event demand and member repeat purchases; list valid outcomes/full costs and count each order once. Separate break-even traffic from the paid shortfall rather than buy all revenue-target traffic
2. Check whether routine tasks have valid demand, affordable acquisition costs and fulfillable products. Supported tasks retain candidate input; fix unsupported costs/landing first. The routine label does not protect every budget unconditionally
3. Actual event demand, offers, stock and pages plus affordable input within total/cash constraints support bounded event investment. Separate shifted normal member purchases and discounts from new demand
4. Compare retaining routine input, transferring part to events or deferring events, showing foregone outcomes/costs. Exclude unfulfillable, nonpositive-contribution or over-limit options first. Without incremental evidence, propose capped options rather than a fixed split
5. Deliver task allocation, costs/outcome sources, retain/transfer/defer choices and review evidence. Reallocate after changed event demand, mature routine results, stock or cash limits and preserve the original decision

## Calculations and interpretation

Compare same-period incremental available contribution minus additional event/step costs. Without a counterfactual, incremental components remain assumptions. Count existing and new input once within the total

Hypothetical check: both routine and event candidates are affordable, but event goods cannot arrive by the promised date; retain routine input and defer the event. Confirmed fulfillable stock makes the event eligible for the same-total comparison, without raising the total

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

## Required output fields

| Order | Field | How to complete |
|---:|---|---|
| 1 | Source item | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 2 | Target item | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 3 | Supporting task | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 4 | Evidence of fit | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 5 | Applicable conditions | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 6 | Unmatched items/conflicts | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |
| 7 | Next step | Use source evidence, an intermediate method result, or an explicit unknown; do not invent information |

## Verification cases

**MK-096-C05 | One item has two distinct uses**

Expected: List the uses and conditions separately; do not force a single match

## Method sources

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

Location: Annual

Source basis: extracted from course materials

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

English translation of source excerpt:

> Why learn to plan an annual schedule

Files in this skill

  • SKILL.md4.1 KB
  • assets/check-context.py14.6 KB
  • assets/context-contract.json15.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.