QuQi

Decide Which Channels To Stop

Effort spread thin across six platforms produces six weak presences, because every feed rewards concentration and ignores a trickle. Nobody prunes, partly because closing an account feels like discarding an asset and partly because the metric everyone checks - follower count - never goes down and therefore never signals a problem. The decision needs a measure of current return per hour, and it has to distinguish a channel that failed from one that was never actually run.

Get the skill file Let the agents run it
CATEGORY
Social & distribution
FORMAT
channel-portfolio-pruning.md
STEPS
7
PRICE
Free - no account
WHEN TO REACH FOR THIS

Use when you are maintaining accounts on five or six platforms, most of them barely, and cannot say which ones deserve the time.

The skill file

channel-portfolio-pruning.md
---
name: channel-portfolio-pruning
description: Use when you are maintaining accounts on five or six platforms, most of them barely, and cannot say which ones deserve the time.
---

# Decide Which Channels To Stop

Effort spread thin across six platforms produces six weak presences, because every feed rewards concentration and ignores a trickle. Nobody prunes, partly because closing an account feels like discarding an asset and partly because the metric everyone checks - follower count - never goes down and therefore never signals a problem. The decision needs a measure of current return per hour, and it has to distinguish a channel that failed from one that was never actually run.

## What you need first

- median reach and engagement per post per channel over the last six months, medians not means
- an honest estimate of hours per week each channel takes including replies and moderation
- what each channel has produced in real terms: enquiries, subscribers, links, hires, or nothing you can name

## Method

1. Put median reach per post and hours per week for each channel into one table. Leave follower count out of the decision entirely - it records a past that may have no bearing on who sees anything now.
2. Attribute outcomes as far back as you honestly can, and write unknown where you cannot rather than defaulting to zero or to a flattering guess.
3. Separate underperforming from under-invested. A platform you post to twice a month has never been tested, and cutting it tells you nothing about the platform.
4. Pick at most two channels to run properly. Everything else moves to one of three states: parked with a pinned post pointing elsewhere, kept as a claimed handle with no posting, or deleted.
5. Before deleting anything, weigh what the profile does for your identity footprint - profiles are used to confirm who a company is, and a dormant but complete profile is usually worth more than a removed one. Practitioners disagree here, so decide it per handle rather than as a rule.
6. Name in writing where the freed hours go. A prune that does not reassign the time becomes less work rather than better work, and quietly reverses within a quarter.
7. Set a revisit date six months out with a pre-agreed condition for restarting a parked channel, so the decision can be reversed on evidence instead of on someone's enthusiasm.

## What this produces

A channel table with median reach, hours and named outcomes, and a keep, park or delete decision per channel with a revisit date.

## Where this goes wrong

- keeping a channel because the follower number is large, when median reach shows almost none of them see anything
- deleting rather than parking, which gives up a claimed handle and a profile that helps confirm your identity elsewhere
- cutting a channel you never genuinely ran, then concluding the platform does not work for your market

---

From the QuQi skill library - https://www.quqi.io/skills/channel-portfolio-pruning
Free to download · no account, no email

What you need first

  • median reach and engagement per post per channel over the last six months, medians not means
  • an honest estimate of hours per week each channel takes including replies and moderation
  • what each channel has produced in real terms: enquiries, subscribers, links, hires, or nothing you can name

Method

  1. 01 Put median reach per post and hours per week for each channel into one table. Leave follower count out of the decision entirely - it records a past that may have no bearing on who sees anything now.
  2. 02 Attribute outcomes as far back as you honestly can, and write unknown where you cannot rather than defaulting to zero or to a flattering guess.
  3. 03 Separate underperforming from under-invested. A platform you post to twice a month has never been tested, and cutting it tells you nothing about the platform.
  4. 04 Pick at most two channels to run properly. Everything else moves to one of three states: parked with a pinned post pointing elsewhere, kept as a claimed handle with no posting, or deleted.
  5. 05 Before deleting anything, weigh what the profile does for your identity footprint - profiles are used to confirm who a company is, and a dormant but complete profile is usually worth more than a removed one. Practitioners disagree here, so decide it per handle rather than as a rule.
  6. 06 Name in writing where the freed hours go. A prune that does not reassign the time becomes less work rather than better work, and quietly reverses within a quarter.
  7. 07 Set a revisit date six months out with a pre-agreed condition for restarting a parked channel, so the decision can be reversed on evidence instead of on someone's enthusiasm.

What this produces

A channel table with median reach, hours and named outcomes, and a keep, park or delete decision per channel with a revisit date.

Where this goes wrong

  • keeping a channel because the follower number is large, when median reach shows almost none of them see anything
  • deleting rather than parking, which gives up a claimed handle and a profile that helps confirm your identity elsewhere
  • cutting a channel you never genuinely ran, then concluding the platform does not work for your market

Use this skill in your own AI

The download is a plain markdown file with the name and trigger in its frontmatter. Where an assistant supports skills it can load itself, that frontmatter is what it reads to decide this one applies.

Claude Code Save it as ~/.claude/skills/channel-portfolio-pruning/SKILL.md and Claude loads it on its own when what you are doing matches the trigger line. Put it in .claude/skills inside a project instead if the whole team should have it.
Claude Upload the file in the skills section of your settings. Once it is there it applies itself in any conversation where the trigger fits, so you do not have to remember it exists.
ChatGPT There is no skills format to install into, so paste the file contents into a Project instruction or a Custom GPT instead. It then applies to every chat in that project rather than only the one you paste it into.
Anything else Paste the markdown into the chat before your question. It works in any assistant, it just has to be pasted again each time.

Questions about this skill

When should I prune rather than keep every channel ticking over?

When you maintain five or six accounts, most of them barely, and cannot say which deserve the hours. The metric everyone checks, follower count, never falls and so never signals a problem. Every feed rewards concentration and ignores a trickle, so the real question is which two channels you will run properly, not which to add next.

What do I need in hand before deciding?

Median reach and engagement per post per channel across six months, medians not means, honest hours per week including replies and moderation, and what each channel has produced in real terms. Six months of post-level data is the threshold: below it you cannot separate a channel that failed from one you posted to twice a month and never actually tested.

What do I end up with?

A channel table showing median reach, hours and named outcomes, with a keep, park or delete verdict and a revisit date carrying a pre-agreed restart condition. The verdict and that condition are what get used. Write unknown where you cannot attribute an outcome rather than defaulting to zero, which ends the argument on a number you made up.

What ruins this most often?

Cutting a channel you never genuinely ran, then concluding the platform does not work for your market, which closes off a route for years. Deleting rather than parking is the other one, since a dormant but complete profile helps confirm who you are elsewhere. Practitioners disagree on that, so decide it per handle rather than as a rule.

More in Social & distribution