mcpField
S
share

share

github.com/serhiikorniienkoMarketing & growth16074 installsUpdated 4w ago
Repository

About share

A marketing skill that turns a finished report into platform-specific, ready-to-post content. It follows each platform’s format and link requirements, and can also create carousel assets from a report.

Key features

  1. 01Create platform-native posts from a report
  2. 02Follow platform-specific length and link rules
  3. 03Generate carousel slide data from findings
  4. 04Render slides as images and a PDF

Use cases

  1. 01Adapt a report for X and LinkedIn
  2. 02Turn selected report findings into carousel slides

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/serhiikorniienko/bullshit-detector --skill share

After installing, type/sharein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

PLATFORMS.md
VERSION
scripts/
render_carousel.py

Details

From the project README

share

Take a finished report and produce platform-native content, ready to paste. Nothing generic: each platform gets its own format, length, and link etiquette.

Workflow

  1. Locate the report. A file the user points at, the report from this conversation, or — if there is none — offer to run the bullshit-detector skill first.
  2. Ask which platforms if not stated. Default set: X thread + LinkedIn post.
  3. Write the posts following the per-platform specs in PLATFORMS.md exactly — hooks, length limits, link placement. Output each as a separate fenced block the user can copy verbatim.
  4. Carousel (if requested or if the platform benefits): extract the report into a slides.json (schema below) and render:
uv run <this-skill-dir>/scripts/render_carousel.py slides.json -o carousel/

First run needs a one-time browser install: uv run --with playwright playwright install chromium. Output: slide-N.png (1080×1350, works on X, LinkedIn, Instagram) + carousel.pdf (LinkedIn document post).

slides.json schema

{
  "title": "Video/article title",
  "source": "Author · Platform · 1.16M views",
  "score": 5,
  "verdict_line": "Real tools, fantasy income math",
  "footer": "@their-handle · their-link (the sharer's, not the tool author's — see rules)",
  "slides": [
    { "type": "hook" },
    { "type": "claim", "n": "1/12", "claim": "Quoted or paraphrased claim, ≤200 chars",
      "verdict": "misleading", "evidence": "One-sentence reality, ≤160 chars" },
    { "type": "cta", "headline": "Run it on anything",
      "lines": ["the sharer's own links — ask, don't assume"] }
  ]
}

Verdicts: confirmed / plausible / misleading / false / unverifiable / not checked — the same six the report uses, and the renderer rejects anything else rather than guessing a colour. Pick 3–4 claim slides — the spiciest verdicts with the strongest evidence, not the first four. Hook and CTA slides bookend them.

A not checked claim renders, but think before using one: it carries no verdict and no evidence by definition, so it makes a weak slide and a reader may take the empty cell for a finding.

Rules

  • The report is the content; the tool is the footnote. Hooks lead with findings ("12 claims, 3 misleading"), never with "I built a tool".
  • Footer and CTA belong to the person sharing. Ask for their handle/newsletter/links (or omit those slides) — never default to the tool author's branding. Crediting the tool is welcome but optional: one line like "made with bullshit-detector" is plenty.
  • Numbers must match the report exactly — a fact-checking brand cannot round its own stats.
  • Stay honest in compression: if the report's verdict is nuanced ("competent hype, not a scam"), the post says that too. No rage-bait the report doesn't support.
  • Never fabricate engagement bait ("everyone is talking about this").
  • Each platform block must be paste-ready: correct length, line breaks, and links already positioned per PLATFORMS.md.

Comments

Markdown supported