Paper Review
EvoScientist/EvoSkills
Guides self-review of YOUR OWN academic paper before submission with adversarial stress-testing.
Identify recurring weak arguments, unsupported assumptions, and vulnerable inference patterns across a literature corpus.
Install Weakness Scanner
$ npx skills add flonat/flonat-research --skill weakness-scanner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install flonat/flonat-research weakness-scanner --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/weakness-scanner .claude/skills/weakness-scanner && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "weakness-scanner" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/weakness-scanner into .claude/skills/weakness-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weakness-scanner", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/flonat/flonat-research/tree/main/skills/weakness-scannerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add flonat/flonat-research --skill weakness-scanner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install flonat/flonat-research weakness-scanner --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/weakness-scanner .agents/skills/weakness-scanner && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "weakness-scanner" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/weakness-scanner into .agents/skills/weakness-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weakness-scanner", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add flonat/flonat-research --skill weakness-scanner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install flonat/flonat-research weakness-scanner --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/weakness-scanner .cursor/skills/weakness-scanner && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "weakness-scanner" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/weakness-scanner into .cursor/skills/weakness-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weakness-scanner", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/flonat/flonat-research.git --path skills/weakness-scanner--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add flonat/flonat-research --skill weakness-scanner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install flonat/flonat-research weakness-scanner --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/weakness-scanner .gemini/skills/weakness-scanner && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "weakness-scanner" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/weakness-scanner into .gemini/skills/weakness-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weakness-scanner", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install flonat/flonat-research weakness-scannerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add flonat/flonat-research --skill weakness-scanner -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/weakness-scanner .github/skills/weakness-scanner && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "weakness-scanner" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/weakness-scanner into .github/skills/weakness-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weakness-scanner", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add flonat/flonat-research --skill weakness-scanner -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install flonat/flonat-research weakness-scanner --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/weakness-scanner .opencode/skills/weakness-scanner && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "weakness-scanner" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/weakness-scanner into .opencode/skills/weakness-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "weakness-scanner", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
weakness-scanner- GitHub stars
- 145
- Token cost
- ~1.5k tokens
- SKILL.md length
- 481 words
- Files
- 1
- Skills in repo
- 83
- Repo updated
- First seen
- Licence
- MIT
At a glance
Identify recurring weak arguments, unsupported assumptions, and vulnerable inference patterns across a literature corpus.
- Works in 5 steps: Corpus Assembly → Weakness Extraction → Cross-Paper Validation → …
- Stress-testing a body of work rather than reviewing one manuscript
- SKILL.md covers When to Use, When NOT to Use, Input and Workflow, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Weakness Scanner is an agent skill from flonat/flonat-research. 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.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Load testing and Peer review. The repository describes itself as: Shareable Claude Code + Codex infrastructure for PhD researchers — skills, agents, hooks, and rules for academic workflows. The licence is MIT.
When your agent uses it
- Stress-testing a body of work rather than reviewing one manuscript
- Tasks that involve Load testing
- Tasks that involve Peer review
Example prompts
- “/weakness-scanner”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Bash(uv*), Bash(uv:*), Task, WebSearch, WebFetch, Bash(paperpile*)
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit da27600. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGlobGrepBash(uv*)Bash(uv:*)TaskWebSearchWebFetch
…and 1 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Weakness Scanner loads about 1.5k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 481 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 481 words, ~1,462 tokens.
Download SKILL.mdSave it as
.claude/skills/weakness-scanner/SKILL.md (or your agent's skills folder).- name
- weakness-scanner
- description
- 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.
- allowed-tools
- Read, Write, Edit, Glob, Grep, Bash(uv*), Bash(uv:*), Task, WebSearch, WebFetch, Bash(paperpile*)
- argument-hint
- [topic, .bib file, or paper directory]
- skill-dependencies
- devils-advocate, method-audit
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
- Your own paper — use
devils-advocateor thepaper-criticagent - Full peer review — use the
referee2-revieweragent - Methodological comparison — use
method-audit(overlaps, but different focus)
Input
Same corpus inputs: .bib file, PDF directory, topic, or paper list. Works best with 10-20 papers on a focused topic.
Workflow
Phase 1: Corpus Assembly
Same as other corpus skills. Prioritise empirical papers making causal or strong claims — these are most likely to have exploitable weaknesses.
Phase 2: Weakness Extraction
For each paper (read via split-pdf), look for:
Logical flaws
- Non sequiturs — conclusions that don't follow from the evidence
- Circular reasoning — assuming what they're trying to prove
- False dichotomies — presenting only two options when more exist
- Hasty generalisation — drawing broad conclusions from narrow evidence
Data limitations
- Small samples without power analysis
- Non-representative populations with claims of generalisability
- Measurement issues (self-report bias, proxy variables)
- Missing data handled without sensitivity analysis
Identification problems
- Causal claims from observational data without credible identification
- Omitted variable bias acknowledged but not addressed
- Reverse causality not ruled out
- Weak instruments (if IV)
Contradicted claims
- Findings that conflict with other papers in the corpus
- Claims undermined by the authors' own robustness checks
- Results that don't survive alternative specifications
Rhetorical overreach
- Abstract claims stronger than the evidence supports
- Policy recommendations not grounded in the findings
- "First to study X" claims that ignore prior work
Show full SKILL.md (149 more words)Show less
Phase 3: Cross-Paper Validation
For each weakness identified:
- Check if other papers in the corpus have already flagged it
- Search for papers that contradict the weak claim (use
scholarly scholarly-search) - Check if the weakness has been addressed in subsequent work by the same authors
Phase 4: Severity Ranking
Rank all weaknesses by severity:
| Severity | Criteria |
|---|---|
| Fatal | The core finding is likely wrong — the paper's contribution doesn't hold |
| Serious | A major limitation that significantly qualifies the findings |
| Moderate | A real limitation that the authors should have discussed |
| Minor | A weakness that doesn't undermine the main claims |
Phase 5: Output
Write to WEAKNESS-SCAN.md in the project directory.
Output Format
# Weakness Scan: [Topic]
**Date:** YYYY-MM-DD
**Corpus:** [N] papers
**Weaknesses identified:** [N] (Fatal: X, Serious: Y, Moderate: Z, Minor: W)
## Top 5 Weaknesses
### 1. [Paper — Author (Year)]
**Claim:**
> "[Verbatim quote of the weak claim]" (p. XX)
**Flaw:** [Type: logical / data / identification / contradiction / rhetorical]
**Why it's weak:** [Specific explanation of the logical flaw or data limitation]
**Already contradicted by:**
- [Paper A (Year)] — [How it contradicts]
- [Paper B (Year)] — [How it contradicts]
**What evidence WOULD make it strong:** [What the authors would need to show]
**Severity:** [Fatal / Serious / Moderate / Minor]
**Opportunity for your research:** [How this weakness creates space for new work]
### 2. [Paper — Author (Year)]
...
## Field-Level Vulnerabilities
Patterns that recur across multiple papers:
1. **[Vulnerability]** — seen in [N] papers
- Papers affected: [list]
- Why nobody has addressed it: [likely explanation]
- How to exploit it: [what a new paper could do]
2. **[Vulnerability]**
...
## Contradiction Map
| Claim | Paper A says | Paper B says | Who has better evidence? |
|-------|-------------|-------------|------------------------|
## Implications for Your Research
- **Strongest opportunity:** [The biggest gap this scan reveals]
- **Contribution framing:** "[Your paper] addresses the [specific weakness] in [prior work] by [your approach]"
- **Caution:** [Any weakness that also applies to your planned approach]Cross-References
| Skill | When to use instead/alongside |
|---|---|
devils-advocate | To stress-test YOUR argument (this scans others') |
method-audit | For systematic methodological comparison (less adversarial) |
theory-mapper | To understand which theories underpin the weak arguments |
replication-audit | To check which findings have actually been replicated |
© flonat, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/weakness-scanner of flonat/flonat-research.
Open the folder on GitHubat commit da27600
Compare with similar skills
Weakness Scanner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Weakness Scanner this skillflonat/flonat-research | 145 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Paper ReviewEvoScientist/EvoSkills | 475 | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| Aeri Referee Strategybrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Devpsych Review Processbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Jedpsych Review Processbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Joap Review Processbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Aeri Referee Strategy
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when calibrating expectations for the fast, decisive American Economic Review: Insights (AER: Insights) review process — conditional-accept-or-reject decisions, the…
Devpsych Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how Developmental Psychology (APA) evaluates a manuscript — masked peer review, editorial weighting of developmental significance, design rigor…
Jedpsych Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Journal of Educational Psychology evaluates a manuscript — masked peer review, editorial weighting of educational relevance, theory…
Joap Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Journal of Applied Psychology (JAP) evaluates a manuscript — masked (anonymized) peer review, the action-editor model, the dual gate of…
Psci Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how Psychological Science evaluates a manuscript — anonymized peer review, editorial weighting of robustness, transparency, and preregistration…
More from flonat/flonat-research
All 83 skills in this repoLatex Posters
flonat/flonat-research
Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter.
Skill Creator
flonat/flonat-research
Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests.
DOCX
flonat/flonat-research
Create, read, edit, or convert Microsoft Word documents while preserving professional document structure.
PDF
flonat/flonat-research
Read, create, combine, split, rotate, OCR, watermark, secure, or extract content from PDF files.
Init Project Orchestration
flonat/flonat-research
Create or migrate project-level agents, repeatable project workflows, and planning state from one client-neutral contract, then render repository-scoped adapters for both Claude Code and Codex.
Pre Commit Audit
flonat/flonat-research
Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers.
Related
Categories
Questions about Weakness Scanner
What does Weakness Scanner do?
Identify recurring weak arguments, unsupported assumptions, and vulnerable inference patterns across a literature corpus. Weakness Scanner is an agent skill from flonat/flonat-research. Identify recurring weak arguments, unsupported assumptions, and vulnerable inference patterns across a literature corpus.
When should I use Weakness Scanner?
Weakness Scanner fits situations like: stress-testing a body of work rather than reviewing one manuscript; tasks that involve Load testing; tasks that involve Peer review.
How do I install Weakness Scanner in Claude Code?
Run `npx skills add flonat/flonat-research --skill weakness-scanner -a claude-code`. Or copy the skill folder (skills/weakness-scanner in flonat/flonat-research) into .claude/skills/weakness-scanner in your project. Claude Code loads it when a task matches its description.
How do I install Weakness Scanner in Codex?
Run `npx skills add flonat/flonat-research --skill weakness-scanner -a codex`. Or copy the skill folder (skills/weakness-scanner in flonat/flonat-research) into .agents/skills/weakness-scanner in your project. Codex loads it when a task matches its description.
Can I use Weakness Scanner in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flonat/flonat-research --skill weakness-scanner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/weakness-scanner, .gemini/skills/weakness-scanner, .github/skills/weakness-scanner and .opencode/skills/weakness-scanner in your project.
What does Weakness Scanner need to run?
SKILL.md names no scripts, command-line tools or credentials: Weakness Scanner is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Bash(uv*), Bash(uv:*), Task, WebSearch, WebFetch, Bash(paperpile*).
Does Weakness Scanner access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Weakness Scanner safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Weakness Scanner use?
Weakness Scanner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Weakness Scanner use?
About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Weakness Scanner?
Skills that share tags, products or a category with Weakness Scanner: Paper Review (EvoScientist/EvoSkills, 475 stars), Aeri Referee Strategy (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars), Devpsych Review Process (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Jedpsych Review Process (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Weakness Scanner?
flonat (a GitHub user) maintains it in flonat/flonat-research, which has 145 GitHub stars. The repository holds 83 skills in this directory. The repository was last updated on September 29, 2026.
Source: flonat/flonat-research on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.