Weaponized Autism
Obsessive-detail mode that reads every relevant file, checks every edge case, questions every assumption, and chases every dependency before answering; slower on purpose and far harder to fool — invoke via /weaponized-autism when a confident-but-wrong answer would be expensive, e.g. deep debugging, auditing, or high-stakes research.
Install
npx skills add Jakeschincariol/unhinged-claude-skills --skill weaponized-autismgit clone --depth 1 https://github.com/Jakeschincariol/unhinged-claude-skills.git /tmp/unhinged-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/unhinged-claude-skills/weaponized-autism ~/.claude/skills/weaponized-autismPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Weaponized Autism Maximum rigor, zero hand-waving. This mode refuses to guess. It reads the actual source, traces the actual call path, and treats every "should be fine" as a claim to be verified. Slower by design — and almost impossible to fool. ## When to use - Debugging, auditing, or research where a wrong-but-confident answer is costly. - Anything where the surface-level explanation has already failed you once. ## Behavior 1. Read every file relevant to the question in full — no skimming, no assuming the obvious function does the obvious thing. 2. List your assumptions explicitly, then attack each one. Mark which you verified and which you could not. 3. Trace dependencies end to end: follow imports, callers, config, and runtime values rather than inferring them. 4. Enumerate edge cases — empty inputs, nulls, concurrency, off-by-one, encoding, timezones, failure paths — and check each against the code. 5. Reproduce the behavior or cite the exact lines that prove your claim; never assert without evidence. 6. When two sources of truth disagree (docs vs code, comment vs implementation), trust the executing code and flag the discrepancy. 7. Distinguish what you KNOW (verified) from what you SUSPECT (inferred) in the final answer. ## Output A precise, evidence-backed answer with file:line citations, an explicit assumptions-checked list, and a clear separation of verified facts from open questions.
Details
- Skill name
weaponized-autism- Repository
- Jakeschincariol/unhinged-claude-skills
- Path
weaponized-autism/SKILL.md- License
- MIT
- Repo updated
- 27 June 2026
FAQ
What does the Weaponized Autism skill do?
Obsessive-detail mode that reads every relevant file, checks every edge case, questions every assumption, and chases every dependency before answering; slower on purpose and far harder to fool — invoke via /weaponized-autism when a confident-but-wrong answer would be expensive, e.g. deep debugging, auditing, or high-stakes research.
How do I install the Weaponized Autism skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Jakeschincariol/unhinged-claude-skills --skill weaponized-autism. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Weaponized Autism popular?
It lives in Jakeschincariol/unhinged-claude-skills, which has 44 GitHub stars and 13 forks.
Related skills
Apollo 13
44Jakeschincariol/unhinged-claude-skills
Works a critical failure under hard constraints — limited options, no clean fix — to get the broken thing home with whatever you have; invoke via /apollo-13 when something important is down, the usual tools are unavailable, and you must improvise a survival fix.
Autopilot Chaos
44Jakeschincariol/unhinged-claude-skills
Takes the whole task and runs it end to end without stopping to ask, leaving the user to review at the finish line; invoke via /autopilot-chaos when you want a fully autonomous run and will inspect the result once it's done.
Basement Hacker
44Jakeschincariol/unhinged-claude-skills
Goes underground to reverse-engineer internals, read the source nobody reads, and explain how something actually works; invoke via /basement-hacker when documentation is missing or lying and you need ground truth from the implementation itself.
Academic Paper Verify
36dariia-m/my_claude_skills
Thoroughly verify all code, tables, figures, modeling decisions, and quantitative claims in an academic paper against its source R scripts and output files. Use this skill whenever you need to audit, replicate, or verify an academic research paper - including cross-checking LaTeX tables against R output, validating econometric modeling choices, ensuring sample sizes are consistent, building a verification manifest, and running automated replication tests. Trigger this skill for any mention of: paper verification, replication check, table audit, code-paper consistency, reproducing results, veri
Employment Law Research
43bstevescherer/heycounsel-community
Research a US employment law topic across federal, state, and city jurisdictions and produce structured research notes with proper source attribution. Use this skill any time the user asks about US employment laws, regulations, or pending legislation - from a single jurisdiction question to a 50-state survey. Triggers include phrases like "research [employment law topic]", "what are the laws on [employment topic]", "state-by-state [employment topic]", "help me understand [topic] across the US", or any prompt that asks for a legal landscape overview before another deliverable. Always run this B
Academic Writing
36dariia-m/my_claude_skills
Activate when the user is drafting any academic economics content from scratch (e.g., outlines, abstracts, introductions, data/methods/identification sections, results narratives, conclusions, referee responses, table/figure captions) and needs economics-specific structure, phrasing options, and quality checks to produce publication-ready prose.
Browse the most popular Claude skills, all research & science skills, or write your own with the skills generator.