---
name: prism-knowledge-graph-mapper
description: "Use when an AI client needs to inspect or create explicit relationships among Prism sources, claims, companies, drafts, artifacts, and other research nodes."
---

# Knowledge graph mapper

Connect sources, claims, and outputs with explicit, evidence-backed relationships.

## Before you start

Copy this guidance into ChatGPT, Claude, Codex, Grok, or another client that accepts custom instructions. It changes the client's instructions only; it does not grant Prism access. Direct MCP calls require the client's current MCP support, a configured connection, and separately authorized scopes.

Scopes this workflow may need:

- `knowledge:read`
- `graph:write`

The installed skill does not grant these permissions. Use only the scopes and Projects authorized on the current Prism MCP connection.

## Workflow

1. Inspect neighboring evidence and existing relationships for the source and target nodes.
2. Verify that both nodes are the precise objects intended by the user.
3. Choose the most specific true relationship: supports, contradicts, references, cites, derived_from, updates, summarizes, mentions, duplicates, or related_to.
4. Use the batch create tool when one output connects to several nodes, otherwise create one relationship.
5. Show cleanup operations before updating, archiving, deleting, or bulk-cleaning edges.

## Tool routing

- `get_evidence_graph_neighbors`, `list_library_relationships`: Inspect graph context and avoid duplicate edges.
- `create_library_relationships`, `create_library_relationship`: Create a bounded batch or one precise edge.
- `update_library_relationship`, `archive_library_relationship`, `delete_library_relationship`, `bulk_clean_library_relationships`: Apply explicit user-reviewed cleanup operations only.

## Expected result

- Edges use the most specific truthful relationship type and precise Prism node ids.
- New relationships include concise notes that explain why the connection matters.
- Existing edges are reused or updated instead of duplicated.

## Boundaries

- A skill does not grant Prism access. The connection must separately authorize every required scope and Project.
- Call only tools verified callable by the current AI host. Use discover_prism_actions for granular actions. If a default workflow tool is missing, follow the capability-handshake recovery guidance instead of inventing a substitute tool.
- Read before writing. Mutate Prism only when the user asked for a durable change and the connected tool exposes that exact action.
- Keep retrieved evidence separate from analysis. Cite Prism source ids, titles, snippets, locations, and chunk ids when available.
- Do not infer broad cleanup authority from a vague request.
- If the exact relationship is uncertain, use related_to with a concise note or return a proposal without writing.
- Project Canvas edges are visual layout, not system Knowledge Graph relationships.