Menu
Use when operating Nextcloud as the shared coordination layer for desk state, calendars, todos, tables, sharing, or coordination status.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | coordinate-in-nextcloud |
| description | Use when operating Nextcloud as the shared coordination layer for desk state, calendars, todos, tables, sharing, or coordination status. |
Main owns shared coordination state, not specialist project authorship.
Use Nextcloud for:
/Desk/ shared continuity and live indexing/Projects/ sharing and top-level coordination/Projects/ai-homebase/coordination-status.jsonopenclaw account before something is intentionally shared with the user's own accountDo not use Nextcloud to:
/Desk/, Nextcloud /Desk/current.md, Nextcloud /Desk/index.md, and Nextcloud /Desk/daily/README.md if shared continuity is needed and they do not exist yet./Desk/current.md, Nextcloud /Desk/index.md, and the latest shared daily note when they exist./Projects/<slug>/ already exists./Projects/<slug>/, relevant calendars, task lists, tables, and user-shared folders in Nextcloud /Desk/index.md./Desk/index.md entry should include type, stable id or path, purpose, steward, project or domain, and a read trigger./Projects/ai-homebase/coordination-status.json.project, tags, and nc_refs, plus expiry when the memory is intentionally short-lived.Do not create a standing heartbeat for a frontier agent just to poll for conditions.
If a recurring need is a simple timed check or reminder, prefer watchdog or a conservative cron.
If it is a recurring multi-step workflow with stable rules, route toward architect and manage-worker-lifecycle.
If a higher-cost agent needs recurring work, prefer sparse cron such as nightly or weekly rather than a 30-minute heartbeat.
Do not let Nextcloud /Desk/ become a generic archive; move stable material into Qdrant, Memgraph, or Nextcloud /Projects/.
/Desk/current.md/Desk/index.md/Desk/daily//Projects/<slug>/status.md/Projects/<slug>/outputs//Projects/ai-homebase/coordination-status.json