본문으로 건너뛰기
cccskills
무료GitHub에 공개

loopx-doc-registry

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.

설치 방법 보기

이럴 때 유용합니다

  • Registering design documents and wiki references
  • Keeping research notes and papers discoverable
  • Recording procedures and migration reports
  • Handing project references over to future agents

포함된 파일(3)

  • SKILL.md2.8 KB
  • .loopx-skill-scope7 B
  • agents/openai.yaml259 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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:

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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Define research objectives, metrics, and editable scope
  • Record hypotheses and unsuccessful research directions
  • Run a selected experiment and capture evidence
loopx-project/loopx6.4천2026년 10월 19일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Planning and managing benchmark runs
  • Comparing baselines and treatments under matched conditions
  • Diagnosing outcomes and efficiency from agent action histories
loopx-project/loopx6.4천2026년 10월 19일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing final changes before delivery or merge
  • Checking reuse and opportunities to simplify code
  • Recording validation results and concrete quality risks
loopx-project/loopx6.4천2026년 10월 19일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Summarizing progress across active projects
  • Identifying decisions that need the owner's input
  • Handing work to a suitable agent
loopx-project/loopx6.4천2026년 10월 19일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Inventory stored materials before migration
  • Rank reading candidates using verified sources
  • Archive materials while preserving references
loopx-project/loopx6.4천2026년 10월 19일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Investigate a command that has become slower
  • Locate CPU or memory allocation hotspots
  • Separate transport waits from backend processing costs
loopx-project/loopx6.4천2026년 10월 19일 업데이트

loopx-project의 스킬 모두 보기

이 스킬의 문제 신고