Skip to content
Back to search

Claude-Code-Skills-for-Academics

A collection of Skills for academics.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/aspi6246--claude-code-skills-for-academics/badge.svg)](/listings/aspi6246--claude-code-skills-for-academics)

HTML

<a href="/listings/aspi6246--claude-code-skills-for-academics"><img src="/api/listings/aspi6246--claude-code-skills-for-academics/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

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

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 118 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Claude Code Skills
  2. Personal skills repo for academic empirical finance research workflows.
  3. ## Repo layout
  4. ```
  5. ~/.claude/skills/
  6. ├── <skill-name>/ one folder per skill, each with a SKILL.md
  7. ├── output-styles/ copies of my Claude Code output styles
  8. ├── presentations/ talks given about this repo
  9. └── README.md
  10. ```
  11. **Skill folders have to stay at the top level.** Claude Code discovers
  12. personal skills at exactly `~/.claude/skills/<skill-name>/SKILL.md` and does
  13. not look any deeper, so the skills cannot be tidied into a `skills/`
  14. subfolder — they would silently stop loading. (Nested `.claude/skills/`
  15. directories are supported inside a project, but that is a monorepo feature
  16. and does not apply here.)
  17. `output-styles/` and `presentations/` are safe as siblings: a folder with no
  18. `SKILL.md` in it is ignored by skill discovery.
  19. ## Setup
  20. ### Fresh install (empty `~/.claude/skills/`)
  21. Clone this repo directly into the Claude Code global skills directory:
  22. ```powershell
  23. git clone https://github.com/aspi6246/Claude-Code-Skills-for-Academics.git "$HOME\.claude\skills"
  24. ```
  25. ### Selective install (skills directory already exists)
  26. If `~/.claude/skills/` already contains other skills, do **not** clone
  27. on top of it — it will fail. Instead, clone into a temporary location
  28. and copy only the skills you want:
  29. ```powershell
  30. git clone https://github.com/aspi6246/Claude-Code-Skills-for-Academics.git "$HOME\claude-skills-tmp"
  31. Copy-Item "$HOME\claude-skills-tmp\wrap-up" "$HOME\.claude\skills\" -Recurse
  32. # repeat for each desired skill, then remove the temp dir
  33. Remove-Item "$HOME\claude-skills-tmp" -Recurse -Force
  34. ```
  35. ## Updating
  36. After editing skills on GitHub or locally:
  37. ```powershell
  38. cd "$HOME\.claude\skills"
  39. git pull
  40. ```
  41. ## Skills
  42. | Skill | Purpose |
  43. |---|---|
  44. | `r-empirical-finance` | R code conventions for panel data, causal inference, and data pipelines (data.table, fixest, arrow) |
  45. | `beamer-slides-teaching` | LaTeX Beamer slide generation with pdfLaTeX and UTS house style |
  46. | `beamer-check` | Compile → inspect → fix → verify audit loop for Beamer decks |
  47. | `code-audit` | Two-phase code review for research scripts, with safeguards for licensed data |
  48. | `data-profiler` | Systematic dataset profiling protocol — unit of observation, panel structure, data quality |
  49. | `paper-editor` | Seven-audit editorial review protocol for academic finance working papers |
  50. | `paper-review` | Structured summary template for academic papers |
  51. | `edmans-audit` | Pre-submission paper audit against Edmans' (2025) three-part framework: Contribution, Execution, Exposition |
  52. | `canvas-lms-api` | Canvas LMS REST API conventions for course sync scripts (modules, pages, file uploads) |
  53. | `spin-up` | Start-of-session briefing — git state, last log, pinboard, active output style, project state synthesis |
  54. | `wrap-up` | End-of-session cleanup — log, memory, pinboard, session-scoped git commit |
  55. | `script-registry` | Track R Markdown script dependencies, inputs/outputs, and paper targets via per-script YAML metadata |
  56. | `code-sweep` | End-of-milestone audit of the Code/ folder for drift between scripts, registry, outputs, and paper — propose-and-confirm fixes |
  57. | `skill-writing-guide` | Reference for writing and improving skills |
  58. | `pinboard` | Quick-capture pinboard for to-dos, paper leads, data issues, and ideas |
  59. | `glossary` | Per-project glossary of definitions, abbreviations, and command-phrases, loaded adaptively at session start |
  60. | `wtf` | Type "wtf" to get the previous response again in ASD-STE100 Simplified Technical English — jargon out, technical names kept |
  61. ## Output styles
  62. The `output-styles/` folder holds copies of my Claude Code output styles.
  63. They are **not skills** and Claude Code does not load them from this repo —
  64. they are kept here so one repo holds the whole setup. A skill loads for a
  65. specific task; an output style changes role, tone, and response format for
  66. every turn of a session.
  67. | File | Name | Purpose |
  68. |---|---|---|
  69. | `output-styles/eli5.md` | `ELI5` | Plain language for the end of a long day — short sentences, at most two options with a recommendation |
  70. | `output-styles/phdadvisor.md` | `PhDAdvisor` | Short, sharp intuition for a 2nd-year finance PhD — intuition, then formalism, then the catch |
  71. Install and activation instructions are in
  72. [`output-styles/README.md`](output-styles/README.md). These are copies; the
  73. live files live in `~/.claude/output-styles/` and do not sync automatically.
  74. ## Presentations
  75. `presentations/` holds talks given about this repo. Currently:
  76. - **Claude Code Skills for Academic Researchers — A Practical Introduction**
  77. (UTS Finance Department Brownbag, March 2026, 28 slides)
  78. Slides only; the Beamer sources live elsewhere. See
  79. [`presentations/README.md`](presentations/README.md).
  80. ## Adding a new skill
  81. 1. Create a new folder with a descriptive name
  82. 2. Add a `SKILL.md` file with YAML frontmatter (`name` and `description`)
  83. 3. Test with a natural prompt in Claude Code
  84. 4. Iterate until stable
  85. 5. Commit and push
  86. ## Notes
  87. - Skills are plain Markdown
  88. - The `description` field is the most important line in any skill — Claude uses it to decide whether to load the skill
  89. - GitHub is the cloud backup

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.