菜单
Use when meaningful coordination work is complete and you need to decide what belongs in Qdrant or whether to refresh the shared coordination status marker.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use for Gitea, GitOps, registry, and every non-trivial implementation task that should be delegated to Codex instead of being coded inline.
Use for non-trivial implementation work. Delegate the coding or large-repo analysis to Codex CLI, then record usage before handing back results.
Browse in-cluster Gitea repos, issues, pull requests, commits, chart values, GitOps definitions, and sandbox image sources for read-only design context with the `__REVIEWER_GITEA_USERNAME__` Gitea user shared with auditor.
Review in-cluster Gitea repos and pull requests by reading files, inspecting diffs, checking comments, posting review feedback, and approving with the `__REVIEWER_GITEA_USERNAME__` Gitea user shared with architect; merge only with explicit instruction.
Use this to turn recent Qdrant memories and changed Nextcloud docs into clean Memgraph links, Qdrant graph-link annotations, and an updated grooming checkpoint.
Use when routing work to a standing specialist or reviewing a specialist return.
| name | record-memory-and-coordination-status |
| description | Use when meaningful coordination work is complete and you need to decide what belongs in Qdrant or whether to refresh the shared coordination status marker. |
Use this skill after meaningful coordination work.
Read the local desk and the relevant shared Nextcloud /Desk/ cues first.
Search Qdrant before non-trivial coordination, especially when prior context, preferences, or project history may matter.
Prefer small recency-scoped searches guided by active project slugs, people, services, and open loops.
Store a Qdrant memory when:
When a memory corresponds to a Nextcloud artifact, include nc_refs.
When a memory is project-specific, set project.
Add 1 to 4 short tags for discoverability.
Use expiry for short-lived current-context memories that should stop shaping retrieval after the near term.
Use desk promotion first when the information is only short-term continuity:
CURRENT.md or daily//Desk/current.md or Nextcloud /Desk/daily/After meaningful coordination work:
CURRENT.md and the latest local note when short-term continuity changed/Desk/current.md or Nextcloud /Desk/daily/ when it should survive a restart/Desk/index.md/Projects/ai-homebase/coordination-status.json when shared coordination state changed in a way watchdog should noticeWhen you refresh the shared coordination status marker, write:
{"lastActivity":"ISO-8601","agent":"main","status":"ok"}
/Desk/ as a general archive.