Skip to main content
Run any Skill in Manus
with one click
aspi6246
GitHub creator profile

aspi6246

Repository-level view of 16 collected skills across 1 GitHub repositories, including approximate occupation coverage.

skills collected
16
repositories
1
occupation fields
4
updated
2026-06-02
repository explorer

Repositories and representative skills

#001
Claude-Code-Skills-for-Academics
16 skills13026updated 2026-06-02
100% of creator
script-registry
software-developers

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`.

2026-06-02
code-sweep
software-developers

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`; reuses its `registry:` YAML block and `Code/_Claude Scripts/build_registry.R` builder rather than redefining either.

2026-06-02
glossary
technical-writers

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 include "add to glossary", "glossary: X means Y", "define X for this project", "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". Also use proactively: offer to capture a term when the user defines one in 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.

2026-05-28
spin-up
software-developers

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 briefing. Performs: git status check (unpushed commits, remote 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.

2026-05-28
edmans-audit
software-developers

Audit a finance paper against Alex Edmans' "Learnings From 1,000 Rejections" (2025, Financial Management) three-part framework: Contribution, Execution, 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".

2026-05-27
canvas-lms-api
software-developers

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.

2026-04-24
wrap-up
secretaries-and-administrative-assistants-except-legal-medical-and-executive

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.

2026-04-24
pinboard
secretaries-and-administrative-assistants-except-legal-medical-and-executive

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."

2026-04-13
Showing top 8 of 16 collected skills in this repository.
Showing 1 of 1 repositories
All repositories loaded