技能 why-did-this-post-flop

📦

why-did-this-post-flop

Name: why-did-this-post-flop
Author: prateeks367

內容修訂 r1 安全 ⚙️ 外部命令

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.

支援: Claude Codex Code(CC)

🥉 78 銅級

Maintain this Skill? Claim it 🥉 78 銅級

使用我的智慧代理安裝

將此請求複製給你的智慧代理，其中包含權威 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.

你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。

Agent 可讀資源

當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。

Markdown 詳情 GET /skills/prateeks367-why-did-this-post-flop.md 已簽名 manifest GET /api/skills/prateeks367-why-did-this-post-flop/manifest 已簽名 lockfile GET /api/skills/prateeks367-why-did-this-post-flop/lockfile

測試它

正在使用「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.

安全審計

安全

v1 • 2026/10/2 開啟版本化報告

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)

SKILL.md:73 SKILL.md:75 SKILL.md:78 SKILL.md:80

最近一次完成的靜態與語意稽核未偵測到已確認的安全發現。這並不能證明該 Skill 沒有副作用。

審計單位: codex

分享與引用此報告

分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。

開啟版本化報告

複製報告連結

https://skillstore.io/skills/prateeks367-why-did-this-post-flop/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/prateeks367-why-did-this-post-flop/security.svg)](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/1

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"

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.

試試這些提示

Basic post diagnosis

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 with my normal results

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.

Review a platform-specific outlier

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 connected account evidence

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?

Provide the post text, impressions, reactions, comments, reposts, and what success meant for that post.

Can this diagnose a post without impressions?

It can review the writing, but it cannot separate distribution failure from content failure without impressions.

Does it review a whole account?

No. It focuses on one post and uses account context only when you provide a relevant baseline.

Can it explain low comments despite good reach?

Yes. It checks whether the post asked for a response and whether the request matched your goal.

Can it use VoiceMOAT data?

Yes, when connected. It can use post details, analytics, comparison posts, and voice insights, subject to sync freshness.

Will it rewrite my post?

Its primary purpose is diagnosis and one next change. You can request a rewrite after the failure type is clear.

開發者詳細資訊

作者

prateeks367

授權

MIT

Skillstore 修訂

版本提示

作者未聲明版本。

儲存庫

https://github.com/prateeks367/voicemoat-skills/tree/b1749d2bf583cf8c78baf246f6007522e8c052a2/skills/why-did-this-post-flop

引用

5726d703fd79596f46a4232d911221f962d9af1d

維護新鮮度

2026/10/2

使用量

0 次下載 · 0 次瀏覽

檔案結構

📄 SKILL.md