agentleFS
Sign inStart free
deciqAIdeciqAI/knowledge-skills/bullseye-traction-channels/SKILL.md

bullseye-traction-channels

Skill13 starsChanged 4 months agoMITView on GitHub

Activate when: a founder is guessing at marketing channels or pouring effort into one that isn't working; 'how do we get customers', 'which channel should we use', growth is stalled on distribution. Do NOT activate when: a channel is already proven and the task is to optimize/scale it, not to find one. More: deciqai.com/s/bullseye-traction-channels

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No repeatable customer-acquisition channel yet

    line 12
  2. Distinctive:

    Test to a pre-set success bar so results are decisive, not vibes.

    line 25
  3. Distinctive:

    No CAC/response threshold set before the test.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Bullseye — Find the One Traction Channel That Works

Overview

From Traction (Weinberg & Mares, 2014): most startups die from lack of distribution, not product, and they fail because they over-invest in one favored channel instead of systematically testing across all of them. The Bullseye framework cycles through 19 traction channels (SEO, content, paid, virality, sales, partnerships, community, PR, events, etc.), runs cheap tests, and concentrates on the one channel that is currently working.

When to Use

  • No repeatable customer-acquisition channel yet
  • Effort sunk into one channel out of habit/comfort
  • Reallocating a limited growth budget

The Process

  1. Brainstorm all 19 channels — a realistic idea for each, including ones you'd dismiss. Gate: skipping "unlikely" channels is how you miss the one that works.
  2. Rank into three rings: inner (promising now), middle (possible), outer (long shots).
  3. Run cheap parallel tests on the inner ring — small, time-boxed, with a target CAC/response bar defined up front.
  4. Read the data, not your preference — which test hit the bar?
  5. Pick one channel and focus — double down on the single working channel; ignore the rest for now. Gate: spreading across 3+ channels pre-fit = none get enough to work.
  6. Re-run when the channel saturates — channels decay; cycle Bullseye again.

Applying It Well

  • Test to a pre-set success bar so results are decisive, not vibes.
  • One working channel is usually enough to reach the next stage.
  • Founder bias toward a comfortable channel is the most common failure.

Red Flags

  • Committing to a channel before testing it.
  • "Doing a bit of everything" and nothing at scale.
  • No CAC/response threshold set before the test.

Verification

  • All 19 channels considered, ranked into three rings
  • Inner-ring tests run with a pre-set success bar
  • Decision made on data, not preference
  • Focus concentrated on the single working channel

Part of deciqAI Knowledge Skills — 253 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. See it run → https://www.deciqai.com/s/bullseye-traction-channels · Built by deciqAI · github.com/deciqAI · Contributions welcome.

Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/bullseye-traction-channels.json

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free