xerj-hub
Skill1 starsChanged 16 days agoMITView on GitHub
Answer a question about public source code, a standard, a regulation or an advisory feed from a pre-indexed hub corpus with one command, xerj "your question". Use it for exact public material you cannot quote from memory. Not for this project's own files.
- Reads credentials
In this repository95 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- agent-architectureSkill
- agentic-evalSkill
- agent-owasp-complianceSkill
- agent-skill-stackSkill
- ai-readySkill
- ai-team-orchestrationSkill
- answer-me-with-htmlSkill
- anti-ui-slopSkill
- archifySkill
- autoresearchSkill
- batch-script-progressSkill
- cli-creatorSkill
- codebase-designSkill
- code-exemplars-blueprint-generatorSkill
- copilot-instructions-blueprint-generatorSkill
- create-agentsmdSkill
- create-architectural-decision-recordSkill
- create-github-action-workflow-specificationSkill
- create-github-issues-feature-from-implementation-planSkill
- create-readmeSkill
- create-specificationSkill
- create-technical-spikeSkill
- create-tldr-pageSkill
- docs-sync-auditSkill
- folder-structure-blueprint-generatorSkill
- gh-fix-ciSkill
- github-actions-hardeningSkill
- github-repo-careSkill
- impeccableSkill
- launchd-automationSkill
- mcp-security-auditSkill
- notion-cliSkill
- opencode-model-routerSkill
- playwright-cliSkill
- python-pypi-package-builderSkill
- refactorSkill
- simple-englishSkill
- swiftui-expert-skillSkill
- technical-documentationSkill
- workshop-driverSkill
- xerjSkill
- anti-ui-slopSkill
- autoresearchSkill
- batch-script-progressSkill
- calling-frontend-from-tauri-rustSkill
- calling-rust-from-tauri-frontendSkill
- cli-creatorSkill
- codebase-designSkill
- code-exemplars-blueprint-generatorSkill
- configuring-tauri-appsSkill
- configuring-tauri-capabilitiesSkill
- configuring-tauri-cspSkill
- configuring-tauri-permissionsSkill
- configuring-tauri-scopesSkill
- copilot-instructions-blueprint-generatorSkill
- create-agentsmdSkill
- create-architectural-decision-recordSkill
- create-github-action-workflow-specificationSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 47
Use --def for a value, a signature or a default.
- Very specific: line 65
If a node answers on --url, $XERJ_URL or localhost:9200 (first one set), XERJ uses it as it is.
- Very specific: line 67
Stop only the node you started: xerj hub stop for XERJ's own (success: stopped the hub node (pid <N>) or no hub node was started by xerj.
- Very specific: line 88
Use the absolute path to the binary: an editor started from a desktop icon does not inherit your shell PATH.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- xerj-init-version: 5 sha256:131aa9224f56d182 -->XERJ hub: ask, do not clone
Pick the source before you search:
- HUB: public material you cannot quote exactly. A library's source at a pinned commit, a standard, a regulation, an advisory feed.
- LOCAL: files only this machine has. This project, private documents, exports.
xerj autoindex <folder> --prefix <name>once, then pass that--prefix <name>toxerj searchandxerj def. Without--prefixthey search the defaultaxprefix. - NEITHER: a fact you can already state exactly. Retrieval on memorised content only adds cost.
Ask the hub
xerj "<question>"One line. No corpus name, no clone, no index. XERJ picks the corpus (your project's dependencies
first), fetches its signed, pre-indexed pack on first use, and answers. Retrieval is lexical, not
semantic: use the words and identifiers the source uses. The bare form needs a space in the
question; for a single word write xerj ask "<word>".
A good answer is three lines, then any warning: lines:
<corpus> pin <date> (<N> days old) <licence> <file>:<line>
<the passage, or the declaration>
answered from: local packpin is the source revision the corpus was built from: check its age when you ask about the current
version. answered from: can also say hosted hub. Tell the user which corpus, pin date and licence
your answer rests on. warning: approach-only licence means read the source, do not copy it.
Exact questions
xerj ask --def <SYMBOL>Use --def for a value, a signature or a default. It prints the definition (file:line, the
declaration, and a value: line for a constant or macro) and no passages. Add --corpus <slug> when
more than one corpus defines the name.
When it does not answer
- Exit 4: more than one corpus fits. The candidates print, one per line. Run again with
--corpus <slug>. - Exit 1,
no hub corpus matches: the hub does not hold it. Say so. Do not answer from memory. - Exit 3: a downloaded pack failed its checksum or signature check and was discarded. Do not use it. Tell the user.
- Exit 5: this build has no hub public key, so no pack can be verified and nothing was downloaded. Tell the user; a retry will not help.
run: xerj hub pull <slug> (<MB> MB): the pack is above the automatic download limit. Run that line, then ask again. Success:pulled <slug> <pin8> <bytes> → <n> indices, <defs> definitions.
The node, and where the question goes
If a node answers on --url, $XERJ_URL or localhost:9200 (first one set), XERJ uses it as it
is. If none does, XERJ starts its own on a free loopback port and records its PID.
Stop only the node you started: xerj hub stop for XERJ's own (success: stopped the hub node
(pid <N>) or no hub node was started by xerj; nothing to stop); for a node you started by hand,
kill only the PID you recorded when you started it. Never pkill xerj or killall xerj: other XERJ nodes may be running
on this machine.
By default, inside a git repository the question is answered on this machine. Outside one it may be
sent to the hosted hub. xerj hub config hosted off forbids that.
MCP
xerj mcp serves three hub tools. They run the same flow as xerj ask:
xerj_hub_ask{question, corpus?, mode?, max_tokens?}: the shell line above, as one call.xerj_hub_def{slug, symbol, k?}:xerj ask --corpus <slug> --def <SYMBOL>.xerj_hub_find{question, k?}: which corpora could answer, best first. No passages.
A hub tool answers only from packs already on this machine; it never downloads one. When a corpus
is not here, the answer is the xerj hub pull <slug> line: run it in a shell, then ask again.
Nor does a hub tool fetch the catalogue: it reads the cached copy. If it says no catalogue is
cached, run xerj hub sync in a shell once, then call the tool again.
Register xerj mcp once, then restart the session. Success: xerj_search is in the tool list.
Use the absolute path to the binary: an editor started from a desktop icon does not inherit your
shell PATH. command -v xerj prints it (PowerShell: (Get-Command xerj).Source).
- Claude Code:
claude mcp add --scope user xerj -- "$(command -v xerj)" mcp(PowerShell or cmd: put the full path ofxerj.exein place of"$(command -v xerj)") .mcp.json(Claude Code, project scope;xerj initwrites it), Cursor, Windsurf, Claude Desktop, Cline: root keymcpServers.{"mcpServers": {"xerj": {"command": "/abs/path/to/xerj", "args": ["mcp"]}}}- VS Code (
.vscode/mcp.json): root keyservers, notmcpServers. A block under the wrong key is silently ignored.{"servers": {"xerj": {"type": "stdio", "command": "/abs/path/to/xerj", "args": ["mcp"]}}} - Codex (
.codex/config.toml, trusted projects only;xerj initwrites it when.codex/exists):[mcp_servers.xerj]withcommand,args = ["mcp"], and[mcp_servers.xerj.env]XERJ_URL.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

