PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Per-project glossary of key definitions, abbreviations, and command-phrases, stored in GLOSSARY.md at the project root.
No licenceAuto-check passed
Install Glossary
$ npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aspi6246/Claude-Code-Skills-for-Academics glossary --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aspi6246/Claude-Code-Skills-for-Academics.git skills-src && mkdir -p .claude/skills && cp -r skills-src/glossary .claude/skills/glossary && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "glossary" agent skill from https://github.com/aspi6246/Claude-Code-Skills-for-Academics/tree/main/glossary into .claude/skills/glossary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glossary", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aspi6246/Claude-Code-Skills-for-Academics/tree/main/glossaryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aspi6246/Claude-Code-Skills-for-Academics glossary --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aspi6246/Claude-Code-Skills-for-Academics.git skills-src && mkdir -p .agents/skills && cp -r skills-src/glossary .agents/skills/glossary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "glossary" agent skill from https://github.com/aspi6246/Claude-Code-Skills-for-Academics/tree/main/glossary into .agents/skills/glossary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glossary", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aspi6246/Claude-Code-Skills-for-Academics glossary --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aspi6246/Claude-Code-Skills-for-Academics.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/glossary .cursor/skills/glossary && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "glossary" agent skill from https://github.com/aspi6246/Claude-Code-Skills-for-Academics/tree/main/glossary into .cursor/skills/glossary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glossary", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aspi6246/Claude-Code-Skills-for-Academics.git --path glossary--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aspi6246/Claude-Code-Skills-for-Academics glossary --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aspi6246/Claude-Code-Skills-for-Academics.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/glossary .gemini/skills/glossary && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "glossary" agent skill from https://github.com/aspi6246/Claude-Code-Skills-for-Academics/tree/main/glossary into .gemini/skills/glossary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glossary", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aspi6246/Claude-Code-Skills-for-Academics glossaryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aspi6246/Claude-Code-Skills-for-Academics.git skills-src && mkdir -p .github/skills && cp -r skills-src/glossary .github/skills/glossary && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "glossary" agent skill from https://github.com/aspi6246/Claude-Code-Skills-for-Academics/tree/main/glossary into .github/skills/glossary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glossary", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aspi6246/Claude-Code-Skills-for-Academics glossary --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aspi6246/Claude-Code-Skills-for-Academics.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/glossary .opencode/skills/glossary && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "glossary" agent skill from https://github.com/aspi6246/Claude-Code-Skills-for-Academics/tree/main/glossary into .opencode/skills/glossary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "glossary", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
glossary- GitHub stars
- 159
- Token cost
- ~2.2k tokens
- SKILL.md length
- 1,070 words
- Files
- 1
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- None found
At a glance
Per-project glossary of key definitions, abbreviations, and command-phrases, stored in GLOSSARY.md at the project root.
- Works in 3 steps: Categorise the entry — a phrase mapping… → Append silently under the right section… → Acknowledge in one line — "Added to the…
- The user defines
- SKILL.md covers How the glossary is used, Command-phrases (behavioral), Adding entries and Showing, editing, removing, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Glossary is an agent skill from aspi6246/Claude-Code-Skills-for-Academics. 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…
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with GitHub. The repository describes itself as: A collection of Skills for academics.
When your agent uses it
- The user defines
- Asks about a project-specific term — variable names
- Sets up a command-phrase (a phrase that maps to an action
- Include add to glossary
Example prompts
- “= commit and push the paper to GitHub). Triggers include”
- “glossary: X means Y”
- “define X for this project”
- “/glossary”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Categorise the entry — a phrase mapping to an action → Command-Phrase; an
- Append silently under the right section in GLOSSARY.md. Don't reorder or
- Acknowledge in one line — "Added to the glossary." Don't read it back.
What it can do on your machine
Read from SKILL.md and the folder at commit 8a8f112. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Glossary loads about 2.2k tokens when it runs. Until then it costs about 213 tokens; SKILL.md has 1,070 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,070 words (~2,230 tokens).
“A project-local dictionary of the definitions, abbreviations, and command-phrases that matter for this project. Stored in GLOSSARY.md at the project root, so each project keeps its own. The skill definition is global; the data is per-project — the same split…”
- name
- glossary
Files
Just SKILL.md in glossary of aspi6246/Claude-Code-Skills-for-Academics.
Open the folder on GitHubat commit 8a8f112
Compare with similar skills
Glossary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Glossary this skillaspi6246/Claude-Code-Skills-for-Academics | 159 | — | ~2.2k | Automated safety check: Pass | None | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Superpowers Sessionsobra/superpowers | 297k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Update V8 Versionopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Update V8 Version
openinterpreter/openinterpreter
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
More from aspi6246/Claude-Code-Skills-for-Academics
All 15 skills in this repoBeamer Check
aspi6246/Claude-Code-Skills-for-Academics
Audit and fix Beamer slide decks for compilation errors, layout problems, and visual issues.
Beamer Slides Teaching
aspi6246/Claude-Code-Skills-for-Academics
Generate LaTeX Beamer slide decks using my defined style and conventions.
Data Profiler
aspi6246/Claude-Code-Skills-for-Academics
Systematic dataset profiling protocol for empirical research.
Edmans Audit
aspi6246/Claude-Code-Skills-for-Academics
Audit a finance paper against Alex Edmans' "Learnings From 1,000 Rejections" (2025, Financial Management) three-part framework: Contribution, Execution, Exposition.
R Empirical Finance
aspi6246/Claude-Code-Skills-for-Academics
Conventions for writing empirical finance R code with data.table, fixest, arrow, and ggplot2.
Top5 Framing
aspi6246/Claude-Code-Skills-for-Academics
Diagnose and raise the general-interest ceiling of an academic economics or finance paper so it reads like a top-5 (or top-3 finance) submission.
Related
Works with
Questions about Glossary
What does Glossary do?
Per-project glossary of key definitions, abbreviations, and command-phrases, stored in GLOSSARY.md at the project root. Glossary is an agent skill from aspi6246/Claude-Code-Skills-for-Academics.md at the project root.
When should I use Glossary?
Glossary fits situations like: the user defines; asks about a project-specific term — variable names; sets up a command-phrase (a phrase that maps to an action; include add to glossary.
How do I install Glossary in Claude Code?
Run `npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a claude-code`. Or copy the skill folder (glossary in aspi6246/Claude-Code-Skills-for-Academics) into .claude/skills/glossary in your project. Claude Code loads it when a task matches its description.
How do I install Glossary in Codex?
Run `npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a codex`. Or copy the skill folder (glossary in aspi6246/Claude-Code-Skills-for-Academics) into .agents/skills/glossary in your project. Codex loads it when a task matches its description.
Can I use Glossary in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aspi6246/Claude-Code-Skills-for-Academics --skill glossary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/glossary, .gemini/skills/glossary, .github/skills/glossary and .opencode/skills/glossary in your project.
What does Glossary need to run?
SKILL.md names no scripts, command-line tools or credentials: Glossary is instructions for the agent only.
Does Glossary access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Glossary safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Glossary use?
No licence was found for Glossary or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Glossary use?
About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Glossary?
Skills that share tags, products or a category with Glossary: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 297k stars), Greploop (onyx-dot-app/onyx, 32k stars) and GitHub Deep Research (bytedance/deer-flow, 84k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Glossary?
aspi6246 (a GitHub user) maintains it in aspi6246/Claude-Code-Skills-for-Academics, which has 159 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on August 21, 2026.
Source: aspi6246/Claude-Code-Skills-for-Academics on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.