Agent skill

LoopX Doc Registry

by loopx-project in loopx-project/loopx

Registers durable project materials such as design docs, SOPs and research notes in a LoopX project's own registry so future agents can find them without raw URLs or private content.

Apache-2.0Auto-check passedAgent Workflows

Install LoopX Doc Registry

skills CLI
$ npx skills add loopx-project/loopx --skill loopx-doc-registry -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install loopx-project/loopx loopx-doc-registry --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/loopx-project/loopx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/loopx-doc-registry .claude/skills/loopx-doc-registry && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
loopx-doc-registry
GitHub stars
6.2k
Token cost
~707 tokens
SKILL.md length
256 words
Files
3
Skills in repo
12
Repo updated
First seen
Licence
Apache-2.0

At a glance

Registers durable project materials such as design docs, SOPs and research notes in a LoopX project's own registry so future agents can find them without raw URLs or private content.

  • Works in 5 steps: Resolve the target project and stable… → If the material belongs to that project,… → If the project has a tracked… → …
  • Recording a design doc, SOP or research note so future agents can find it
  • SKILL.md covers Default Route, Command Shape and Stop Conditions
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

For a project connected to LoopX, the skill makes material findable by future agents from the project's authority surface rather than from chat or personal memory. It resolves the target project and its goal id from the repo or the project you named, then registers the material in that project's own registry: a tracked docs/meta/DOC_REGISTRY.yaml if one exists, otherwise .loopx/registry.json. It does not file things under loopx-meta just because a worker happened to find them.

Registration uses the loopx register-authority-source command with a redacted source contract, since raw URLs, document ids, private local paths, comments and source bodies must stay out of public files. A dry run is advised when the classification is unclear, and status or state is refreshed afterward so review packets, maps, dashboards and heartbeat workers can see the entry. The agent stops and writes a project-local todo or blocker if the project or goal is ambiguous, if the material cannot be described as public-safe metadata, if registering would need private reading nobody asked for, or if the material conflicts with newer owner-approved material.

When your agent uses it

  • Recording a design doc, SOP or research note so future agents can find it
  • Registering an external material source with a LoopX project
  • Deciding which project's registry owns a document
  • Checking that a registration is public-safe before it is written

Example prompts

  • “Register the migration report for this project in its doc registry.”
  • “Index our onboarding SOP so future agents can find it, and do a dry run first.”
  • “Remember this benchmark paper as a project material, but keep the URL out of public files.”

Requirements

  • A project connected to LoopX, with the loopx CLI
  • A .loopx/registry.json or docs/meta/DOC_REGISTRY.yaml file

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Resolve the target project and stable goal_id from the current repo or the
  2. If the material belongs to that project, register it in that project's own
  3. If the project has a tracked docs/meta/DOC_REGISTRY.yaml or equivalent,
  4. Run loopx register-authority-source with a redacted source contract.
  5. Refresh status or state so review packets, read-only maps, dashboards, and

What it can do on your machine

Read from SKILL.md and the folder at commit 8205c8b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

LoopX Doc Registry loads about 707 tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 256 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
When it runs · the whole SKILL.md, loaded when a task matches
~707

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from loopx-project/loopx at commit 8205c8b, republished under its Apache-2.0 licence (© loopx-project). 256 words, ~707 tokens.

Download SKILL.mdSave it as .claude/skills/loopx-doc-registry/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
loopx-doc-registry
description
Use when a connected LoopX project is asked to read, remember, record, index, register, or use a durable project material such as a Lark/wiki/design doc, research note, SOP, owner packet, migration report, benchmark paper, or external material source. Use even when the user does not mention LoopX or doc registry.

LoopX Doc Registry

Use this skill for durable project materials. The goal is to make future agents find the material from the project authority surface, not only from chat or personal memory.

Default Route

  1. Resolve the target project and stable goal_id from the current repo or the user's named project. Prefer .loopx/registry.json and .codex/goals/<goal-id>/ACTIVE_GOAL_STATE.md.
  2. If the material belongs to that project, register it in that project's own authority surface. Do not register it into loopx-meta just because the current worker discovered it.
  3. If the project has a tracked docs/meta/DOC_REGISTRY.yaml or equivalent, update that first. If it does not, use .loopx/registry.json as the project-local doc registry through authority_registry.topic_authority and authority_registry.project_materials.
  4. Run loopx register-authority-source with a redacted source contract. Raw URLs, doc ids, local private paths, comments, and source bodies must not be stored in public files.
  5. Refresh status or state so review packets, read-only maps, dashboards, and heartbeat workers can find the material.

Memory extensions are allowed only as secondary personal reminders. They are not a substitute for project-local authority registration when the project is connected to LoopX.

Command Shape

From the target project:

bash
loopx --registry .loopx/registry.json register-authority-source \
  --goal-id <goal-id> \
  --source-id <stable-source-id> \
  --source-ref "<raw-url-or-private-path-to-hash>" \
  --source-kind <doc|lark_doc|wiki|paper|owner_packet|migration_report> \
  --role <public-safe-role> \
  --freshness <current|historical|unknown> \
  --owner-status <public-safe-owner-status> \
  --gate-status <readable|needs_access|owner_review_pending> \
  --boundary private_redacted \
  --revision "<public-safe-revision-label>" \
  --conflict-rule "<public-safe-conflict-rule>" \
  --topic <topic-key>

Use --dry-run first when the source classification or target project is not obvious.

Stop Conditions

Stop and write a project-local todo or blocker instead of registering when:

  • the target project or goal is ambiguous;
  • the material cannot be represented as public-safe metadata;
  • registering would require reading private content that was not requested or permitted;
  • the source conflicts with a newer owner-approved material and the conflict rule is unclear.

© loopx-project, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in skills/loopx-doc-registry of loopx-project/loopx.

  • SKILL.md
  • .loopx-skill-scope
  • agents/openai.yaml

Open the folder on GitHubat commit 8205c8b

Compare with similar skills

LoopX Doc Registry next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

LoopX Doc Registry compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
LoopX Doc Registry this skillloopx-project/loopx6.2k—~707Automated safety check: PassApache-2.0
MemPalace Memory SearchMemPalace/mempalace59k—~1.4kAutomated safety check: PassMIT
Remember Project Knowledgezereight/gitlab-mcp2k1 repos~846Automated safety check: PassMIT
Context Mode Searchmksglu/context-mode26k—~250Automated safety check: PassCustom licence
Claude-Mem Knowledge Agentthedotmack/claude-mem97k—~617Automated safety check: PassApache-2.0
Autocontext Knowledge Readergreyhaven-ai/autocontext1.3k—~934Automated safety check: PassApache-2.0

Similar skills

  • MemPalace Memory Search

    MemPalace/mempalace

    Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.

    59k GitHub stars~1.4k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Remember Project Knowledge

    zereight/gitlab-mcp

    Sorts what you learned in a session into the right memory surface, filtering out ephemeral notes and duplicates before anything is stored.

    2k GitHub starsUsed in 1 repo~846 tokens
    Agent WorkflowsAuto-check passed
  • Context Mode Search

    mksglu/context-mode

    Search context-mode's persistent FTS5 knowledge base for previously indexed local project content, documentation, or session memory. Trigger…

    26k GitHub stars~250 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Claude-Mem Knowledge Agent

    thedotmack/claude-mem

    Builds focused knowledge corpora from claude-mem observations, loads them into an AI session and answers questions about past work.

    97k GitHub stars~617 tokensUpdated yesterday
    Knowledge ManagementAuto-check passed
  • Autocontext Knowledge Reader

    greyhaven-ai/autocontext

    Reads and moves the playbooks and lessons that Autocontext has already learned, using the autoctx CLI and plain files on disk.

    1.3k GitHub stars~934 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • LLM Wiki

    Yeachan-Heo/oh-my-claudecode

    Keeps a persistent markdown wiki of project and session knowledge that the agent can ingest into, query, lint and read across sessions.

    40k GitHub stars~721 tokensUpdated today
    Knowledge ManagementAuto-check passed

More from loopx-project/loopx

All 12 skills in this repo
  • LoopX PR Program Manager

    loopx-project/loopx

    Tracks a group of pull or merge requests across repositories as durable LoopX state: inventory, reconcile changes, keep priorities and a roadmap, and monitor over time.

    6.2k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • LoopX Self Repair

    loopx-project/loopx

    Diagnoses surprising LoopX behavior, such as stale recommendations or tiny progress, assigns it to the responsible layer and repairs it at the lowest durable level.

    6.2k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • LoopX Auto-Research Worker

    loopx-project/loopx

    Role playbook for a LoopX worker running an auto-research lane, with execution checklists, artifact contracts and stop conditions.

    6.2k GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • LoopX Benchmark Operator

    loopx-project/loopx

    Operates or analyzes a LoopX-managed benchmark experiment: launching runs, maintaining the experiment board, qualifying integrity, and writing case insights.

    6.2k GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • LoopX PR Review

    loopx-project/loopx

    Runs an evidence-backed pull request review through the loopx CLI and posts bilingual reviews: a full Chinese review plus one concise English verdict.

    6.2k GitHub stars~3.3k tokensUpdated today
    Auto-check passed
  • LoopX Project Lifecycle

    loopx-project/loopx

    Connects and configures LoopX projects and Goals, repairs project-local state and stale status, syncs registry entries and diagnoses CLI routing.

    6.2k GitHub stars~14k tokensUpdated today
    Auto-check passed

Questions about LoopX Doc Registry

What does LoopX Doc Registry do?

Registers durable project materials such as design docs, SOPs and research notes in a LoopX project's own registry so future agents can find them without raw URLs or private content. For a project connected to LoopX, the skill makes material findable by future agents from the project's authority surface rather than from chat or personal memory.json.

When should I use LoopX Doc Registry?

LoopX Doc Registry fits situations like: recording a design doc, SOP or research note so future agents can find it; registering an external material source with a LoopX project; deciding which project's registry owns a document; checking that a registration is public-safe before it is written.

How do I install LoopX Doc Registry in Claude Code?

Run `npx skills add loopx-project/loopx --skill loopx-doc-registry -a claude-code`. Or copy the skill folder (skills/loopx-doc-registry in loopx-project/loopx) into .claude/skills/loopx-doc-registry in your project. Claude Code loads it when a task matches its description.

How do I install LoopX Doc Registry in Codex?

Run `npx skills add loopx-project/loopx --skill loopx-doc-registry -a codex`. Or copy the skill folder (skills/loopx-doc-registry in loopx-project/loopx) into .agents/skills/loopx-doc-registry in your project. Codex loads it when a task matches its description.

Can I use LoopX Doc Registry in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add loopx-project/loopx --skill loopx-doc-registry -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/loopx-doc-registry, .gemini/skills/loopx-doc-registry, .github/skills/loopx-doc-registry and .opencode/skills/loopx-doc-registry in your project.

What does LoopX Doc Registry need to run?

SKILL.md names no scripts, command-line tools or credentials: LoopX Doc Registry is instructions for the agent only. Our summary lists: A project connected to LoopX, with the loopx CLI; A .loopx/registry.json or docs/meta/DOC_REGISTRY.yaml file.

Does LoopX Doc Registry access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is LoopX Doc Registry safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does LoopX Doc Registry use?

LoopX Doc Registry is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does LoopX Doc Registry use?

About 707 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to LoopX Doc Registry?

Skills that share tags, products or a category with LoopX Doc Registry: MemPalace Memory Search (MemPalace/mempalace, 59k stars), Remember Project Knowledge (zereight/gitlab-mcp, 2k stars), Context Mode Search (mksglu/context-mode, 26k stars) and Claude-Mem Knowledge Agent (thedotmack/claude-mem, 97k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains LoopX Doc Registry?

loopx-project (a GitHub organization) maintains it in loopx-project/loopx, which has 6,167 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.

Source: loopx-project/loopx on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.