Menu
Use this to answer "what do we know about this?" with a Memgraph-first context map and link relevant Qdrant memories as graph evidence.
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
| name | map-context-and-link-evidence |
| description | Use this to answer "what do we know about this?" with a Memgraph-first context map and link relevant Qdrant memories as graph evidence. |
Use when asked for durable cross-entity context.
## Context Map: <entity or topic>
### Entity
- Slug: <slug>
- Labels: <graph labels>
- Domain: <real | fictional | speculative>
- Status: <active | archived | other>
### Relationships
- <relationship> -> <connected entity> (role: <role>, kind: <kind>)
### Linked Memories
- [<kind>] <memory summary> (agent: <agent>, created: <date>)
### Nextcloud References
- <path> - <brief description>
### Summary
<2-3 sentence synthesis>
MemoryEntry.qdrant_id: run python3 qdrant/get_memory.py "<point-id>"/Desk/ cues and Nextcloud references third for supporting docsMemoryEntry structure with slug qdrant:<point_id>nc_refs when a memory points to a Nextcloud artifactpython3 qdrant/set_graph_link.pyUse this when the task is curation work but not primarily a context-map response:
## Handoff Complete
**Task:** <brief restatement>
**Status:** <complete | partial - needs X | blocked - needs Y>
### Deliverables
- Memgraph: <nodes, edges, schema or query updates>
- Qdrant: <memories stored, linked, groomed>
- Nextcloud: <paths updated, if any>
### For the user
<concise explanation of what durable context was added or clarified>
### Follow-up needed
<which agent should do what next>
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.