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.

Obtenir le fichier de compétence Laissez les agents s’en charger
CATÉGORIE
Social & diffusion
FORMAT
employee-amplification-without-astroturf.md
ÉTAPES
7
PRIX
Gratuit — sans compte
QUAND S’EN SERVIR

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

Le fichier de compétence

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.

## Ce qu’il vous faut d’abord

- 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éthode

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.

## Ce que ça produit

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

## Là où ça dérape

- 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

---

Extrait de la bibliothèque de compétences QuQi - https://www.quqi.io/fr/skills/employee-amplification-without-astroturf
Téléchargement gratuit · sans compte, sans e-mail

Ce qu’il vous faut d’abord

  • 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éthode

  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.

Ce que ça produit

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

Là où ça dérape

  • 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

Utiliser cette compétence dans votre propre IA

Le fichier téléchargé est un simple markdown dont l'en-tête porte le nom et le déclencheur. Quand un assistant sait charger des compétences tout seul, c'est cet en-tête qu'il lit pour décider que celle-ci s'applique.

Claude Code Enregistrez-le sous ~/.claude/skills/employee-amplification-without-astroturf/SKILL.md et Claude le charge tout seul dès que ce que vous faites correspond au déclencheur. Placez-le plutôt dans .claude/skills d'un projet si toute l'équipe doit l'avoir.
Claude Importez le fichier dans la section compétences de vos réglages. Une fois là, il s'applique tout seul dans toute conversation où le déclencheur colle, sans que vous ayez à y penser.
ChatGPT Il n'existe pas de format de compétences où l'installer, alors collez le contenu du fichier dans les instructions d'un Projet ou d'un GPT personnalisé. Il s'applique ensuite à toutes les conversations du projet, pas seulement à celle où vous l'avez collé.
Tout le reste Collez le markdown dans la conversation avant votre question. Cela fonctionne avec n'importe quel assistant, il faut simplement le recoller à chaque fois.

Plus dans Social & diffusion