skills/29-quarcs-lab-project20XXy/dot-claude/skills/literature-note/SKILL.md
Creates a structured annotation note in references/ with sections for research question, data, findings, and relevance. Use when documenting a paper.
npx skillsauth add brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research literature-noteInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Create a structured annotation note for a paper in references/.
$ARGUMENTS — a citation key from references.bib, a DOI, or a paper description (e.g., "acemoglu2001colonial" or "Acemoglu 2001 colonial origins")Parse the argument:
references.bib, use that entry's metadatareferences.bib first (offer to run the /project:cite workflow)If a URL or DOI is provided, attempt to fetch and read the paper to extract key information.
Create a Markdown file in references/ named <citation-key>.md with this structure:
# <Author (Year)> — <Short Title>
**Citation key:** `<key>`
**Full reference:** <formatted reference>
## Research Question
[What question does this paper address?]
## Identification Strategy
[How do the authors establish causality? What is the main source of variation?]
## Data and Sample
[What data do they use? What is the sample period, unit of observation, and sample size?]
## Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]
## Methodology Notes
[Econometric methods, estimators, robustness checks worth noting]
## Relevance to This Project
[How does this paper relate to the current research? What can we build on or contrast with?]
If information about the paper was retrieved (from the web or a PDF), pre-fill the sections with extracted content. Otherwise, leave the bracket placeholders for the user to fill in.
Report the file path and remind the user to fill in any remaining placeholder sections.
references.bib and cannot be resolved, ask the user for more details.references/<key>.md already exists, show the existing note and ask if the user wants to update it.tools
Show mcp-stata identity, connected tools, and status. Use when the user asks if mcp-stata is available, asks about access to the toolkit, or asks what Stata tools are connected.
tools
Activate when users mention Stata commands, .do files, regressions, econometrics, stored results, graphs, dataset inspection, replication, or Stata errors. Route the task through mcp-stata tools and the specialized research skills instead of treating it as plain text coding.
development
Build and review paper-ready regression, balance, and summary tables from Stata outputs. Use when the user needs a clean table for a draft, appendix, or coauthor share-out.
tools
Install, configure, update, or verify mcp-stata across Claude Code, Codex, Gemini CLI, Cursor, Windsurf, and VS Code. Activate when users ask to set up the Stata toolkit or troubleshoot the installation.