16 skills published by aspi6246 across 1 repository. Together they weigh 44 681 tokens — that is what loading all of them at once would cost you in context.
16 skills 44 681 tokens total
> Audit and fix Beamer slide decks for compilation errors, layout problems, and visual issues. Use this skill whenever the user says "check my slides", "fix my slides", "the slides don't compile", "text is running off the page", "slides look wrong", or after generating a Beamer deck to verify it before delivering. Also use when the user mentions overfull boxes, overlapping content, broken images, or any Beamer formatting issue.
> Generate LaTeX Beamer slide decks using my defined style and conventions. Use this skill whenever the user asks to create slides, a presentation, a lecture deck, or Beamer content — for teaching.
> Use this skill whenever working with the Canvas LMS REST API — including creating or updating modules, pages, and files for a course, building sync scripts, managing course structure programmatically, or uploading files and linking them in pages. Trigger this skill any time the user mentions Canvas, LMS, course sync, module pages, or file uploads to Canvas. Also use when writing or debugging any Python script that calls the Canvas API.
> Two-phase code audit workflow for empirical research scripts. Use this skill when the user asks to review, audit, check, validate, or verify R or Python research code — especially code that processes licensed or sensitive data (WRDS, CRSP, WellDatabase, PLIDA). Also use when the user says "check my code", "review this script", "does this look right", or "audit my analysis."
> End-of-milestone audit of a research project's `Code/` folder against the paper and outputs. Surfaces drift between scripts, YAML headers, the script registry, outputs, raw data, and the paper. Categorises findings as MUST-FIX or SUGGESTED and proposes fixes one at a time for the user to confirm. Use this skill when the user says "code sweep", "sweep the code", "run a code sweep", "audit my code folder", "check code freshness", "is everything up to date", "any stale outputs", "audit code consistency", or similar — typically before a paper submission, milestone, or share. Extends `script-registry`; builder rather than redefining either.
> Systematic dataset profiling protocol for empirical research. Use this skill when the user has a new dataset and wants to understand it before analysis — including unit of observation, variable definitions, panel structure, data quality, and descriptive statistics. Trigger on phrases like "explore this data", "profile this dataset", "what's in this data", "understand this dataset", "describe this data", "what are the variables", "check the panel structure", or any request to examine a dataset before running regressions.
> 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".
> Per-project glossary of key definitions, abbreviations, and command-phrases, stored in `GLOSSARY.md` at the project root. Use this skill when the user defines or asks about a project-specific term — variable names, dataset or database names, acronyms — or sets up a command-phrase (a phrase that maps to an action, e.g. "push" = commit and push the paper to GitHub). Triggers "what does X mean here", "what does X stand for", "from now on X means Y", "show the glossary", "what's in our glossary", and "remove X from glossary". passing, or when you hit an undefined abbreviation or variable name in their code or data. Loaded at session start by `/spin-up` so command-phrases stay active.
> Seven-audit editorial review protocol for academic finance working papers. Use this skill when the user asks to review, edit, audit, or critique a working paper, manuscript, or draft — including "run The Editor", "review my paper", "audit this draft", "check if this is ready for submission", "what would Referee 2 say", or any request to evaluate a paper for journal submission. Also use when the user mentions R&R, revise and resubmit, or responding to referee reports.
> Produce a structured summary of an academic working paper or published article. Use this skill when the user shares a paper, asks to summarise a paper, says "what's this paper about", "review this paper", "summarise this for me", or provides a PDF/link to an academic article.
> Digital pinboard for quick project notes, reminders, and ideas. Use this skill when the user wants to jot down a note, reminder, to-do, paper to read, idea, or data issue — including phrases like "pin this", "note to self", "remind me to", "add to pinboard", "I need to remember to", "check out this paper", "look into this later", "jot this down", "don't let me forget", or any quick note the user wants saved for later. Also use when the user says "show my pinboard", "what's on my pinboard", "mark X as done", or "clear my pinboard."
> Conventions for writing empirical finance R code with data.table, fixest, arrow, and ggplot2. Use this skill whenever writing, reviewing, refactoring, or debugging R scripts for panel data, event studies, DiD, IV/2SLS, regressions, or data pipelines — even if the user just says "write some R code" or "clean this data."
Use when creating a new `.Rmd` script in `Code/`, editing the `registry:` YAML block of an existing script in `Code/`, moving a `Code/*.Rmd` into `_Archive/`, or when the user says "update registry", "show registry", or "which script makes X". Before writing any new `Code/*.Rmd` script, read `Code/REGISTRY.md` first and surface existing matches before starting fresh. After any YAML change, run `Code/_Claude Scripts/build_registry.R` to refresh `Code/REGISTRY.md`.
> Reference for writing and improving Claude Code skills. Use when the user asks to create a new skill, improve an existing skill, turn a conversation workflow into a reusable skill, or says anything like "make this a skill", "save this as a skill", or "let's capture this."
> Start-of-session orientation routine that briefs Claude on the current state of a project before work begins. Use this skill when the user says "spin up", "spin it up", "let's go", "start up", "spin up the project", "punch it chewy", or any variant signalling they want a session kickoff divergence), CLAUDE.md and README read, most-recent session log read (focusing on "Where we left off"), PINBOARD.md open items, GLOSSARY.md load, and a short synthesis of project state. Ends by asking what to work on today.
> End-of-session cleanup routine that captures all session work before context is lost. Use this skill when the user says "wrap up", "wrap-up", "let's wrap it up", "let's wrap up", "wind down", "end session", "that's it for today", "save and close", "let's call it", "close out", "done for today", or any indication they are finishing a work session and want everything documented before starting fresh.