brycewang-stanford/review-r
skills/15-Felpix-Studios-social-science-research/skills/review-r/SKILL.md
Run the R code review protocol on R scripts. Checks code quality, reproducibility, domain correctness, and professional standards. Produces a report without editing files. Make sure to use this skill whenever the user wants their existing R code evaluated or audited — not when they want new analysis written. Triggers include: "review my R script", "check my R code", "is my code replication-ready", "audit this R file", "does this code follow conventions", "will this reproduce", "check my analysis script", "code review", "review-r", or when the user has an existing .R file and wants quality feedback rather than new code.
$ install --global
skillsauthnpx skillsauth add brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research review-rInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 5, 2026, 4:32 AM81.9s1 file scanned
SKILL.md
- name:
- review-r
- description:
- >-
- Run the R code review protocol on R scripts. Checks code quality, reproducibility, domain correctness, and professional standards. Produces a report without editing files. Make sure to use this skill whenever the user wants their existing R code evaluated or audited — not when they want new analysis written. Triggers include:
- review my R script", "check my R code", "is my code replication-ready", "audit this R file", "does this code follow conventions", "will this reproduce", "check my analysis script", "code review", "review-r", or when the user has an existing .R file and wants quality feedback rather than new code.
- argument-hint:
- [filename, 'all', or analysis name pattern]
- allowed-tools:
- ["Read", "Grep", "Glob", "Write", "Task", "AskUserQuestion"]
Review R Scripts
Run the comprehensive R code review protocol.
Steps
-
Identify scripts to review:
- If
$ARGUMENTSis a specific.Rfilename: review that file only - If
$ARGUMENTSis a name pattern (e.g.,model_name): glob for matching.Rfiles. If multiple matches, use AskUserQuestion:- header: "Scripts"
- question: "Multiple R scripts match that pattern. Which should I review?"
- multiSelect: true
- options: list up to 4 matched files (label: filename, description: path and last modified). User can select multiple.
- If
$ARGUMENTSisall: review all R scripts inscripts/R/andFigures/*/ - If
$ARGUMENTSis empty, glob for all.Rfiles. If multiple found, use AskUserQuestion as above.
- If
-
For each script, launch the
r-revieweragent with instructions to:- Follow the full protocol in the agent instructions
- Read
rules/r-code-conventions.mdfor current standards - Save report to
quality_reports/[script_name]_r_review.md
-
After all reviews complete, present a summary:
- Total issues found per script
- Breakdown by severity (Critical / High / Medium / Low)
- Top 3 most critical issues
-
IMPORTANT: Do NOT edit any R source files. Only produce reports. Fixes are applied after user review.
Related Skills
brycewang-stanford/literature-review-tools
tools
VerifiedTrustedCommunity
Recommend AND run open-source AI tools, agents, Claude Code / Codex skills, and MCP servers for any stage of a literature review — searching, reading, extracting, synthesizing, screening, citation-checking, and paper writing. Use when the user asks "what tool should I use to..." OR "install/run/use <tool> to ..." for research/lit-review work: automating a survey or related-work section, PDF→Markdown extraction for LLMs (MinerU/marker/docling), PRISMA / systematic review (ASReview), citation-backed Q&A over PDFs (PaperQA2), wiring papers into Claude/Cursor via MCP (arxiv/paper-search/zotero servers), or chatting with a Zotero library. Ships a launcher (scripts/litrun.py) that installs each tool in an isolated venv and runs it. Curated catalog of 70+ vetted projects. 支持中英文（用于「文献综述工具选型」与「一键安装/运行」）。
3,109SKILL.mdUpdated Jul 28, 2026
brycewang-stanford/auto-empirical-research-skills
development
VerifiedTrustedCommunity
Route empirical-research requests through the Auto-Empirical Research Skills catalog when this whole repository is installed as one skill in Codex, CodeBuddy, Claude Code, or another IDE. Use to choose and load the right vendored AERS skill for causal inference, econometrics, replication, data acquisition, manuscript writing, peer review and referee responses, citation checking, de-AIGC editing, or full empirical-paper workflows without reading the entire repository at once.
3,109SKILL.mdUpdated Jun 27, 2026
brycewang-stanford/aer-preregistration
documentation
VerifiedTrustedCommunity
Use when the project collects primary data or runs a field, lab, or survey experiment, before the intervention begins — write the pre-analysis plan, size the sample from a power calculation, and register with the AEA RCT Registry. Apply after the design is chosen in aer-identification and before any outcome data are seen.
3,021SKILL.mdUpdated Jul 23, 2026
brycewang-stanford/economist-data-skill
tools
VerifiedTrustedCommunity
Guide economists to authoritative data sources with explicit, confirmed data specifications before retrieval; interfaces with Playwright MCP to navigate portals and extract real data, not articles about data.
3,021SKILL.mdUpdated Jul 23, 2026