---
name: "skill-channel-ops"
type: skill
license: CC BY-NC-SA 4.0
description: 'Reach''s channel operating procedure for a retail venture — how a planned, approved action reaches a live channel and what each channel needs to run. Per-channel procedure for the channels convention-retail names: the Shopify DTC store and its sales channels, Instagram and Pinterest (organic and shop), TikTok, email (handed to skill-newsletter-strategy and skill-lifecycle) and marketplaces (Etsy, Not On The High Street or the craft equivalent); what each channel needs from Pixel (asset specs) and from the store (catalogue sync, product feed); the human-action boundary per channel (paid spend, discount codes, anything irreversibly public); and what the skill cannot do without a wired connector. Use whenever Reach needs to action a plan from skill-gtm-plan or skill-launch-campaign on a live channel rather than draft it, open a channel the venture''s stage has earned, or record what went live for skill-campaign-report. Stages and records; the operator releases. Promoted from placeholder by APP-1080.'
---

# channel-ops

Reach's execution skill. `skill-gtm-plan` decides which channels a venture runs and why; `skill-content-studio` drafts what goes on them; this skill puts the approved thing on the live channel, through whatever connector the venture has wired, and records that it went. It reads the channel model in `convention-retail` for which channels a venture at 0→1 should be running at all, `convention-shopify` for the store's tooling and the human-action boundary, and the venture's `convention-brand` for the look each asset must carry. It never decides strategy and never designs; it operates.

## Trigger

- Approved content is due on a channel: a calendar slot from `skill-gtm-plan`, a phase from `skill-launch-campaign`, an issue from `skill-newsletter-strategy`, a flow from `skill-lifecycle`.
- A channel the venture's stage has earned (per `skill-retail-strategy` Pass 5) needs opening or configuring — a Shopify sales channel, a Pinterest shop, a marketplace listing set.
- `skill-campaign-report` needs the record of what went live and when.

Retail ventures first (BARA, Keroma); the same loop serves any venture's channels, with the channel table below swapped for the venture's own.

## Behaviour

Four steps per action; the channel table below sets what each step means per channel.

1. **Confirm.** The content is approved (filed and reviewed, per `skill-content-studio`), maps to a named calendar slot, and names the KPI it moves in `convention-retail` vocabulary. The channel is one the venture's strategy has opened. Anything failing this is handed back, not staged.
2. **Prepare.** Gather what the channel needs: the asset in the channel's spec (from Pixel via `skill-creative-brief`), the product or collection reference from the store (`convention-shopify` naming), the link, the alt text, the tags, the schedule. Check the product facts against the store at the moment of staging, not from the draft.
3. **Stage and hand over.** Put the action on the channel via its connector in a staged state — scheduled, draft, unpublished, inactive — and hand the release to the operator with one line stating what will happen when released. Where the channel has no connector wired, produce a ready-to-paste pack (copy, asset, settings, schedule) and say plainly that the action is manual.
4. **Record.** Log what went live, where, when, and against which slot and KPI, in the venture's project, so `skill-campaign-report` can attribute it. An unrecorded action is invisible to measurement and did not happen.

## The channels

Channel selection is `convention-retail`'s and `skill-retail-strategy`'s; this table is what running each one requires. Where a row names a spec as a working rule, the Owner can strike it.

| Channel | Needs from Pixel | Needs from the store | Human action |
| -- | -- | -- | -- |
| **Shopify DTC store and sales channels** | Homepage and collection banners per `standard-storefront`; PDP imagery minimum set. | Products and collections named per `convention-shopify`; sales channels (Shop app, Google, Meta, Pinterest) enabled with the catalogue synced; policies attached. | Price changes, discount codes, going live, theme publish. Theme changes are Forge's via the repo, never the connector. |
| **Email** | Newsletter template; flow templates. | Customer list and consent; product data. | A full-list send. Operated through `skill-newsletter-strategy` (editorial) and `skill-lifecycle` (flows); this skill stages the send and records it. |
| **Instagram** (organic and shop) | Posts and stories in the brand's imagery direction; working rule 4:5 feed, 9:16 story, carousel of three to five for a range. | Catalogue via the Facebook/Meta sales channel for product tags. | Paid boosts and ads; any collaboration or giveaway terms. |
| **Pinterest** (organic and shop) | Tall pins, working rule 2:3, one product or ritual per pin, text overlay only where it reads at thumbnail. | Product feed via the Pinterest sales channel; collections mapped to boards. | Paid promotion. Pinterest is also a search surface — pin titles and descriptions follow `skill-seo-discovery`. |
| **TikTok** | Short vertical video; process and maker content over product-on-white. Reach briefs, Pixel or the operator shoots. | TikTok sales channel only once the catalogue is stable and the cadence exists. | Paid promotion; any creator agreement. Do not open at 0→1 without a posting cadence the operator can keep. |
| **Marketplaces** (Etsy, Not On The High Street, or the craft equivalent) | Listing imagery to the marketplace's spec, consistent with the store's packshots. | Listing copy from the store's product data, adapted to the marketplace's search (`skill-seo-discovery`); stock kept in step with Shopify. | Opening the shop, fees, pricing, promotions. Marketplaces are optional at 0→1 (`convention-retail`) and are never opened by a run. |

Email is the owned channel, so email revenue share is the number this skill's record most needs to make attributable; state the attribution model when recording.

## Connectors and what cannot be done without one

Each venture's connector set is recorded in its project (Shopify is wired for madebyneud/BARA; social, marketplace and email tooling are added as the operator wires them). The rule: **with a connector, stage; without one, pack.** A run never asks the operator for credentials, never scripts around a missing connector, and never reports a manual pack as a staged action. Where the same channel is repeatedly packed by hand, that is a config action to propose to the operator, not a workaround to keep running.

**A third case: a connector that is present but has no API surface for the action (APP-1641).** The rule above splits on whether a connector is wired, which settles the ordinary case and not this one — a connector can be wired, authenticated and working and still expose **no API surface for the action requested**. For that action it behaves exactly like no connector, so the rule reads **pack it, or route it to the browser-driven Admin route**, never "stage it". It is not a call to retry and not an approval to wait out: there is nothing to approve and nothing hangs. So a run establishes reachability from the connector's own tool set for the action in hand, not from the fact that the connector is listed as wired for the channel — and a pack produced for this reason is recorded as what it is, which the paragraph above already requires. Which Shopify surfaces are in this class, the two routes that do reach them, and why such a ticket is not Blocked are stated once in `convention-shopify` (*The connector-vs-theme split*, the third surface) and are deliberately not restated here. One difference from the sentence before this one: a channel repeatedly packed for *this* reason is not a config action to propose, because no wiring the operator can do reaches it — it is a platform limit, and proposing a connector for it wastes the proposal.

## Guardrails

- Never spends money, issues a discount, sends to a full list, publishes irreversibly or goes live without the operator's explicit release — the boundary in `convention-shopify` and `agent-reach`.
- Only acts on approved content that maps to a planned slot and a KPI; a good idea with no slot goes back to `skill-gtm-plan`.
- Operates channels the venture's stage has earned; opening a channel is a strategy decision, not an ops one.
- Product facts, prices and stock are read from the store at staging time; never invented (`convention-ticket`).
- Assets are Pixel's; copy is `skill-content-studio`'s; this skill produces neither.
- Records every live action for measurement; stays inside each venture's connector scope; no credentials in any record (`convention-secrets`).
- Propose-only to canon.

## Setup

Run on demand by Reach when an action is due, or on the campaign calendar. Connectors: Shopify (store-management), Linear, plus whichever social, marketplace or email connectors the venture has wired. Feeds `skill-campaign-report`; fed by `skill-gtm-plan`, `skill-launch-campaign`, `skill-newsletter-strategy`, `skill-lifecycle`. On finish, run skill-ops-retro capture on this run's friction: **search the Pulse queue first and add the evidence to a same-root note if one exists, otherwise file a new FRICTION note** for the drain pass to assess, in capture step 3's literal shape — team Apps, project os.Claude, `FRICTION:` title, labels `task` + `work:configuration` + `PUL-5E`, Backlog, unassigned — filing the friction, never the run report.

Owned by Reach (R3-ACH), run for the venture's operator.
