skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
serhiikorniienko/bullshit-detector77 installs

share

Turn a BS report (or any analysis result) into ready-to-paste posts for X/Twitter, LinkedIn, Facebook, Reddit, Hacker News, or a newsletter issue — plus a branded image carousel (PNGs + PDF) for visual platforms. Use when the user wants to share, post, publish, or promote a report, asks for "a thread", "a LinkedIn post", "a carousel", or "format this for X".

How do I install this agent skill?

npx skills add https://github.com/serhiikorniienko/bullshit-detector --skill share
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is a utility for formatting reports into social media posts and image carousels. It uses a local Python script to generate visual slides via Playwright. The skill follows security best practices, such as HTML escaping of processed data, and its external dependency download (Chromium) is from a well-known, trusted source.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

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.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/serhiikorniienko/bullshit-detector/share">View share on skillZs</a>