Help us improve
Share bugs, ideas, or general feedback.
From 11mirror
Graph reasoning decision protocol for 11Mirror agents. Teaches when to use knowledge graph queries (via Cognee/TrustGraph) vs brain search (via fbrain). Route relationship questions to the graph engine; route content retrieval to brain search first.
npx claudepluginhub postergully/11mirror-plugin --plugin 11mirrorHow this skill is triggered — by the user, by Claude, or both
Slash command
/11mirror:11mirror-graph-reasoningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When an agent needs to understand RELATIONSHIPS between entities (people, vendors, cost centers, documents), route to the graph engine. For direct content retrieval, use brain search first.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.
Share bugs, ideas, or general feedback.
When an agent needs to understand RELATIONSHIPS between entities (people, vendors, cost centers, documents), route to the graph engine. For direct content retrieval, use brain search first.
First: ALWAYS try fbrain search (fast, <1s, hybrid vector+keyword)
Then: If the question is about CONNECTIONS, use graph_query (5-20s, uses LLM)
Never skip brain search. Even for graph questions, brain search gives context.
| Tool | When | Latency | Cost |
|---|---|---|---|
search | Any content question | <1s | Free (no LLM) |
query | Semantic + keyword hybrid | <1s | Free (no LLM) |
graph_query | Entity relationships, multi-hop | 5-20s | ~$0.005 (LLM synthesis) |
entity_search | Find specific entities in graph | 3-10s | ~$0.003 |
get_page | Read full document | <1s | Free |
traverse_graph | Walk typed edges from a node | <1s | Free (no LLM) |
get_backlinks | Find pages linking to a slug | <1s | Free |
traverse_graph over graph_query when you already know the starting entity slugget_backlinks to discover reverse relationships cheaply before escalating to graph_querysearch("Project Aurora")search("Q3 board deck")search("Alice hiring")search("Alice") then graph_querysearch("Acme Corp") then graph_querysearch("budget") then graph_queryentity_search("CC-4401") then graph_querytraverse_graph(slug="people/alice", type="works_with")traverse_graph(slug="funds/fund-a", type="invested_in")This skill guarantees: