QuQi

Get Colleagues Sharing Without Astroturfing

Fifteen individual accounts reach far more people than one brand account, and the usual attempt to close that gap is a shared block of copy sent round for everyone to paste. Feeds detect near-identical posts from connected accounts within minutes and suppress all of them, and staff stop taking part after the second time they are asked to publish something they would not have written. The version that works hands people raw material and lets them write it themselves, which means giving up control of the wording.

Obter o ficheiro da competência Deixe os agentes tratar disso
CATEGORIA
Redes e distribuição
FORMATO
employee-amplification-without-astroturf.md
PASSOS
7
PREÇO
Grátis — sem conta
QUANDO USAR ISTO

Use when a company has staff with real audiences and every launch still reaches nobody beyond the brand account.

O ficheiro da competência

employee-amplification-without-astroturf.md
---
name: employee-amplification-without-astroturf
description: Use when a company has staff with real audiences and every launch still reaches nobody beyond the brand account.
---

# Get Colleagues Sharing Without Astroturfing

Fifteen individual accounts reach far more people than one brand account, and the usual attempt to close that gap is a shared block of copy sent round for everyone to paste. Feeds detect near-identical posts from connected accounts within minutes and suppress all of them, and staff stop taking part after the second time they are asked to publish something they would not have written. The version that works hands people raw material and lets them write it themselves, which means giving up control of the wording.

## O que precisa primeiro

- an honest list of who already posts voluntarily, which is not the org chart
- the piece plus three or four angles into it matched to different roles
- a clear written position from legal or comms on what staff may and may not say

## Método

1. Start with the four or five people who already post without being asked. Recruiting reluctant colleagues produces one dead post each and lasting resistance to the next request.
2. Give each person a different angle matched to why their audience follows them: the engineer gets the method, the salesperson gets the objection it answers, the founder gets the decision behind it.
3. Send raw material - the chart, the quote, the number - rather than finished copy, and say plainly that rewriting it in their own words is the point rather than a liberty.
4. Spread the posts across a week. Simultaneous posts from accounts that all list the same employer is precisely the pattern coordinated-behaviour detection is built to catch.
5. Keep participation optional and never report it as a performance measure, because the moment it is counted the posts turn into compliance text that nobody engages with.
6. Draw the line explicitly in writing: no staff reviews, no posing as a customer, no replying to each other as if unconnected. One screenshot of that costs more than every share is worth.
7. Tell each person what their post did afterwards. Seeing the reach is the only reason a colleague posts a second time.

## O que isto produz

A per-person angle sheet, a staggered posting week, and a written list of what the company will not ask staff to post.

## Onde isto corre mal

- circulating a copy-paste block, which gets the whole cluster demoted and reads as astroturf to anyone following two of you
- mandating participation, which produces posts that visibly nobody meant to write
- letting people post a bare link with no context, which performs worse than not posting at all

---

Da biblioteca de competências da QuQi - https://www.quqi.io/pt/skills/employee-amplification-without-astroturf
Transferência gratuita · sem conta, sem e-mail

O que precisa primeiro

  • an honest list of who already posts voluntarily, which is not the org chart
  • the piece plus three or four angles into it matched to different roles
  • a clear written position from legal or comms on what staff may and may not say

Método

  1. 01 Start with the four or five people who already post without being asked. Recruiting reluctant colleagues produces one dead post each and lasting resistance to the next request.
  2. 02 Give each person a different angle matched to why their audience follows them: the engineer gets the method, the salesperson gets the objection it answers, the founder gets the decision behind it.
  3. 03 Send raw material - the chart, the quote, the number - rather than finished copy, and say plainly that rewriting it in their own words is the point rather than a liberty.
  4. 04 Spread the posts across a week. Simultaneous posts from accounts that all list the same employer is precisely the pattern coordinated-behaviour detection is built to catch.
  5. 05 Keep participation optional and never report it as a performance measure, because the moment it is counted the posts turn into compliance text that nobody engages with.
  6. 06 Draw the line explicitly in writing: no staff reviews, no posing as a customer, no replying to each other as if unconnected. One screenshot of that costs more than every share is worth.
  7. 07 Tell each person what their post did afterwards. Seeing the reach is the only reason a colleague posts a second time.

O que isto produz

A per-person angle sheet, a staggered posting week, and a written list of what the company will not ask staff to post.

Onde isto corre mal

  • circulating a copy-paste block, which gets the whole cluster demoted and reads as astroturf to anyone following two of you
  • mandating participation, which produces posts that visibly nobody meant to write
  • letting people post a bare link with no context, which performs worse than not posting at all

Use esta skill na sua própria IA

O ficheiro é markdown simples, com o nome e o gatilho no frontmatter. Quando um assistente consegue carregar skills sozinho, é esse frontmatter que lê para decidir que esta se aplica.

Claude Code Guarde-a como ~/.claude/skills/employee-amplification-without-astroturf/SKILL.md e o Claude carrega-a sozinho quando o que está a fazer corresponde ao gatilho. Coloque-a em .claude/skills dentro de um projeto se toda a equipa a deve ter.
Claude Carregue o ficheiro na secção de skills das suas definições. A partir daí aplica-se sozinho em qualquer conversa onde o gatilho encaixe, sem ter de se lembrar dele.
ChatGPT Não existe um formato de skills onde a instalar, por isso cole o conteúdo do ficheiro nas instruções de um Projeto ou de um GPT personalizado. Passa então a aplicar-se a todas as conversas desse projeto e não só àquela onde o colou.
Qualquer outro Cole o markdown na conversa antes da sua pergunta. Funciona em qualquer assistente, só tem de ser colado de novo de cada vez.

Mais em Redes e distribuição