Menu
Use this to query or change Memgraph by adding canonical entities and relationships, linking Qdrant memories, and keeping graph structure consistent.
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.
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.
Based on SOC occupation classification
| name | curate-memgraph |
| description | Use this to query or change Memgraph by adding canonical entities and relationships, linking Qdrant memories, and keeping graph structure consistent. |
Memgraph is the structural source of truth.
queries/ files when possible.python3 queries/run_query.py <query.cypher> --params-json '{...}' or --params <file.json> for parameterized query helpers.qdrant/scroll_memories.py or qdrant/get_memory.py to obtain the point ID and normalized packet.MemoryEntry node with slug qdrant:<point_id>, then connect it to the relevant entities with the queries/ helpers.qdrant/set_graph_link.py.Labels:
EntityPersonAgentOrganizationPlaceThingConceptEventWorkProjectServiceCollectionMemoryEntryMemoryEntry nodes should carry slug, qdrant_id, document_sha256, agent, domain, kind, project, created, summary, linked_at, and optional memory_ref when Qdrant metadata already has one.
Relationships:
RELATES_TOHAS_PARTINFLUENCESLOCATED_INCREATED_BYDERIVED_FROMOCCURS_INTAGGED_WITHStandard memory links:
CREATED_BY agentHAS_PART {kind: "memory"} memoryRELATES_TO {kind: "memory-evidence"} selected entitiesDERIVED_FROM {kind: "supersedes"} older memoryTAGGED_WITH durable tag concepts