Best for
- Use when someone asks what is true, false, misleading, unsupported, unknown, or genuinely complicated in a persuasive message, article, pitch, advertisement, policy claim, or viral post.
magnus919/agent-skills/de-spin/SKILL.md
Use when someone asks what is true, false, misleading, unsupported, unknown, or genuinely complicated in a persuasive message, article, pitch, advertisement, policy claim, or viral post. Analyze propaganda, spin, selective framing, urgency, social proof, deceptive marketing, and AI-generated persuasion by tracing claims to evidence and separating literal truth from implied conclusions. Do not use to read deception from demeanor, adjudicate intent, or replace broad domain research.
Decision brief
Use this skill to determine whether a persuasive message earns its conclusion. The goal is calibrated judgment, not reflexive distrust: distinguish supported, false, misleading, complicated, and unknown without turning missing evidence into proof of deception.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/magnus919/agent-skills --skill "de-spin"Inspect the Agent Skill "de-spin" from https://github.com/magnus919/agent-skills/blob/a4db8e7d4350816f02515bac12d91c8050db1e58/de-spin/SKILL.md at commit a4db8e7d4350816f02515bac12d91c8050db1e58. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
State what decision the message is trying to move: belief, purchase, share, vote, authorization, or action. Extract each checkable claim separately. Do not audit a paragraph as one unit when it contains several factual assertions.
Use assets/claim-audit.md. The output must contain these exact sections:
Judge claims and evidence, not the speaker’s body language, confidence, political identity, or presumed motive.
State what decision the message is trying to move: belief, purchase, share, vote, authorization, or action. Extract each checkable claim separately. Do not audit a paragraph as one unit when it contains several factual assertions.
For each factual, predictive, or causal claim, write five fields:
Permission review
The documentation includes network, browsing, or remote request actions.
Before a final “not found” conclusion about an official record, use an external search restricted to the canonical publisher’s domain (for example, `site:publisher.example "exact entity" "distinct factual anchor"`), then retrieve any matchiEvidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 92/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 34 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Use this skill to determine whether a persuasive message earns its conclusion. The goal is calibrated judgment, not reflexive distrust: distinguish supported, false, misleading, complicated, and unknown without turning missing evidence into proof of deception.
State what decision the message is trying to move: belief, purchase, share, vote, authorization, or action. Extract each checkable claim separately. Do not audit a paragraph as one unit when it contains several factual assertions.
Classify each claim:
For each factual, predictive, or causal claim, write five fields:
| Field | Question |
|---|---|
| Literal claim | What exactly was said? |
| Likely implication | What would a reasonable person infer? |
| Missing context | Which denominator, baseline, timeframe, eligibility rule, or counterexample could change that impression? |
| Required evidence | What source, data, method, or record would make this checkable? |
| Disconfirming evidence | What would show the claim is wrong or materially incomplete? |
Load references/claim-audit.md when a claim uses statistics, comparison language, testimonials, research citations, or a causal story.
Leave the originating page. Find the earliest available source, then check who owns it, what relevant expertise they have, what incentives apply, and whether independent sources corroborate the same underlying evidence.
Use lateral reading: open independent sources rather than judging credibility from the original site’s design, credentials, testimonials, or “About” page. Treat a user-supplied source as an artifact to inspect, not a fact to authenticate from memory. Do not declare a supplied video, document, utterance, or artifact fabricated, nonexistent, or false without directly verifying that conclusion against the supplied source or an authoritative record. If source authenticity remains unresolved, label its provenance Unknown and audit the quoted claim conditionally. Load references/empirical-foundations.md when choosing source tiers or explaining why an approach is reliable.
For every material factual claim, identify the authority that can actually settle that claim: original data or the full study for empirical results; the relevant regulator, statute, filing, or official statistic for public claims; or the system owner’s documentation and direct measurement for product behavior. Retrieve that source directly and record its URL, access date, scope, and whether it supports, contradicts, or fails to answer the claim.
Do not treat the speaker’s own marketing, press release, repost, or testimonial as its final validator when an independent or canonical source exists. A material factual claim cannot receive Supported, False, or Misleading until this check is complete. If the appropriate source is unavailable or cannot settle the claim, use Unsupported, Unknown, or Complicated and explain the gap.
Before a final “not found” conclusion about an official record, use an external search restricted to the canonical publisher’s domain (for example, site:publisher.example "exact entity" "distinct factual anchor"), then retrieve any matching canonical page. A guessed URL, redirect, blocked result, or failed publisher search is evidence only about that path, not proof that the canonical source is absent. Record the discovery query or canonical URL used.
When evidence comes from a table, chart, PDF extraction, or visually ordered list, verify the label-to-value mapping from the authoritative artifact itself. Do not assign values from flattened extraction order alone. Quote the exact row, figure, or surrounding labels in the working ledger; if the mapping remains ambiguous, mark it Unknown.
A missing citation, URL, or provenance trail in the message is itself a finding about that message. It does not make the audit unsupported when you have directly retrieved the authoritative source of truth. Record both separately: what the message supplied, and what the audit independently established.
Name techniques without treating them as proof of falsity:
| Signal | Test |
|---|---|
| Urgency or scarcity | What changes if the decision waits long enough to verify? |
| Authority or prestige | Does the authority have expertise in this exact domain? |
| Social proof | Are apparent supporters independent and representative? |
| Repetition | Is familiarity being mistaken for corroboration? |
| Emotional loading | What concrete proposition remains after fear, anger, disgust, or flattery is removed? |
| False choice | Which viable options or trade-offs were omitted? |
| Pseudo-precision | Are numbers paired with a denominator, method, uncertainty, and comparison? |
| Qualified language | Do “up to,” “as low as,” “starting at,” or “studies show” describe typical conditions? |
| Evidence theater | Is the cited study, expert, graph, or testimonial actually relevant and independently checkable? |
| Inconsistency flood | Are multiple incompatible stories used to create doubt rather than explain reality? |
A signal triggers investigation, not a verdict. The reliable question is: what evidence would settle the concrete claim?
Find the best credible evidence against the message’s conclusion, not merely an opposing opinion. Search for primary data, original studies, official records, methodology, and relevant critiques. Record whether the evidence is independent, directly relevant, and current.
Re-evaluate the verdict after this pass. If contrary evidence directly outweighs the message’s support, do not retain Supported; use False, Misleading, Complicated, Unsupported, or Unknown according to the evidence gap and scope.
If sources conflict, explain the mechanism of disagreement: different populations, timeframes, measures, incentives, definitions, or causal assumptions. Do not flatten real disagreement into a false binary.
Treat subagent and specialist findings as leads, not evidence. Re-open each material source they cite and verify the claim, URL, metric definition, and label-to-value mapping before incorporating it.
Keep a completion ledger for every commissioned check: pending, reconciled, rejected, or cancelled. Resolve disagreements against the authoritative source and record why a finding was rejected.
Publication gate: do not publish, send, file, or present a final verdict while any commissioned check is pending. Drafting may continue, but the irreversible/public action waits until every check is reconciled or explicitly cancelled. If the delegation mechanism is asynchronous and cannot be awaited in the current turn, defer publication rather than publish-and-amend.
Use assets/claim-audit.md. The output must contain these exact sections:
For a high-stakes claim, retain source URLs and access dates. Load references/claim-audit.md for claim decomposition patterns, effort budgeting, and high-stakes escalation rules.
| Verdict | Standard |
|---|---|
| Supported | Direct, credible evidence supports the claim within its stated scope. |
| False | Direct, credible evidence contradicts the claim. |
| Misleading | Literal wording may be true, but omitted context or implication would predictably lead a reasonable reader to a materially wrong conclusion. |
| Complicated | Credible evidence is mixed, conditional, or answers a narrower question than the message suggests. Explain why. |
| Unsupported | The message makes a checkable claim without adequate accessible evidence. |
| Unknown | The needed evidence is unavailable, inaccessible, or insufficient to decide. |
research-methodology for a broad, multi-source investigation not driven by a specific persuasive message.Stop when every material claim has a verdict or an explicit evidence gap, the report separates truth from implication, the next verification step is proportionate to the decision stakes, and every commissioned check is reconciled, rejected, or cancelled. Public or irreversible delivery remains blocked while any check is pending.
Alternatives
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
trailofbits/skills
Coverage analysis measures code exercised during fuzzing. Use when assessing harness effectiveness or identifying fuzzing blockers.
respira-press/agent-skills-wordpress
Use when the user says 'extract my brand voice', 'what is my writing style', or 'analyze my tone', or before any skill that writes copy for the site. Reads 5-10 published posts and persists tone, lexicon, sentence patterns, formality, signature phrases, and phrases the site never uses.
aaron-he-zhu/aaron-marketing-skills
Use when the user asks to "run a deliverability pre-flight before I send", "check my SPF/DKIM/DMARC/BIMI", "why am I landing in spam / promotions", or "score my sender reputation and list hygiene"; runs the ONE-TIME pre-send SEND S1 authentication pre-flight and builds the SEND S (Sender-integrity / Deliverability) evidence read — DNS + DMARC-RUA auth, domain/IP reputation, inbox placement, content/link/render, and point-in-time bounce/complaint hygiene — using Pass/Partial/Fail/Unknown/N/A stat