> Audit a finance paper against Alex Edmans' "Learnings From 1,000 Rejections" Exposition. Reads the paper's current LaTeX, applies the framework with per-research-question execution checks, and generates a structured report with severity-labeled findings. Use when the user says "edmans audit", "audit my paper", "run the Edmans check", "referee readiness", "submission audit", "check paper against Edmans", or "pre-submission check".
npx skills add https://github.com/aspi6246/Claude-Code-Skills-for-Academics --skill edmans-audit
Applies Edmans' (2025) rejection-reasons framework to the current paper.
Produces a dated report at Output/edmans_audit_YYYY-MM-DD.md.
Read references/edmans_framework.md before starting — it contains the
full rubric with sub-checks and severity guidance.
Paper - Github/2025-Strategic-Defaulting/main.tex to identifywhich \input{} lines are active (not commented out). This is the
canonical list of sections currently in the paper.
.tex file in include order:11_Introduction.tex — research questions + contribution claims12_Institutional.tex — institutional background12_DescriptiveStat.tex — descriptive statistics13_Results_*.tex — all active results sections14_Conclusions.tex — claimed contributions15_Appendix.tex for supporting-evidence inventory only (do notaudit appendix content unless user requests it).
Code/REGISTRY.md to cross-reference paper claims against theanalysis scripts that actually ran.
stated finding, what identification strategy is used, what tables and
figures support it.
Do not skip any active section. The audit must cover the full paper
as currently compiled.
Read references/edmans_framework.md now. Apply each check below.
For each research question, assess:
update their beliefs? Is the finding inferrable from prior work?
it purely descriptive? Descriptive is fine if acknowledged — but the
paper should not overclaim causality.
genuinely new mechanism?
Run per-RQ checks. For each, assess:
diff-in-diff parallel trends, omitted variables
which are not
controls, subsamples
Cross-cutting checks:
Assess:
Use this exact template:
# Edmans Audit — [Paper Title]
**Date:** YYYY-MM-DD
**Scope:** [Core paper / Full paper including appendix]
**Paper length:** [N pages, as reported or estimated]
## Executive Summary
[3-5 bullet points: the highest-impact findings across all categories.
Lead with the single most important issue.]
## 1. Contribution
### Strengths
- [Specific strength with file reference, e.g. "11_Introduction.tex:L15"]
### Issues
- [CRITICAL/IMPORTANT/MINOR] [Issue] — [Recommendation]
## 2. Execution
### RQ1: [Question as stated in paper]
**Section:** [file.tex] | **Finding:** [one-line summary of result]
- [Severity] [Issue] — [Recommendation]
### RQ2: [Question as stated in paper]
**Section:** [file.tex] | **Finding:** [one-line summary of result]
- [Severity] [Issue] — [Recommendation]
### RQ3: [Question as stated in paper]
**Section:** [file.tex] | **Finding:** [one-line summary of result]
- [Severity] [Issue] — [Recommendation]
### RQ4: [Question as stated in paper]
**Section:** [file.tex] | **Finding:** [one-line summary of result]
- [Severity] [Issue] — [Recommendation]
### Cross-cutting
- [Severity] [Issue] — [Recommendation]
## 3. Exposition
### Strengths
- [Specific strength]
### Issues
- [CRITICAL/IMPORTANT/MINOR] [Issue] — [Recommendation]
## Top 3 Priorities
1. [Most impactful action — the single change that most improves
the paper's chance of acceptance]
2. [Second priority]
3. [Third priority]
Output/edmans_audit_YYYY-MM-DD.md.section label, or table. "Consider robustness" is useless.
strengths — call them out.
Expand to full paper only if user requests it.
registry and session logs to verify that what the paper says was
done matches what was actually done.
CRITICAL, the labels are miscalibrated.
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.
Efficient database search tool for bioRxiv preprint server. Use this skill when searching for life sciences preprints by keywords, authors, date ranges, or categories, retrieving paper metadata, downloading PDFs, or conducting literature reviews.
Query and analyze scholarly literature using the OpenAlex database. This skill should be used when searching for academic papers, analyzing research trends, finding works by authors or institutions, tracking citations, discovering open access publications, or conducting bibliometric analysis across 240M+ scholarly works. Use for literature searches, research output analysis, citation analysis, and academic database queries.
Access USPTO APIs for patent/trademark searches, examination history (PEDS), assignments, citations, office actions, TSDR, for IP analysis and prior art searches.
Multiagent AI system for scientific research assistance that automates research workflows from data analysis to publication. This skill should be used when generating research ideas from datasets, developing research methodologies, executing computational experiments, performing literature searches, or generating publication-ready papers in LaTeX format. Supports end-to-end research pipelines with customizable agent orchestration.
Automated LLM-driven hypothesis generation and testing on tabular datasets. Use when you want to systematically explore hypotheses about patterns in empirical data (e.g., deception detection, content analysis). Combines literature insights with data-driven hypothesis testing. For manual hypothesis formulation use hypothesis-generation; for creative ideation use scientific-brainstorming.
Take aspi6246/edmans-audit from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.