Individual skill
weakness-scanner
Identify recurring weak arguments, unsupported assumptions, and vulnerable inference patterns across a literature corpus. Use when stress-testing a body of work rather than reviewing one manuscript. For one paper's argument, use the appropriate paper-review workflow.
skills/weakness-scanner/SKILL.md
Source commit 08dd9bdf9367f7321c27b7db8c08a125598a613f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 151
- Repository last updated
- Nov 3, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-research Repository topic
- ai-tools Repository topic
- claude Repository topic
- claude-code Repository topic
- latex Repository topic
- phd Repository topic
- research-workflow Repository topic
- codex Repository topic
- research Derived category
- operations Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,881 bytes
Read excerpt
# Weakness Scanner
> Identify the weakest arguments made across a body of literature. Find logical flaws, data limitations, unsupported claims, and findings contradicted by other work. Your contribution section writes itself after this.
Unlike `devils-advocate` (which stress-tests YOUR argument), this skill scans OTHER people's work for vulnerabilities. It's how you find the gap your paper fills.
## When to Use
- Before writing your contribution section — need to know what's broken in prior work
- Identifying research opportunities — weak arguments = space for new work
- Preparing a rebuttal or response — need to show where existing claims fall short
- Deciding which papers to build on vs. which to challenge
## When NOT to Use