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.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「why-did-this-post-flop」を使用しています。 The post had 42 impressions, two reactions, and no comments. My usual posts receive about 500 impressions.
期待される結果:
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.
「why-did-this-post-flop」を使用しています。 The post had 1,200 impressions, 18 reactions, no comments, and normally gets 1,000 impressions with 15 reactions.
期待される結果:
- 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.
「why-did-this-post-flop」を使用しています。 The post reached my usual audience, but people did not engage. The first line says, 'Some thoughts on leadership.'
期待される結果:
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.
セキュリティ監査
安全All 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.
リスク要因
⚙️ 外部コマンド (4)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/prateeks367-why-did-this-post-flop/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/prateeks367-why-did-this-post-flop?utm_source=security_passport_badge)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>埋め込みカード
<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>学術引用 (APA · BibTeX · CFF)
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/1BibTeX形式の引用
@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"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
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.
これらのプロンプトを試す
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.
ベストプラクティス
- 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.
回避
- 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.
よくある質問
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?
開発者情報
作成者
prateeks367ライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
5726d703fd79596f46a4232d911221f962d9af1d
メンテナンスの新しさ
2026/10/2
利用状況
0 ダウンロード · 0 閲覧
ファイル構成
📄 SKILL.md