mcpbeat

Ralph Specum Index

tzachbon/ralph-specum-index

This skill should be used only when the user explicitly asks to use `$ralph-specum-index`, or explicitly asks Ralph Specum in Codex to generate or refresh index artifacts.

453 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
432
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/tzachbon/smart-ralph --skill ralph-specum-index

The instruction itself

4 sections, as written by the author

Ralph Specum Index

Use this to generate searchable index specs for an existing codebase.

Contract

  • Index output lives under specs/.index/
  • Use stable Ralph templates for index.md, component specs, and external specs
  • Keep component and external entries deterministic and easy to diff

Action

  • Parse the user scope such as path, types, excludes, quick mode, dry run, or force.
  • Scan the requested code areas for controllers, services, models, helpers, migrations, or comparable project structures.
  • Generate or update:
  • specs/.index/index.md
  • specs/.index/components/*.md
  • specs/.index/external/*.md
  • Keep outputs deterministic so start, research, and triage can reuse them.
  • Include external URLs, MCP endpoints, or installed skills only when the user asked for them or they are clearly relevant.
  • In dry run mode, report what would be created without writing files.

Response Handoff

  • After updating the index, name the files that changed and summarize the index scope briefly.
  • End with exactly one explicit choice prompt:
  • approve current artifact
  • request changes
  • continue to research
  • Treat continue to research as approval of the updated index artifacts.

How to use it

Copy the folder

Take tzachbon/ralph-specum-index from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.