Borrowing it
Nothing to install: this file belongs to LeanOS-Technologies/strategy-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LeanOS-Technologies/strategy-os/main/.claude/skills/stg-designing-channels/SKILL.mdgit clone --depth 1 https://github.com/LeanOS-Technologies/strategy-osWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/leanos-technologies/strategy-os/stg-designing-channels)<a href="https://agentmods.dev/skills/leanos-technologies/strategy-os/stg-designing-channels"><img src="https://agentmods.dev/badge/skills/leanos-technologies/strategy-os/stg-designing-channels/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/leanos-technologies/strategy-os/stg-designing-channels"><img src="https://agentmods.dev/badge/skills/leanos-technologies/strategy-os/stg-designing-channels.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00056 | $0.02365 |
| Opus 5 | $0.00028 | $0.01182 |
| Sonnet 5 | $0.00011 | $0.00473 |
| Haiku 4.5 | $0.00006 | $0.00236 |
Grade A, and why
stg-designing-channels scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Channel Strategy Design
Select GTM acquisition channels, estimate per-channel CAC, design channel mix with investment allocation, and sequence channels by phase. Constrained by ACV-channel viability from pricing and growth architecture from solutions.
Procedure
Step 1: Load Constraints [S]
Read upstream outputs:
- ACV-channel constraint from stg-designing-pricing Step 4 (< $1K: zero-touch only; $1K-$10K: light-touch; > $10K: sales-assisted viable)
- Growth architecture from stg-designing-solutions Step 2 (PLG/Network/Traditional/Hybrid)
- Growth loops from stg-designing-solutions Step 6
- Segment characteristics from stg-segmenting-customers (where they gather, observable filters)
- Competitor channels from stg-analyzing-competition
- Pricing tier structure from stg-designing-pricing Step 4
- Mode (VENTURE/BOOTSTRAP/HYBRID) from governor
Assemble constraint summary with sources.
Gate: constraints_loaded: bool -- ACV-channel constraint, growth architecture, and segment characteristics all available.
- Pass: Step 2.
- Fail: If ACV-channel constraint missing, derive from ARPU range (ARPU x 12 = rough ACV). If growth architecture missing, infer from ACV and buyer type with reduced confidence. Flag missing upstream outputs.
Step 2: Enumerate Candidate Channels [K-grounded]
Grounded in: segment characteristics, growth architecture, competitor channels.
Enumerate 5-8 candidate channels. For each, state the specific mechanism by which it reaches the segment.
Channel taxonomy:
| Category | Channels | Typical ACV Fit |
|---|---|---|
| Zero-touch | SEO/content, product-led viral, community/open-source, marketplace listings | < $5K |
| Light-touch | Paid search (SEM), paid social, webinars, developer communities, email outreach, partnerships/integrations | $1K-$25K |
| Sales-assisted | Outbound sales (SDR/AE), events/conferences, channel partners, analyst relations | > $10K |
For each candidate:
- Mechanism: How this channel reaches the target segment SPECIFICALLY. "Content marketing" is not a mechanism. "Technical blog posts targeting [segment role] searching for [problem-related queries]" is a mechanism.
- Segment fit: Why this channel reaches this segment (cite segment characteristics).
- Competitor presence: Are competitors using this channel? (from competitive analysis).
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 201 lines · 56 tokens per session scan A 915b984549de
stg-designing-channels is a skill published in the GitHub repository LeanOS-Technologies/strategy-os (38 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 2,365 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
email-sequence
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," or "lifecycle…
qa-test-planner
Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.
gepetto
Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
guidance
Control LLM output with regex and grammars, guarantee valid JSON/XML/code generation, enforce structured formats, and build multi-step workflows with Guidance - Microsoft Research's constrained generation framework.
content-research-writer
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.