← Browse

@maxim/ringbinder

A

Use ringbinder to find documents, list documents, answer with citations, and propose file renames.

skillclaude

Install

agr install @maxim/ringbinder --target claude

Writes 8 files into .claude/skills/, pinned to git-fc9e3152.

  • .claude/skills/ringbinder/.gitignore
  • .claude/skills/ringbinder/.gitkeep
  • .claude/skills/ringbinder/LICENSE
  • .claude/skills/ringbinder/README.md
  • .claude/skills/ringbinder/SKILL.md
  • .claude/skills/ringbinder/go.mod
  • .claude/skills/ringbinder/go.sum
  • .claude/skills/ringbinder/main.go

Document


name: ringbinder description: Use ringbinder to find documents, list documents, answer with citations, and propose file renames.

Ringbinder

Use ringbinder help and ringbinder help [command] to learn what's possible.

List recent documents, or by date / time range

By default ringbinder doc list lists 50 recent docs. Read ringbinder doc list --help to learn what else is possible.

Find information in documents

Retrieval loop

  1. Build probe set (5–20 probes):
    • precision probes: --mode and
    • recall probes: --mode or
    • expert probes: --fts '<raw fts5 query>'
    • OCR-noise fallback: repeat key probes with --trigram

Raw FTS safety

  • --fts is good; prefer known-good patterns: terms, quoted phrases, AND/OR/NOT, and parentheses.
  • Don’t guess advanced syntax like NEAR/5 unless you’ve confirmed ringbinder supports it.
  • If a raw FTS query errors, simplify it or split it into multiple --fts probes.
  1. Run each probe:

    • ringbinder find --json --limit 50 --offset 0 <query>
    • or ringbinder find --json --fts '<raw>'
  2. Parse result fields:

    • path, page_index, page_count, snippet, rank, search_source
    • search_source is one of: fts, trigram, path
  3. Merge candidates:

    • dedupe by (path, page_index)
    • prefer fts over trigram over path when evidence quality conflicts
    • keep ~10–30 pages for reading
  4. Read full text before answering:

    • ringbinder read --json --path <path> --page <i> --context 1
    • use --start/--end for wider ranges when needed
  5. Optional metadata for ranking/citations:

    • ringbinder doc get --json --path <path>
  6. Answer with quotes and citations:

    • quote exact supporting lines
    • cite as path (page X) with human 1-based page numbers

Rules

  • Never guess; only claim what you can quote from read output.
  • If evidence is weak, run more probes (OR/raw/trigram) or ask one targeted clarifying question.
  • Prefer reading fewer pages deeply over many snippets shallowly.
  • When using --fts, prefer known-good patterns; if it errors, simplify.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-fc9e315273262026-07-31