why-did-this-post-flop
Diagnose Why a Post Flopped
A weak post can fail because it was not distributed, was seen and skipped, or asked for the wrong response. This skill uses available metrics, account baselines, and post structure to identify the likeliest failure and recommend one next change.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
Review the Skillstore skill "why-did-this-post-flop" from https://skillstore.io/skills/prateeks367-why-did-this-post-flop.md and its manifest at https://skillstore.io/api/skills/prateeks367-why-did-this-post-flop/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "why-did-this-post-flop". The post had 42 impressions, two reactions, and no comments. My usual posts receive about 500 impressions.
Resultado esperado:
Diagnosis: distribution failure. The low impressions explain the low engagement, so rewriting the opening line is unlikely to help first. Check timing, posting history, and whether the post synced correctly.
Usando "why-did-this-post-flop". The post had 1,200 impressions, 18 reactions, no comments, and normally gets 1,000 impressions with 15 reactions.
Resultado esperado:
- Diagnosis: the post performed normally for reach and reactions.
- The likely mismatch is the goal: it did not create comments.
- Next change: ask one specific question that invites a useful response.
Usando "why-did-this-post-flop". The post reached my usual audience, but people did not engage. The first line says, 'Some thoughts on leadership.'
Resultado esperado:
Diagnosis: readers likely saw the post but had little reason to continue. Test a specific first line that creates a clear reason to read the next sentence.
Auditoría de seguridad
SeguroAll six static findings are false positives. The flagged lines contain Markdown descriptions, post-diagnosis guidance, and ordinary headings; no shell execution or system reconnaissance is present.
Factores de riesgo
⚙️ Comandos externos (4)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/prateeks367-why-did-this-post-flop/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/prateeks367-why-did-this-post-flop?utm_source=security_passport_badge)Insignia HTML
<a href="https://skillstore.io/skills/prateeks367-why-did-this-post-flop?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/prateeks367-why-did-this-post-flop/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Tarjeta para insertar
<iframe src="https://skillstore.io/embed/skills/prateeks367-why-did-this-post-flop.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citas académicas (APA · BibTeX · CFF)
Cita APA
prateeks367. (2026). why-did-this-post-flop security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/prateeks367-why-did-this-post-flop/audits/1Cita BibTeX
@techreport{prateeks367-prateeks367-why-did-this-post-flop-2026,
author = {prateeks367},
title = {why-did-this-post-flop security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/prateeks367-why-did-this-post-flop/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "why-did-this-post-flop security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "prateeks367"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/prateeks367-why-did-this-post-flop/audits/1"
identifiers:
- type: other
value: "skillstore:prateeks367-why-did-this-post-flop:audit:1"
description: "Skillstore immutable audit report identifier"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
Review a disappointing launch
A solo creator provides one post and its metrics to identify whether reach, content, or the requested action limited results.
Coach a client on one weak post
A content consultant uses the post, account baseline, and comparison posts to give a focused diagnosis instead of a full rewrite.
Investigate a campaign outlier
A small marketing team compares one underperforming post with nearby posts and chooses one testable improvement.
Prueba estos prompts
Diagnose this post using its text and metrics. Separate distribution failure, low engagement after viewing, and a mismatch between engagement and my goal. Post: [paste]. Impressions: [number]. Reactions: [number]. Comments: [number]. Reposts: [number]. Goal: [goal].
Compare this post with my usual results and explain what the comparison rules out. Post: [paste]. Post metrics: [paste]. Typical metrics: [paste]. State what is known, what is uncertain, and the single most useful next change.
Analyze why this post underperformed on [platform]. Consider timing, recency, reply or repost status, outbound links, reach trend, opening line, specificity, and requested action. Use only the evidence provided, then rank the top two explanations.
Use the connected post, analytics baseline, nearby posts, and voice insights to diagnose this one underperforming post. Identify the failure type, cite the evidence, distinguish sync limitations from real results, and finish with one high-impact test.
Mejores prácticas
- Provide impressions and a personal baseline before asking for a diagnosis.
- State the desired outcome, such as comments, clicks, or qualified replies.
- Apply one recommended change and compare the next result with a similar baseline.
Evitar
- Do not ask for a hook rewrite before checking whether the post was distributed.
- Do not invent metrics, platform causes, or lessons from missing evidence.
- Do not apply six changes to one post when a single test would reveal more.
Preguntas frecuentes
What information should I provide?
Can this diagnose a post without impressions?
Does it review a whole account?
Can it explain low comments despite good reach?
Can it use VoiceMOAT data?
Will it rewrite my post?
Detalles del desarrollador
Autor
prateeks367Licencia
MIT
Revisión de Skillstore
r1
Aviso de versión
El autor no declaró una versión.
Ref.
5726d703fd79596f46a4232d911221f962d9af1d
Actualidad del mantenimiento
2/10/2026
Uso
0 descargas · 0 vistas
Estructura de archivos
📄 SKILL.md