| name | research-skill-installer |
| description | Install, update, sync back, list, inspect, or remove skills between this repository's Research-skills-hub and both Codex (.agents/skills) and Claude Code (.claude/skills). Use when the user wants Codex or Claude Code to use a hub skill, promote edits from an installed skill back to the hub, sync installed skills across both agent directories, check which research skills are installed, or manage Research-skills-hub collections. |
Research Skill Installer
Use this skill to manage skills stored under research-skills-hub/.
The installer always treats both agent directories as the target:
.agents/skills/ for Codex..claude/skills/ for Claude Code.
Run commands from the repository root unless you pass --repo.
Skills are discovered at research-skills-hub/<collection>/<skill>/SKILL.md. A
collection may also group skills into a bundle folder that has no SKILL.md
of its own (for example collected-skills/productivity/); nested skills inside
such a bundle (collected-skills/productivity/grill-me/SKILL.md) are discovered
and installed by their own name (grill-me) into .agents/skills/ and
.claude/skills/.
Commands
List available hub skills:
python research-skills-hub/open-paper-skills/research-skill-installer/scripts/install_research_skill.py list
Check installed status:
python research-skills-hub/open-paper-skills/research-skill-installer/scripts/install_research_skill.py status
python research-skills-hub/open-paper-skills/research-skill-installer/scripts/install_research_skill.py status research-bible
Install a skill into both Codex and Claude Code:
python research-skills-hub/open-paper-skills/research-skill-installer/scripts/install_research_skill.py install research-bible
If the skill exists in more than one collection, specify the collection:
python research-skills-hub/open-paper-skills/research-skill-installer/scripts/install_research_skill.py install uv --collection science-skills
Update an already-installed skill:
python research-skills-hub/open-paper-skills/research-skill-installer/scripts/install_research_skill.py install research-bible --update
Promote edits from an installed copy back to the hub, then sync both installed
copies:
python research-skills-hub/open-paper-skills/research-skill-installer/scripts/install_research_skill.py sync-back research-bible --from agents
python research-skills-hub/open-paper-skills/research-skill-installer/scripts/install_research_skill.py sync-back research-bible --from claude
If both installed copies changed differently, the command stops. To deliberately
use one side as the source of truth:
python research-skills-hub/open-paper-skills/research-skill-installer/scripts/install_research_skill.py sync-back research-bible --from agents --force
Preview without writing:
python research-skills-hub/open-paper-skills/research-skill-installer/scripts/install_research_skill.py install research-bible --dry-run
python research-skills-hub/open-paper-skills/research-skill-installer/scripts/install_research_skill.py sync-back research-bible --from agents --dry-run
Remove a skill from both installed locations:
python research-skills-hub/open-paper-skills/research-skill-installer/scripts/install_research_skill.py remove research-bible --yes
Workflow
- Use
list or status first if the requested skill name is uncertain.
- Use
install <skill> for new installs.
- Use
install <skill> --update only when replacing an installed copy is intended.
- Use
sync-back <skill> --from agents|claude when a skill was edited inside .agents/skills/ or .claude/skills/ and the hub should become the canonical copy.
- After installing, updating, or syncing back, run
status <skill> to confirm both targets are installed and match the hub source.
- If public top-level entrypoints changed in the same task, run
filetree-simple generate, then filetree-simple lint.
Guardrails
- Do not manually copy a hub skill when this script can do it.
- Do not use
--update unless the user asked to update/reinstall or the installed copy is known to be stale.
- Do not use
sync-back --force unless the user chose which installed copy should win.
- Do not remove a skill without an explicit user request;
remove requires --yes.
- Review a collected skill's
SKILL.md and bundled scripts before installing it from collected-skills or another third-party collection.
