aspi6246/Claude-Code-Skills-for-Academics

A collection of Skills for academics.

153

stars

49

commits

Python

primary language

Aug 21, 2026

updated

README

Claude Code Skills

Personal skills repo for academic empirical finance research workflows.

Repo layout

~/.claude/skills/
├── <skill-name>/       one folder per skill, each with a SKILL.md
├── output-styles/      copies of my Claude Code output styles
├── presentations/      talks given about this repo
└── README.md

Skill folders have to stay at the top level. Claude Code discovers personal skills at exactly ~/.claude/skills/<skill-name>/SKILL.md and does not look any deeper, so the skills cannot be tidied into a skills/ subfolder — they would silently stop loading. (Nested .claude/skills/ directories are supported inside a project, but that is a monorepo feature and does not apply here.)

output-styles/ and presentations/ are safe as siblings: a folder with no SKILL.md in it is ignored by skill discovery.

Setup

Fresh install (empty ~/.claude/skills/)

Clone this repo directly into the Claude Code global skills directory:

git clone https://github.com/aspi6246/Claude-Code-Skills-for-Academics.git "$HOME\.claude\skills"

Selective install (skills directory already exists)

If ~/.claude/skills/ already contains other skills, do not clone on top of it — it will fail. Instead, clone into a temporary location and copy only the skills you want:

git clone https://github.com/aspi6246/Claude-Code-Skills-for-Academics.git "$HOME\claude-skills-tmp"
Copy-Item "$HOME\claude-skills-tmp\wrap-up" "$HOME\.claude\skills\" -Recurse
# repeat for each desired skill, then remove the temp dir
Remove-Item "$HOME\claude-skills-tmp" -Recurse -Force

Updating

After editing skills on GitHub or locally:

cd "$HOME\.claude\skills"
git pull

Skills

SkillPurpose
r-empirical-financeR code conventions for panel data, causal inference, and data pipelines (data.table, fixest, arrow)
beamer-slides-teachingLaTeX Beamer slide generation with pdfLaTeX and UTS house style
beamer-checkCompile → inspect → fix → verify audit loop for Beamer decks
code-auditTwo-phase code review for research scripts, with safeguards for licensed data
data-profilerSystematic dataset profiling protocol — unit of observation, panel structure, data quality
paper-editorSeven-audit editorial review protocol for academic finance working papers
paper-reviewStructured summary template for academic papers
edmans-auditPre-submission paper audit against Edmans' (2025) three-part framework: Contribution, Execution, Exposition
canvas-lms-apiCanvas LMS REST API conventions for course sync scripts (modules, pages, file uploads)
spin-upStart-of-session briefing — git state, last log, pinboard, active output style, project state synthesis
wrap-upEnd-of-session cleanup — log, memory, pinboard, session-scoped git commit
script-registryTrack R Markdown script dependencies, inputs/outputs, and paper targets via per-script YAML metadata
code-sweepEnd-of-milestone audit of the Code/ folder for drift between scripts, registry, outputs, and paper — propose-and-confirm fixes
skill-writing-guideReference for writing and improving skills
pinboardQuick-capture pinboard for to-dos, paper leads, data issues, and ideas
glossaryPer-project glossary of definitions, abbreviations, and command-phrases, loaded adaptively at session start
wtfType "wtf" to get the previous response again in ASD-STE100 Simplified Technical English — jargon out, technical names kept

Output styles

The output-styles/ folder holds copies of my Claude Code output styles. They are not skills and Claude Code does not load them from this repo — they are kept here so one repo holds the whole setup. A skill loads for a specific task; an output style changes role, tone, and response format for every turn of a session.

FileNamePurpose
output-styles/eli5.mdELI5Plain language for the end of a long day — short sentences, at most two options with a recommendation
output-styles/phdadvisor.mdPhDAdvisorShort, sharp intuition for a 2nd-year finance PhD — intuition, then formalism, then the catch

Install and activation instructions are in output-styles/README.md. These are copies; the live files live in ~/.claude/output-styles/ and do not sync automatically.

Presentations

presentations/ holds talks given about this repo. Currently:

  • Claude Code Skills for Academic Researchers — A Practical Introduction (UTS Finance Department Brownbag, March 2026, 28 slides)

Slides only; the Beamer sources live elsewhere. See presentations/README.md.

Adding a new skill

  1. Create a new folder with a descriptive name
  2. Add a SKILL.md file with YAML frontmatter (name and description)
  3. Test with a natural prompt in Claude Code
  4. Iterate until stable
  5. Commit and push

Notes

  • Skills are plain Markdown
  • The description field is the most important line in any skill — Claude uses it to decide whether to load the skill
  • GitHub is the cloud backup

Contributors

aspi6246

49 commits

aspi6246/Claude-Code-Skills-for-Academics

A collection of Skills for academics.

153

stars

49

commits

Python

primary language

Aug 21, 2026

updated

README

Claude Code Skills

Personal skills repo for academic empirical finance research workflows.

Repo layout

~/.claude/skills/
├── <skill-name>/       one folder per skill, each with a SKILL.md
├── output-styles/      copies of my Claude Code output styles
├── presentations/      talks given about this repo
└── README.md

Skill folders have to stay at the top level. Claude Code discovers personal skills at exactly ~/.claude/skills/<skill-name>/SKILL.md and does not look any deeper, so the skills cannot be tidied into a skills/ subfolder — they would silently stop loading. (Nested .claude/skills/ directories are supported inside a project, but that is a monorepo feature and does not apply here.)

output-styles/ and presentations/ are safe as siblings: a folder with no SKILL.md in it is ignored by skill discovery.

Setup

Fresh install (empty ~/.claude/skills/)

Clone this repo directly into the Claude Code global skills directory:

git clone https://github.com/aspi6246/Claude-Code-Skills-for-Academics.git "$HOME\.claude\skills"

Selective install (skills directory already exists)

If ~/.claude/skills/ already contains other skills, do not clone on top of it — it will fail. Instead, clone into a temporary location and copy only the skills you want:

git clone https://github.com/aspi6246/Claude-Code-Skills-for-Academics.git "$HOME\claude-skills-tmp"
Copy-Item "$HOME\claude-skills-tmp\wrap-up" "$HOME\.claude\skills\" -Recurse
# repeat for each desired skill, then remove the temp dir
Remove-Item "$HOME\claude-skills-tmp" -Recurse -Force

Updating

After editing skills on GitHub or locally:

cd "$HOME\.claude\skills"
git pull

Skills

SkillPurpose
r-empirical-financeR code conventions for panel data, causal inference, and data pipelines (data.table, fixest, arrow)
beamer-slides-teachingLaTeX Beamer slide generation with pdfLaTeX and UTS house style
beamer-checkCompile → inspect → fix → verify audit loop for Beamer decks
code-auditTwo-phase code review for research scripts, with safeguards for licensed data
data-profilerSystematic dataset profiling protocol — unit of observation, panel structure, data quality
paper-editorSeven-audit editorial review protocol for academic finance working papers
paper-reviewStructured summary template for academic papers
edmans-auditPre-submission paper audit against Edmans' (2025) three-part framework: Contribution, Execution, Exposition
canvas-lms-apiCanvas LMS REST API conventions for course sync scripts (modules, pages, file uploads)
spin-upStart-of-session briefing — git state, last log, pinboard, active output style, project state synthesis
wrap-upEnd-of-session cleanup — log, memory, pinboard, session-scoped git commit
script-registryTrack R Markdown script dependencies, inputs/outputs, and paper targets via per-script YAML metadata
code-sweepEnd-of-milestone audit of the Code/ folder for drift between scripts, registry, outputs, and paper — propose-and-confirm fixes
skill-writing-guideReference for writing and improving skills
pinboardQuick-capture pinboard for to-dos, paper leads, data issues, and ideas
glossaryPer-project glossary of definitions, abbreviations, and command-phrases, loaded adaptively at session start
wtfType "wtf" to get the previous response again in ASD-STE100 Simplified Technical English — jargon out, technical names kept

Output styles

The output-styles/ folder holds copies of my Claude Code output styles. They are not skills and Claude Code does not load them from this repo — they are kept here so one repo holds the whole setup. A skill loads for a specific task; an output style changes role, tone, and response format for every turn of a session.

FileNamePurpose
output-styles/eli5.mdELI5Plain language for the end of a long day — short sentences, at most two options with a recommendation
output-styles/phdadvisor.mdPhDAdvisorShort, sharp intuition for a 2nd-year finance PhD — intuition, then formalism, then the catch

Install and activation instructions are in output-styles/README.md. These are copies; the live files live in ~/.claude/output-styles/ and do not sync automatically.

Presentations

presentations/ holds talks given about this repo. Currently:

  • Claude Code Skills for Academic Researchers — A Practical Introduction (UTS Finance Department Brownbag, March 2026, 28 slides)

Slides only; the Beamer sources live elsewhere. See presentations/README.md.

Adding a new skill

  1. Create a new folder with a descriptive name
  2. Add a SKILL.md file with YAML frontmatter (name and description)
  3. Test with a natural prompt in Claude Code
  4. Iterate until stable
  5. Commit and push

Notes

  • Skills are plain Markdown
  • The description field is the most important line in any skill — Claude uses it to decide whether to load the skill
  • GitHub is the cloud backup

Contributors

aspi6246

49 commits

Languages

Python

87.6%

TeX

12.4%