abm9111

Chamber — AI skill for Claude Code

AI community

Checks that the numbers, capitalised names, and file names in a claim occur in the indexed note.

How to install Chamber

This entry records only its repository, not the path inside it, so there is no exact command to give. Open abm9111/chamber and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Chamber does

Checks that the numbers, capitalised names, and file names in a claim occur in the indexed note. Local, no model. It does not judge meaning. MIT.

Alternatives in AI

Update Branch Name — by giselles-ai - Updates branch names with proper prefixes and formats, enforcing naming conventions, supporti 502 ★
ZotSeek — AI semantic search for Zotero, with a built-in MCP server for AI agents (Claude Code, Codex) 193 ★
Obsidian AI Tagger Universe — An intelligent Obsidian plugin that leverages AI to automatically analyze note content and suggest relevant ta 102 ★

README

Chamber

The check your AI agent runs on your notes. When Claude Code or any MCP host answers from your vault, `chamber_check` confirms the numbers, capitalised names and file names it quotes are really in the note it cites — and says so when they are not, or when the note changed since it was indexed. [How it works](#use-it-from-an-ai-coding-agent).

You can also ask questions yourself and get answers that cite their sources, plus a daily check that tells you when a source has changed underneath a conclusion you already trusted.

Zero runtime dependencies. Everything is `node:sqlite` and files on your disk. No account, no cloud call unless you point it at one.

Run the check

Checkout and the published package are different runtimes. Config is a third path, for [ingest and chamber_ask](#for-ingest-and-chamber_ask-not-for-the-check).

claude mcp add -s user chamber -- npx -y @bu7umaid/chamber mcp

**Checkout — Node 23.6+.** TypeScript runs directly from the repo, with no build step. `--experimental-strip-types` has been the default since 23.6.0, so the flag is defensive. No config, no model, no network.

git clone https://github.com/abm9111/chamber.git && cd chamber && npm ci && node --experimental-strip-types src/cli.ts try

**Agent.** The command above runs the published bin (`dist/`), not `src/`. If `/mcp` does not list `chamber_check`, the host spawned with a minimal `PATH`. Take the interpreter from `command -v node` in the shell you actually use, and point it at the published bin or at a checkout's `src/mcp_server.ts`. Those are different files.

# published bin: bin/chamber.js loads dist/. This is not src/mcp_server.ts.
claude mcp add -s user chamber -- "$(command -v node)" /path/to/node_modules/@bu7umaid/chamber/bin/chamber.js mcp

# checkout only. src/mcp_server.ts is not in the npm install.
claude mcp add -s user chamber -- "$(command -v node)" --experimental-strip-types /path/to/chamber/src/mcp_server.ts

A number