How do I install the Ragnarok Install skill?

Run npx skillmds@latest add castorini/ragnarok-install in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ragnarok Install safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ragnarok Install?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ragnarok Install free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ragnarok Install?

castorini (@castorini) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ragnarok Install by castorini — Agent Skill

Name: Ragnarok Install
Author: castorini

Ragnarok Install

Set up a ragnarok development environment — checks Python 3.11+, installs via uv or pip with cloud extras, and verifies with doctor. Use when someone is onboarding, setting up a fresh clone, or troubleshooting their environment.

castorini 66662f3 2 files · 3.9 KB Updated Sep 17, 2026

File contents

ragnarok Install

Development environment setup for ragnarok — RAG answer generation and TREC evaluation.

Prerequisites

Python 3.11+
Git (SSH access to github.com:castorini)

Verify Runtime

python3 --version   # must be 3.11+
command -v uv       # if present, use uv path; otherwise recommend uv

If uv is on PATH, use it silently. If not, ask the user once: install uv or proceed with pip.

Clone (if needed)

If no pyproject.toml in cwd:

git clone git@github.com:castorini/ragnarok.git && cd ragnarok

Install (source — preferred)

uv path

uv venv --python 3.11
source .venv/bin/activate
uv sync --group dev --extra cloud

pip path

python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[cloud]"
pip install pre-commit pytest

PyPI alternative (mention but don't default to)

pip install pyragnarok

Note: the PyPI package name is pyragnarok, not ragnarok.

Smoke Test

ragnarok doctor --output json
ragnarok --help

Pre-commit (source installs)

pre-commit install

Reference Files

references/extras.md — Optional dependency stacks (cloud, local, api, pyserini)

Gotchas

PyPI name mismatch: the package is published as pyragnarok on PyPI, but the CLI binary and import name are both ragnarok.
ragnarok uses an async-first design — many internal APIs are coroutines.
Dev dependencies use PEP 735 [dependency-groups] — only uv sync --group dev resolves them natively. With pip, install each package manually.
The local extra pulls in PyTorch, vLLM, and transformers — large downloads, only needed for local model inference.
Test directory is test/ (no trailing s).

---name: ragnarok-installdescription: Set up a ragnarok development environment — checks Python 3.11+, installs via uv or pip with cloud extras, and verifies with doctor. Use when someone is onboarding, setting up a fresh clone, or troubleshooting their environment.---# ragnarok InstallDevelopment environment setup for [ragnarok](https://github.com/castorini/ragnarok) — RAG answer generation and TREC evaluation.## Prerequisites- Python 3.11+- Git (SSH access to `github.com:castorini`)## Verify Runtime```bashpython3 --version # must be 3.11+command -v uv # if present, use uv path; otherwise recommend uv```If `uv` is on PATH, use it silently. If not, ask the user once: install uv or proceed with pip.## Clone (if needed)If no `pyproject.toml` in cwd:```bashgit clone git@github.com:castorini/ragnarok.git && cd ragnarok```## Install (source — preferred)### uv path```bashuv venv --python 3.11source .venv/bin/activateuv sync --group dev --extra cloud```### pip path```bashpython3 -m venv .venvsource .venv/bin/activatepip install -e ".[cloud]"pip install pre-commit pytest```### PyPI alternative (mention but don't default to)```bashpip install pyragnarok```Note: the PyPI package name is `pyragnarok`, not `ragnarok`.## Smoke Test```bashragnarok doctor --output jsonragnarok --help```## Pre-commit (source installs)```bashpre-commit install```## Reference Files- `references/extras.md` — Optional dependency stacks (cloud, local, api, pyserini)## Gotchas- **PyPI name mismatch**: the package is published as `pyragnarok` on PyPI, but the CLI binary and import name are both `ragnarok`.- ragnarok uses an async-first design — many internal APIs are coroutines.- Dev dependencies use PEP 735 `[dependency-groups]` — only `uv sync --group dev` resolves them natively. With pip, install each package manually.- The `local` extra pulls in PyTorch, vLLM, and transformers — large downloads, only needed for local model inference.- Test directory is `test/` (no trailing s).

Frequently asked questions