agentleFS
lorena-bordonaba-paulorena-bordonaba-pau/youtube-agent/.claude/skills/channel-identity/SKILL.md

channel-identity

Skill2 starsChanged 49 days agoMITView on GitHub

Channel positioning, differentiation against the competitive neighbourhood, and niche reframing. Triggered by "how do I position myself", "what makes me different", "where do I take the channel", "who is my real competition". In Spanish, "cómo me posiciono", "en qué me diferencio", "hacia dónde llevo el canal", "quién es mi competencia real".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Update memory/channel_positioning.md if the analysis changes something stable.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Identity and positioning

WHEN

Deciding how the channel positions itself, what sets it apart from the competitive neighbourhood, where to take the niche next, or who the real competition is. Not for a single video's packaging: that is packaging.

EXECUTION ORDER

  1. Where the channel is today python3 tools/yt_channel_stats.py
  2. What the real neighbourhood is python3 tools/yt_outliers_channels.py --min-ratio 1.5 With a low threshold, because here you want each channel's editorial pattern, not only its peaks.
  3. Who you are actually producing for
    python3 tools/yt_demographics.py --days 90
    python3 tools/yt_geography.py --days 90
    The contrast between the audience you think you have and the one you have is usually where the finding is.
  4. What people arrive with — a signal of perceived positioning python3 tools/yt_search_terms.py --days 180 The terms people search and find you with say how you are perceived, which is not always how you want to be positioned.
  5. Update memory/channel_positioning.md if the analysis changes something stable. Only if stable: one week of data does not reposition a channel.

SOURCES

Steps 1, 3 and 4 youtube_api. Step 2 derived.

OUTPUT

  • Current position, with figures and a date.
  • Neighbourhood: which channels occupy the same space and how they differ.
  • The concrete gap, with the evidence backing it.
  • What would change in the editorial line, and what must NOT be touched.

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.