agentleFS
SerhiiKorniienkoSerhiiKorniienko/bullshit-detector/skills/publishing/share/SKILL.md

share

Skill151 starsChanged 2 months agoMITView on GitHub

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".

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use origin, review-bugbot and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • 0mlkrizzz655335vSkill

    origin

    origin CLI 管理。安装、登录、更新、修复 origin.cursor.com 的 CLI。"disabled-environments:

    Also in 3 projects that use this

  • 0mlkrizzz655335vSkill

    review-bugbot

    缺陷导向代码审查。用 Bugbot 子代理找 bug。

    Also in 3 projects that use this

  • PandelisZSkill

    update-cli-config

    View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.

    Also in 3 projects that use this

  • 32103210Skill

    migrate-to-skills

    Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.

    Also in 3 projects that use this

  • 32103210Skill

    update-cursor-settings

    Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.

    Also in 3 projects that use this

  • MicrosoftSkill

    automate

    Propose an automation from a completed task or a new idea, then create it after approval. Use when the user asks to create an automation or wants scheduled local or cloud agent work.

    Also in 3 projects that use this

  • +3 more from 0mlkrizzz655335v
  • +1 more from 32103210

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask which platforms: if not stated. Default set: X thread + LinkedIn post.

    line 13
  2. Very specific:

    Footer and CTA belong to the person sharing: Ask for their handle/newsletter/links (or omit those slides) — never default to the tool …

    line 49
  3. Distinctive:

    Never fabricate engagement bait ("everyone is talking about this").

    line 52

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.