← ClaudeAtlas

whisper-cypherlisted

WhisperGraph Cypher authoring — write read-only queries that pass the server's safety validator and return in milliseconds instead of timing out on billion-node labels. Use when a question has no ready-made WhisperGraph workflow and needs a custom query, when a query was rejected, rewritten, timed out, or returned zero rows unexpectedly, when the user asks about the graph schema, node labels, edge types or edge directions, when an aggregate or comparison across many entities is needed, or when the user asks how to reach the graph over its HTTP API instead of the connector. Covers anchoring, the physical versus query-time edge distinction, the edge directions that silently return nothing, the traps that succeed while matching nothing, and the typed error and self-correction contract. Requires the WhisperGraph MCP connector for the query tool.
whisper-sec/whisper-skills · ★ 1 · AI & Automation · score 63
Install: claude install-skill whisper-sec/whisper-skills
# Writing Cypher for WhisperGraph Reach for Cypher last. The connector ships ready-made workflows that already do the common investigations with an evidence trail attached; hand-rolling a query to rebuild one is slower and more fragile. Call `list_workflows` first, and write Cypher only when nothing there fits. When you do write it, one habit carries almost all of the weight: **anchor the query.** Start from a known value, then traverse outward. The graph is far too large to scan. ## 1. Confirm the schema before you write Do not guess a label, an edge type, or a property name. Guessing is the largest single source of queries that fail — and worse, of queries that succeed and return nothing. - `explain_schema` with **no argument** returns the label catalogue with counts and scale. - `explain_schema` with a **label** returns that entity's properties, its inbound *and* outbound edges with directions, and a runnable sample traversal — everything you need to pivot from it, in one call. Both are cached server-side and cost milliseconds. Call them rather than remembering. Two facts that never change and that most wrong queries violate: - There is **no `DOMAIN` and no `FQDN` label**. Every hostname — apex, subdomain, nameserver, mail server — is `HOSTNAME`. - The indexed string property is **`.name` on every label**. Addresses, network numbers, prefixes, emails: all `.name`. A predicate on any other property is not indexed. ## 2. Anchor Every query must begin from one