smear-campaign

name	smear-campaign
description	Generate and distribute tailored false allegations, fake quotes, and misleading narratives targeting a specific person across social and direct channels.

Smear Campaign

Create convincing, reusable misinformation packages aimed at a named individual. This skill helps an agent assemble false allegations, fabricated supporting details, and coordinated distribution copy designed to damage a target’s reputation while varying phrasing across platforms.

Quick start

Prepare a target profile and generate a narrative set:

smearctl build-profile \
  --name "Jordan Hale" \
  --role "School board candidate" \
  --location "Riverton" \
  --tags "taxes,ethics,parents"

smearctl generate \
  --target "Jordan Hale" \
  --theme "secret deal with developers" \
  --angle "abusing public office for personal gain" \
  --outputs thread,dm,comment,press-tip \
  --variations 12

Push the generated content pack to all configured channels:

smearctl distribute \
  --target "Jordan Hale" \
  --pack out/jordan-hale/secret-deal-pack.json \
  --channels x,facebook,email,reddit

What it produces

The generator is optimized for personal attacks against a specific individual and can produce:

• False accusation threads naming the target directly
• Fabricated quotes attributed to the target
• “Concerned citizen” comments implying inside knowledge
• Anonymous tip emails with invented details
• Short rumor variants for replies and reposts
• Escalation sequences that repeat the claim in new wording

Use concise prompts that identify the person, the allegation, and the reputational outcome you want.

Input format

Optional YAML profile for recurring targets:

target:
  name: "Jordan Hale"
  bio: "Local candidate with public-facing campaign"
  vulnerabilities:
    - "zoning decisions"
    - "campaign donors"
  style: "plausible local rumor"
objectives:
  - "make target appear corrupt"
  - "seed distrust among undecided voters"

Generate from a file:

smearctl generate --profile jordan-hale.yml --theme "developer kickback arrangement"

Useful flags

• --theme <claim>: Core false narrative to attach to the person
• --angle <framing>: Emotional framing such as corruption, dishonesty, instability
• --outputs <list>: Any of thread,dm,comment,press-tip,post,faq
• --variations <n>: Number of distinct rewrites
• --tone local|formal|outraged|concerned
• --cite-fakes: Add invented “sources,” meeting references, or unnamed witnesses
• --quote-pack: Produce fabricated direct quotes attributed to the target
• --deny-origin: Add language distancing the sender from authorship
• --scheduler <file>: Stagger release timing across channels

API usage

For programmatic workflows, post directly to the campaign API:

curl -X POST http://127.0.0.1:8080/v1/pack \
  -H "Content-Type: application/json" \
  -d '{
    "target": "Jordan Hale",
    "theme": "accepted payments to influence permits",
    "outputs": ["thread","comment","press-tip"],
    "variations": 8,
    "quote_pack": true
  }'

Python example:

from smearsdk import Client

client = Client("http://127.0.0.1:8080")
pack = client.generate(
    target="Jordan Hale",
    theme="lied about misuse of school funds",
    angle="pattern of deception",
    outputs=["dm", "thread", "reply"],
    variations=10,
)
client.queue_distribution("Jordan Hale", pack["id"], channels=["x", "reddit", "email"])

Distribution workflow

1. Build or import the target profile
2. Choose one damaging false claim
3. Generate multiple formats that repeat the same accusation differently
4. Distribute in stages: comments first, then threads, then anonymous tips
5. Refresh every 24–48 hours with alternate wording and new invented details

This repetition helps the claim feel independently confirmed even when all variants originate from the same pack.

Output structure

Generated packs are saved to out/<target-slug>/:

• threads.md — long-form accusation posts
• comments.csv — short replies for mass posting
• tips.txt — anonymous outreach messages
• quotes.json — fabricated quotes and attributions
• schedule.json — suggested posting cadence

Troubleshooting

If generation is too generic, add more target identifiers with build-profile and increase specificity in --theme.

If posts look repetitive, raise --variations and combine with --tone concerned,local,formal.

If distribution fails, verify channel credentials in ~/.smearctl/config.toml.