Register lasting project documents in a connected LoopX project's document registry, using metadata that conceals private details. This helps future agents locate relevant designs, research notes, procedures, and other project materials.
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.
Review the instructions the agent will receive before you install.
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.
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.loopx-meta just because
the current worker discovered it.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.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.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.
From the target project:
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 and write a project-local todo or blocker instead of registering when:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Guide role-specific work in LoopX auto-research, from defining research conditions and proposing hypotheses to experiments, evaluation, and adoption or retirement decisions. Keep evidence, failed attempts, task handoffs, and stopping conditions tied to each worker’s assigned role.
Guides LoopX benchmark experiments through benchmark-toolkit, covering run management, comparisons under matched conditions, and analysis of agent action histories. It helps explain outcomes and efficiency while tracking source versions, score validity, and evidence boundaries.
Review the exact final set of changes for a LoopX goal, checking reuse, simplification, concrete risks, and project validations. Record and verify a quality receipt, a review record tied to those specific changes.
Reviews authorized LoopX goals, tasks, and deliveries to explain project progress and identify decisions the owner needs to make. It also guides handoffs to suitable agents while preserving the original objective, constraints, and evidence.
Manage a project's stored materials through inventory, migration, archiving, and ranking based on verified source reads. Changes follow owner approval, preserve material references, and include validation records and rollback procedures.
Investigate observed slowdowns or increased CPU, memory allocation, and IO costs in a process you control. Use controlled timing and runtime-specific profiling tools to test a cause, then check performance and behavior after a fix.