ワンクリックでManusで任意のスキルを実行

rumil-search

スター2

フォーク1

更新日2026年4月15日 05:51

Embedding-based search over the active rumil workspace. Takes a free-text query and returns the most semantically similar pages (questions, claims, judgements, concepts). Default mode is a fast top-N lookup with similarity scores — use proactively mid-conversation to check what the workspace already knows about a topic, find related research, or check for duplicates before creating a new question. Pass --full for the multi-tier context builder when you want a deeper rendered read.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

chaosGuppy

chaosGuppy/rumil

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

rumil-search

Free-text semantic search across the active workspace.

Modes

default (quick) — top-N pages at ABSTRACT detail with similarity scores. Fast and cheap. Use this first. --limit N controls the number of results (default 8).
--full — the multi-tier context builder used inside real rumil calls. Returns a richer rendered block (full pages + summaries within configured char budgets). Reach for this when you want a deep read, not just a pointer list.

setopt no_glob 2>/dev/null; set -f; PYTHONPATH=.claude/lib uv run python -m rumil_skills.search_workspace $ARGUMENTS

このリポジトリの他の Skills

同じリポジトリ

rumil-versus-iterate

chaosGuppy/rumil

Iterate on versus's pipeline — review recent (or freshly-fired) completion / judging runs, identify concrete improvement opportunities, test them via /rumil-forks, and consolidate findings into a ranked punch list. Spawns parallel agents for trace investigation and fork experiments so wall-clock stays low. Use when the user wants to "review the recent versus runs and find improvements," "play with these traces," "see what we could do better in d&e / two_phase," or anytime after a versus generation/judging batch when it's worth turning the runs into actionable code/prompt changes. Default scope is one forethought essay × Sonnet × budget 4, but every input is overridable.

2026-05-042

rumil-system

chaosGuppy/rumil

Background knowledge for working with the rumil research workspace from Claude Code. Explains the two-lane provenance model (rumil-mediated vs cc-mediated), when to use which rumil-* skill, how workspace/session state works, and the visibility/attribution story. Auto-load this whenever the user asks about rumil, wants to inspect research, dispatch a call, discuss a question, apply moves, or review a trace.

2026-05-022

rumil-versus-complete

chaosGuppy/rumil

Run orchestrator-driven essay completions for the versus pairwise-eval pipeline. Per essay × prefix × model × workflow, fires a rumil orchestrator (TwoPhase, DraftAndEdit) and writes the resulting continuation as a `versus_texts` row tagged `kind="completion"`, `source_id="orch:<workflow>:<model>:c<hash8>"` — pickable as a contestant by `rumil-versus-judge` afterwards. Use when the user wants to A/B orchestrator-produced continuations against single-shot model continuations or against the human baseline. Both `--orch two_phase` and `--orch draft_and_edit` are usable. For single-shot completions (no orch), use `rumil-versus-generate`.

2026-05-022

rumil-versus-judge

chaosGuppy/rumil

Run pairwise judgments on versus essay-continuation pairs. Default mode is the unified blind path (single-turn LLM call, no tools, no DB) — claude-* models route direct to Anthropic, others through OpenRouter. --variant orch fires a full TwoPhaseOrchestrator run per pair. Use when the user wants to measure how rumil discriminates on pairs with known ground truth (human continuation vs. model continuations), compare blind judges against workspace-aware ones, or top up pending judgments after adding new dimensions or models.

2026-05-022

rumil-load-run

chaosGuppy/rumil

Load a rumil run into the conversation by run ID. Shows a tree of every call in the run (id, type, status, cost, event summary) grouped under the run. Use when you have a trace URL like /traces/<run_id> and want to see the whole run, not a single call. For one call's verbatim trace use rumil-trace instead. Pass --compare <other_run_id> to A/B two runs side-by-side.

2026-05-022

rumil-trace

chaosGuppy/rumil

Dump a rumil call's full execution trace — trace events plus every LLM exchange verbatim (system prompt, user message, response, tool calls). Use to inspect what happened inside a specific call, debug model confusion, or review a run for quality. Takes a short (8-char) or full call ID.

2026-05-022

name	rumil-search
description	Embedding-based search over the active rumil workspace. Takes a free-text query and returns the most semantically similar pages (questions, claims, judgements, concepts). Default mode is a fast top-N lookup with similarity scores — use proactively mid-conversation to check what the workspace already knows about a topic, find related research, or check for duplicates before creating a new question. Pass --full for the multi-tier context builder when you want a deeper rendered read.
allowed-tools	Bash
argument-hint	<query> [--full] [--limit N]

rumil-search

Free-text semantic search across the active workspace.

Modes

default (quick) — top-N pages at ABSTRACT detail with similarity scores. Fast and cheap. Use this first. --limit N controls the number of results (default 8).
--full — the multi-tier context builder used inside real rumil calls. Returns a richer rendered block (full pages + summaries within configured char budgets). Reach for this when you want a deep read, not just a pointer list.

setopt no_glob 2>/dev/null; set -f; PYTHONPATH=.claude/lib uv run python -m rumil_skills.search_workspace $ARGUMENTS