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.

Consigue el archivo de la habilidad Deja que lo lleven los agentes
CATEGORÍA
Redes y difusión
FORMATO
channel-portfolio-pruning.md
PASOS
7
PRECIO
Gratis, sin cuenta
CUÁNDO USAR ESTO

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

El archivo de la habilidad

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.

## Qué necesitas antes

- 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

## Método

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.

## Qué produce esto

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

## Dónde falla esto

- 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

---

De la biblioteca de habilidades de QuQi - https://www.quqi.io/es/skills/channel-portfolio-pruning
Descarga gratis · sin cuenta, sin correo

Qué necesitas antes

  • 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

Método

  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.

Qué produce esto

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

Dónde falla esto

  • 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

Usa esta skill en tu propia IA

El archivo es markdown simple, con el nombre y el disparador en su frontmatter. Cuando un asistente sabe cargar skills por su cuenta, es ese frontmatter lo que lee para decidir que esta le aplica.

Claude Code Guárdala como ~/.claude/skills/channel-portfolio-pruning/SKILL.md y Claude la carga solo cuando lo que haces coincide con el disparador. Ponla en .claude/skills dentro de un proyecto si la debe tener todo el equipo.
Claude Sube el archivo en la sección de skills de tus ajustes. Una vez ahí se aplica solo en cualquier conversación donde encaje el disparador, sin que tengas que acordarte.
ChatGPT No hay un formato de skills donde instalarla, así que pega el contenido del archivo en las instrucciones de un Proyecto o de un GPT personalizado. Así se aplica a todos los chats de ese proyecto y no solo a aquel donde lo pegaste.
Cualquier otro Pega el markdown en el chat antes de tu pregunta. Funciona en cualquier asistente, solo hay que volver a pegarlo cada vez.

Más en Redes y difusión