Claude
21a0ae09e2
All checks were successful
Integration Tests / test (pull_request) Successful in 30s
115 lines
5.0 KiB
Markdown
115 lines
5.0 KiB
Markdown
---
|
|
name: wiki
|
|
description: >
|
|
Query the RuneScape Wiki (RS3 and OSRS) for item details, quest requirements,
|
|
skill training guides, and Grand Exchange prices. Use this skill whenever the
|
|
user asks anything about RuneScape, Old School RuneScape, OSRS, RS3, or mentions
|
|
game-specific concepts like quests, skills, items, monsters, the Grand Exchange,
|
|
ironman mode, HCIM, or any RuneScape game mechanics. Also trigger when the user
|
|
mentions specific in-game items, quest names, skill names, or boss names that are
|
|
clearly RuneScape-related. Always prefer this skill over answering from memory,
|
|
since it pulls live, authoritative data from the wiki.
|
|
---
|
|
|
|
# RuneScape Wiki Skill
|
|
|
|
This skill provides `rsw`, a CLI that queries the RuneScape Wiki for
|
|
authoritative, up-to-date game data. It supports both **OSRS** and **RS3**.
|
|
|
|
## Setup (first use)
|
|
|
|
The binary is auto-built on session start if Go is available. If the binary is
|
|
missing, compile it manually:
|
|
|
|
```bash
|
|
cd ${CLAUDE_PLUGIN_ROOT}/scripts/rsw && go build -o rsw .
|
|
```
|
|
|
|
The binary lives at `${CLAUDE_PLUGIN_ROOT}/scripts/rsw/rsw`.
|
|
|
|
If Go is not installed, tell the user they need Go 1.22+ (`go.dev/dl`).
|
|
|
|
## Commands
|
|
|
|
The first argument is always the game: `osrs` or `rs3`.
|
|
|
|
### rsw <game> search <query>
|
|
Full-text search across wiki pages. Returns ranked titles with snippets.
|
|
Use this to find the right page name before fetching details.
|
|
|
|
### rsw <game> page <title> [--section <name>] [--complete]
|
|
Fetch a wiki page. By default, returns only the table of contents (section list)
|
|
to conserve context. Use `--section` to fetch a specific section (e.g., "Drops",
|
|
"Strategy", "Requirements"). Use `--complete` for the full page content.
|
|
Use `--raw` for raw wikitext.
|
|
|
|
**Recommended workflow:** First call `page` (no flags) to see available sections,
|
|
then call `page --section <name>` to fetch only what you need.
|
|
|
|
### rsw <game> item <name> [--ironman]
|
|
The workhorse for "where do I find X" questions. Returns:
|
|
- Item stats (examine, weight, alch values, quest association)
|
|
- Equipment bonuses (if applicable)
|
|
- GE price (buy/sell, volume) — or vendor/alch values with `--ironman`
|
|
- Drop sources (monster, quantity, rarity)
|
|
- Acquisition methods from the wiki page
|
|
|
|
### rsw <game> quest <name> [--ironman]
|
|
Quest details: skill requirements, quest prerequisites, items needed, enemies
|
|
to defeat, and rewards. With `--ironman`, adds notes about self-sufficient
|
|
item acquisition and HCIM combat safety.
|
|
|
|
### rsw <game> skill <name> [--level <range>] [--ironman]
|
|
Training guide for a skill. Use `--level 50-70` to filter to a specific range.
|
|
With `--ironman`, notes which methods work without GE access.
|
|
|
|
### rsw <game> price <name> [--ironman]
|
|
Real-time GE price: instant buy/sell, recent volume, trend data.
|
|
With `--ironman`, shows alch values and store prices instead.
|
|
|
|
## Global Flags
|
|
|
|
- `--ironman` / `-i` — Shifts output to self-sufficient play: hides GE prices,
|
|
shows vendor/alch values, emphasizes drop sources and shop locations.
|
|
- `--raw` — Output raw wikitext (for page command).
|
|
|
|
## How to Answer Questions
|
|
|
|
When a user asks a RuneScape question, think about which command(s) to combine:
|
|
|
|
**"Where can I find a dragon scimitar?"**
|
|
→ `rsw osrs item "dragon scimitar"` — shows drop sources and acquisition
|
|
→ If it's a quest reward, follow up with `rsw osrs quest "Monkey Madness I"`
|
|
|
|
**"What are the requirements for Desert Treasure?"**
|
|
→ `rsw osrs quest "Desert Treasure"`
|
|
|
|
**"How do I train Prayer from 43 to 70 as an ironman?"**
|
|
→ `rsw osrs skill prayer --level 43-70 --ironman`
|
|
→ May also want `rsw osrs item "dragon bones" --ironman` for acquisition info
|
|
|
|
**"What's the current price of an abyssal whip?"**
|
|
→ `rsw osrs price "abyssal whip"`
|
|
|
|
**"What's a good money maker at 80 combat?"**
|
|
→ `rsw osrs search "money making"` → then `rsw osrs page "Money making guide"` (TOC)
|
|
→ then `rsw osrs page "Money making guide" --section "Combat"` for relevant section
|
|
|
|
### Inferring the game
|
|
|
|
**Always determine the game before running any command.** Use the following rules:
|
|
|
|
1. **Use stated preference**: If the user has said which game they play earlier in the conversation, use that — no need to ask again.
|
|
2. **Strong context clues**: A few terms are exclusive to one game:
|
|
- OSRS-only: "leagues", "deadman", quest names unique to OSRS (e.g. "Monkey Madness II")
|
|
- RS3-only: "invention", "archaeology", "divination", "EoC", "revolution", "legacy mode"
|
|
3. **When in doubt, ask**: If you cannot confidently determine the game from context, **always ask before running any wiki command**. Do not guess. A short question like "Are you playing OSRS or RS3?" takes one message and prevents a useless lookup.
|
|
|
|
Most content (items, monsters, skills, quests) exists in both games with different stats, locations, and mechanics — so defaulting to one silently is likely wrong.
|
|
|
|
### Combining outputs
|
|
|
|
Don't just dump raw CLI output. Read it, synthesize an answer, and cite specifics.
|
|
If the user asks "how do I get a fire cape", run the search, pull the relevant
|
|
page sections, and give them a coherent strategy — not a wall of wikitext.
|