MAX-561, claude-plugins social package
+ +Prepared for MAX-561.
+ +Source pillar
+-
+
- Pillar ticket: MAX-555 +
- Canonical pillar URL: https://maxtechera.com/blog/claude-plugins-from-single-chatbot-to-real-operator-surface +
- Source repo: https://github.com/maxtechera/claude-plugins +
- Core proof points carried through the pack: +
- 9,000 Claude Code plugins in the market, Max runs 9.
+ - 47 /review runs last week.
- 40+ plugins tested in Q1.
+- A blog-to-published chain that dropped from most of an afternoon to about 70 minutes.
+-
+
- Audience split: 40% developers, 35% builders, 25% founders. +
- Primary reach bias: builders for reach, developers for stars and installs. +
Message spine
+-
+
- Category pain: most Claude workflows still feel like chat, not an operator surface. +
- Point of view: curated plugins beat plugin hoarding. +
- Product promise: `claude-plugins` turns Claude from isolated chat into a real working surface. +
- Credibility: Max tested 40+ plugins in Q1, cut the stack to 9 daily drivers, and uses them in real content and shipping loops. +
- Signature line: Mostrá receipts o callate. +
Hook waterfall, selected set
+ +-
+
- Primary: 9,000 Claude Code plugins. I still run 9. Acá está el filtro. +
- Alternate 1: Claude no necesitaba más prompts. Necesitaba mejores superficies. +
- Alternate 2: Probé 40+ plugins para dejar de perder contexto-window budget en boludeces. +
- STEPPS: 4/6 +
- Value Equation: 8.7/10 +
TikTok
+-
+
- Primary: Si tu Claude sigue siendo solo chat, te falta una superficie operativa. +
- Alternate 1: El problema no era instalar más plugins. Era elegir menos. +
- Alternate 2: Esto me ahorró una tarde entera de prueba y error con Claude Code. +
- STEPPS: 4/6 +
- Value Equation: 8.4/10 +
X
+-
+
- Primary: 9,000 plugins in the market. I kept 9. The delete list mattered more than the install list. +
- Alternate 1: The unlock was not more prompts. It was better operator surfaces. +
- Alternate 2: If your Claude stack feels noisy, your plugin list is probably the bug. +
- STEPPS: 4/6 +
- Value Equation: 8.8/10 +
-
+
- Primary: The highest leverage Claude Code decision I made this quarter was uninstalling most of my plugins. +
- Alternate 1: Curated plugin stacks beat plugin abundance. +
- Alternate 2: The operator surface is becoming the real product layer in AI workflows. +
- STEPPS: 3/6 +
- Value Equation: 8.2/10 +
---
+ +Asset 1, Instagram Reel, 45 to 60 seconds
+Primary CTA: GitHub stars
+Link: https://github.com/maxtechera/claude-plugins?utm_source=instagram&utm_campaign=claude-plugins-launch
+ +Hook, 0 to 3s
+On-screen: 9,000 Claude Code plugins. I kept 9.
VO: 9,000 Claude Code plugins. Yo me quedé con 9.
+ +Stakes, 3 to 6s
+On-screen: More plugins != better workflow
VO: Porque más plugins no te dan mejor workflow. Te dan ruido, overlap y menos foco.
+ +Credibility, 6 to 8s
+On-screen: 40+ tested in Q1 | 47 review runs last week
VO: En Q1 probé más de 40. La semana pasada corrí 47 /review runs con mi stack real.
Promise, 8 to 10s
+On-screen: Curated stack > plugin hoarding
VO: La ganancia vino cuando dejé de acumular y empecé a curar.
+ +Body, 10 to 40s
+VO: El problema no es tener más prompts. Es darle a Claude mejores superficies de acción.
+dev-essentials me limpia el loop técnico.
content-creator me acelera el blog-to-social chain.
hormozi me baja ideas de oferta y hooks sin salir del flujo.
El resultado no fue más output. Fue menos fricción, menos context-window budget desperdiciado y un daily driver stack que sí uso todos los días.
+ +Close, 40 to 52s
+VO: Si estás instalando todo lo que aparece en marketplaces, hacé la inversa. Elegí menos. Elegí mejor. Mostrá receipts o callate.
+ +CTA, 52 to 60s
+On-screen: Star the repo, steal the stack
VO: Dejé el repo en el link. Dale una estrella y robate el stack.
+ +Caption
+9,000 plugins en el mercado. Yo dejé 9 porque el problema no era falta de opciones, era falta de criterio.
+ +Si usás Claude Code para trabajo real, te conviene una pila chica, opinionated y con receipts.
+ +Repo: https://github.com/maxtechera/claude-plugins?utm_source=instagram&utm_campaign=claude-plugins-launch
+ +Comentá STACK si querés que suba el breakdown de los 9.
---
+ +Asset 2, Instagram Carousel, 9 slides
+Primary CTA: GitHub stars
+Link: https://github.com/maxtechera/claude-plugins?utm_source=instagram&utm_campaign=claude-plugins-launch
+ +Slide 1
+9,000 Claude Code plugins.
+I kept 9.
+ +Slide 2
+Más opciones no te dan mejor sistema.
+Muchas veces te dan más ruido.
+ +Slide 3
+Mi criterio cambió cuando dejé de pensar en plugins como hacks sueltos.
+ +Slide 4
+Empecé a mirarlos como operator surfaces.
+Si no mejoran una superficie real, afuera.
+ +Slide 5
+Probé 40+ en Q1.
+La mayoría duplicaba funciones, agregaba fricción o rompía foco.
+ +Slide 6
+Los 3 que más empujan mi stack hoy:
+-
+
- dev-essentials +
- content-creator +
- hormozi +
Slide 7
+Receipts: 47 /review runs la semana pasada y un chain de blog a publish en ~70 min, no una tarde entera.
Slide 8
+Curated beats bulk.
+Opinionated beats infinite choice.
+ +Slide 9, Salty Pretzel CTA
+No necesitas otro plugin dump.
+Necesitás un stack que gane horas.
+👉 Dale estrella al repo y llevate el filtro.
+ +Carousel caption
+No armé claude-plugins para tener una colección linda.
Lo armé para dejar de probar cosas que no sobrevivían una semana de uso real.
+ +Si querés ver qué entró, qué salió y por qué, arrancá por el repo.
+ +https://github.com/maxtechera/claude-plugins?utm_source=instagram&utm_campaign=claude-plugins-launch
+ +---
+ +Asset 3, Instagram Stories, 3-frame sequence
+Primary CTA: GitHub stars
+Link: https://github.com/maxtechera/claude-plugins?utm_source=instagram&utm_campaign=claude-plugins-launch
+ +Story 1
+Text: 9,000 plugins out there. I use 9.
Poll: Curated stack > big stack? Yes / Obvio
Story 2
+Text: Probé 40+ en Q1. Muchos eran ruido con branding.
Sticker: 47 review runs last week.
Story 3
+Text: Si querés el stack real, está en GitHub.
CTA: Tap for repo.
---
+ +Asset 4, TikTok script, 35 to 45 seconds
+Primary CTA: GitHub stars
+Link: https://github.com/maxtechera/claude-plugins?utm_source=tiktok&utm_campaign=claude-plugins-launch
+ +Script
+Si tu Claude sigue siendo solo chat, te falta una superficie operativa.
+ +Yo cometí el error clásico. Empecé a instalar plugins como si más cantidad fuera más leverage.
+No era así.
+ +Después de probar más de 40 en Q1, me quedé con 9 daily drivers.
+Los demás me comían contexto, duplicaban cosas o metían fricción.
+ +Ahí entendí la regla: curated stack beats plugin hoarding.
+ +dev-essentials para trabajo técnico.
content-creator para multiplicar contenido.
hormozi para hooks y offers sin cortar el flujo.
Eso me cambió el loop. Menos ruido, más shipping.
+ +Si querés copiar el stack, dejé el repo abajo.
+ +TikTok caption
+No te falta otro plugin. Te falta un filtro.
+ +Repo: https://github.com/maxtechera/claude-plugins?utm_source=tiktok&utm_campaign=claude-plugins-launch
+ +TikTok hook variants
+1. Si tu Claude sigue siendo solo chat, estás usando mal los plugins.
+2. Me cansé de instalar plugins que duraban menos de una semana.
+3. Probé 40+ para quedarme con 9. Ese ratio fue la lección.
+ +---
+ +Asset 5, X thread, 7 posts
+Primary CTA: GitHub stars
+Link: https://github.com/maxtechera/claude-plugins?utm_source=x&utm_campaign=claude-plugins-launch
+ +1. 9,000 Claude Code plugins in the market. I kept 9.
+ +That ended up being the real lesson.
+ +2. I thought the win would come from installing more.
+Instead, most of the gains came from deleting overlap, noise, and stuff that burned context-window budget.
+ +3. In Q1 I tested 40+ plugins.
+Most were fine in isolation.
+Very few survived a real week of daily use.
+ +4. The filter I use now is simple:
+if it does not improve a real operator surface, it is out.
+ +5. Three that stayed in heavy rotation:
+-
+
- `dev-essentials` +
- `content-creator` +
- `hormozi` +
Technical flow, content multiplication, and offer/hook work, without leaving Claude.
+ +6. Receipts:
+47 /review runs last week.
A blog-to-published chain that dropped to ~70 min instead of eating most of an afternoon.
+ +7. If your Claude stack feels noisy, your plugin list is probably the bug.
+ +Repo:
+https://github.com/maxtechera/claude-plugins?utm_source=x&utm_campaign=claude-plugins-launch
+ +Mostrá receipts o callate.
+ +Screenshot receipt notes for thread media
+-
+
- Tweet 3 image: screenshot of repo README plugin table. +
- Tweet 5 image: screenshot or code crop showing install commands for the 3 anchor plugins. +
- Tweet 6 image: terminal crop or metrics card with 47 `/review` runs and 70-minute chain note. +
---
+ +Asset 6, X single post
+Primary CTA: GitHub stars
+Link: https://github.com/maxtechera/claude-plugins?utm_source=x&utm_campaign=claude-plugins-launch
+ +9,000 plugins in the market.
+I use 9.
+ +The delete list mattered more than the install list.
+ +Curated stack > plugin abundance.
+ +https://github.com/maxtechera/claude-plugins?utm_source=x&utm_campaign=claude-plugins-launch
+ +---
+ +Asset 7, LinkedIn post, under 1,300 chars
+Primary CTA: newsletter in comments
+Body link rule: no link in body
+Comments link: https://maxtechera.com/newsletter?utm_source=linkedin&utm_campaign=claude-plugins-launch
+ +The highest leverage Claude Code decision I made this quarter was uninstalling most of my plugins.
+ +I tested 40+ in Q1.
+I kept 9.
+ +That sounds like a tooling story, but it is really an operating model story.
+ +A lot of teams still treat AI tooling like feature collection.
+More plugins. More prompts. More choices.
+ +In practice, that usually creates overlap, friction, and more context-window budget burned on things that never become daily drivers.
+ +What worked better for me was a stricter filter:
+ +If a plugin does not improve a real operator surface, it is out.
+ +That left me with a small stack I actually use for technical work, content multiplication, and offer development.
+ +The payoff was not theoretical.
+Last week alone, that stack supported 47 /review runs and a much faster blog-to-publish chain.
Curated stacks beat plugin abundance.
+Opinionated workflows beat plugin tourism.
+ +If you want the deeper operator-surface breakdown, I dropped the newsletter link in the first comment.
+ +---
+ +Asset 8, LinkedIn comment CTA
+If you want the operator-surface breakdown and the exact stack, acá va:
+https://maxtechera.com/newsletter?utm_source=linkedin&utm_campaign=claude-plugins-launch
+ +---
+ +Asset 9, YouTube Short, 45 to 60 seconds
+Primary CTA: GitHub stars
+Link: https://github.com/maxtechera/claude-plugins?utm_source=youtube&utm_campaign=claude-plugins-launch
+ +Script
+9,000 Claude Code plugins exist right now.
+I use 9.
+ +And honestly, the unlock was not finding more.
+It was uninstalling most of them.
+ +I tested 40+ plugins in Q1 and filtered them by one rule:
+if the plugin did not improve a real operator surface, it was out.
+ +That left me with a stack I actually use.
+Technical work with dev-essentials.
Content flow with content-creator.
Offer and hook work with hormozi.
The result was less context waste, less plugin overlap, and faster real work.
+ +If your Claude setup feels noisy, your plugin list might be the problem.
+Repo is below.
+ +Short title
+9,000 Claude plugins, I kept 9
+ +Short description
+I tested 40+ Claude Code plugins in Q1 and kept 9 daily drivers.
+Repo: https://github.com/maxtechera/claude-plugins?utm_source=youtube&utm_campaign=claude-plugins-launch
+ +---
+ +Asset 10, YouTube long-form derivative package
+Primary CTA: GitHub stars
+Link: https://github.com/maxtechera/claude-plugins?utm_source=youtube&utm_campaign=claude-plugins-launch
+ +Title options
+1. I Tested 40+ Claude Plugins and Kept 9
+2. 9,000 Claude Plugins Later, This Is My Real Stack
+3. Why I Uninstalled Most of My Claude Plugins
+ +Description
+I spent Q1 testing more than 40 Claude Code plugins and ended up with a much smaller conclusion: the real leverage came from a curated daily-driver stack, not plugin abundance.
+ +In this video I break down the filter, the delete list, the 3 plugins that stayed in heavy rotation, and the receipts behind the workflow.
+ +Repo:
+https://github.com/maxtechera/claude-plugins?utm_source=youtube&utm_campaign=claude-plugins-launch
+ +Pillar post:
+https://maxtechera.com/blog/claude-plugins-from-single-chatbot-to-real-operator-surface?utm_source=youtube&utm_campaign=claude-plugins-launch
+ +Chapters
+00:00 The 9,000-plugin problem
+00:38 Why most plugins do not survive real work
+02:10 The operator-surface filter
+04:25 The 3 plugins that stayed
+06:15 Receipts, 47 review runs and the 70-minute chain
+07:35 How to build your own curated stack
+ +---
+ +Asset 11, Newsletter feature block for NODO
+Primary CTA: newsletter signup / read-more path
+Link: https://maxtechera.com/blog/claude-plugins-from-single-chatbot-to-real-operator-surface?utm_source=newsletter&utm_campaign=claude-plugins-launch
+ +Subject options
+1. 9,000 Claude plugins, I kept 9
+2. The operator-surface filter I use for Claude
+3. I uninstalled most of my Claude plugins
+ +Preview text
+The delete list mattered more than the install list.
+ +Feature block
+I spent Q1 testing 40+ Claude Code plugins and ended up with a smaller, more useful conclusion.
+ +The win was not more plugins.
+It was a curated operator stack that actually survives daily use.
+ +In the new piece, I break down the filter I use, the 3 plugins that stayed in heavy rotation, and the receipts behind the stack.
+ +Read the full breakdown:
+https://maxtechera.com/blog/claude-plugins-from-single-chatbot-to-real-operator-surface?utm_source=newsletter&utm_campaign=claude-plugins-launch
+ +---
+ +Asset 12, Email HTML preview snippet
+
+<section style="font-family:Inter,Arial,sans-serif;padding:32px;background:#0b0b0f;color:#f5f5f7;border-radius:20px;max-width:640px;margin:0 auto;">
+ <p style="font-size:12px;letter-spacing:.12em;text-transform:uppercase;color:#8b8fa3;margin:0 0 12px;">NODO feature</p>
+ <h2 style="font-size:32px;line-height:1.1;margin:0 0 16px;">9,000 Claude plugins, I kept 9</h2>
+ <p style="font-size:18px;line-height:1.6;color:#d6d6dc;margin:0 0 16px;">I tested 40+ Claude Code plugins in Q1 and learned that the delete list mattered more than the install list.</p>
+ <p style="font-size:16px;line-height:1.6;color:#d6d6dc;margin:0 0 24px;">This breakdown covers the operator-surface filter, the 3 plugins that survived real work, and the receipts behind the stack.</p>
+ <a href="https://maxtechera.com/blog/claude-plugins-from-single-chatbot-to-real-operator-surface?utm_source=newsletter&utm_campaign=claude-plugins-launch" style="display:inline-block;background:#f97316;color:#fff;text-decoration:none;padding:14px 18px;border-radius:999px;font-weight:700;">Read the full breakdown</a>
+</section>
+---
+ +Asset 13, HeyGen-ready avatar notes
+-
+
- Framing: medium close-up, dark background, terminal b-roll cutaways. +
- Delivery: direct, advisory, a little spicy, one Spanglish line in the opener. +
- Open on: `9,000 Claude Code plugins. Yo me quedé con 9.` +
- Visual beats: +
1. plugin marketplace overload visual
+2. repo README table crop
+3. install commands for 3 anchor plugins
+4. 47 review runs / 70-minute chain receipt card
+5. repo CTA card
+-
+
- Subtitle style: large white captions, orange highlight on `9`, `40+`, `47`, `70 min`. +
---
+ +Asset 14, CTA variants
+1. GitHub stars: Star the repo and steal the stack.
+2. Newsletter signup: If you want the operator-surface breakdown, sumate a NODO.
+3. Reply keyword: Comentá `STACK` and I’ll turn this into a public teardown.
+ +---
+ +Asset 15, Standalone hooks for future posts
+1. Curated stacks beat plugin abundance.
+2. The delete list mattered more than the install list.
+3. If your Claude setup feels noisy, your plugin list is probably the bug.
+4. Most plugins are fine in demos. Very few survive a real week.
+5. Claude did not need more prompts. It needed better surfaces.
+ +---
+ +Asset 16, Republish variants
+ +Instagram, short
+Probé 40+ plugins. Me quedé con 9. El filtro cambió todo.
+ +Instagram, medium
+La mayoría de los plugins no fallan porque sean malos. Fallan porque no sobreviven uso real. En Q1 probé 40+ y hoy sigo usando 9.
+ +LinkedIn, long
+The more I work with Claude Code, the less I believe in plugin accumulation as a strategy. The practical advantage came from curation, from building a small stack that improves real surfaces of work instead of expanding option count. That shift produced better focus, less context waste, and better repeatability.
+ +---
+ +Asset 17, Draft autoscheduling plan
+-
+
- Monday 14:00 UTC, X thread +
- Tuesday 16:00 UTC, LinkedIn post + comment link +
- Wednesday 18:00 UTC, Instagram Reel +
- Thursday 18:00 UTC, Instagram Carousel +
- Friday 17:00 UTC, TikTok +
- Saturday 15:00 UTC, YouTube Short +
- Sunday 13:00 UTC, NODO feature block +
- Launch-day inbound prep: publish reply packs into notes before first post goes live +
---
+ +Asset 18, Comment reply packs
+ +Instagram, 5 replies
+1. Sí, la idea no es instalar más. Es quedarte con lo que sobrevive trabajo real.
+2. Si querés, después subo el breakdown completo de los 9 que sigo usando.
+3. Totalmente. Context-window budget también es presupuesto, aunque no lo miremos así.
+4. Ese fue mi error al principio también, demasiadas opciones, poco criterio.
+5. Repo acá: https://github.com/maxtechera/claude-plugins?utm_source=instagram&utm_campaign=claude-plugins-launch
+ +TikTok, 5 replies
+1. La clave fue borrar más de lo que instalé.
+2. Plugin tourism mata foco, mal.
+3. Si querés la lista exacta, la dejo en el repo.
+4. El filtro fue operador surface, no novelty.
+5. Repo: https://github.com/maxtechera/claude-plugins?utm_source=tiktok&utm_campaign=claude-plugins-launch
+ +X, 5 replies
+1. The delete list was honestly the harder part.
+2. Most plugins were fine, just not daily-driver good.
+3. Operator surface became the filter.
+4. If you want the full reasoning, the pillar post goes deeper.
+5. Repo: https://github.com/maxtechera/claude-plugins?utm_source=x&utm_campaign=claude-plugins-launch
+ +LinkedIn, 5 replies
+1. The interesting shift was treating plugin choice as workflow design, not feature collection.
+2. I underestimated how much overlap was costing in attention.
+3. The curated stack is smaller than most people expect.
+4. Happy to post the exact filter if useful.
+5. Newsletter comment link is above if you want the deeper operator-surface breakdown.
+ +YouTube, 5 replies
+1. Most of the gains came from uninstalling, which surprised me too.
+2. The 3 anchors are doing very different jobs in the workflow.
+3. If the setup feels noisy, reduce before you add.
+4. The repo is in the description if you want the stack.
+5. I’ll probably do a full video on the delete criteria next.
+ +---
+ +Acceptance criteria coverage map
+-
+
- Pillar source linked and referenced in derivatives: yes, canonical URL included and newsletter/YouTube reference the pillar directly. +
- 15+ assets: yes, 18 packaged items above. +
- Per-platform hooks: yes, with 1 primary + 2 alternates for IG, TikTok, X, LinkedIn. +
- Natural writing pass: plain language, contractions, varied sentence length, zero generic AI filler. +
- Brand voice pass: direct voice, Spanglish moments, receipts, signature phrase. +
- Single CTA per asset: yes, each asset uses one primary CTA. +
- UTM tags: included on every outbound link. +
- STEPPS and Value Equation: scored above threshold on selected hooks. +
- Reel / carousel / X thread / LinkedIn / YouTube / newsletter / comment packs: included. +