query-intelligo

Query Intelligo

This skill wraps the queryIntelligo MCP tool exposed by the Intelligo MCP server. Use it whenever the user asks for Intelligo data — searches, projects, subjects, findings, scores, viewer/org context.

Workflow

1. Discover schema first. If you do not already know the relevant GraphQL types, call the getSchema tool (or invoke the get-schema skill) for the specific type you need. Avoid pulling the full SDL unless you genuinely need it — it's ~12k tokens.
2. Compose a minimal GraphQL query. Only request fields the user actually asked about. Prefer narrow selection sets to keep response sizes small.
3. Use known fixture IDs. When the user is exploring or asks a generic question, prefer these seeded demo IDs over inventing new ones:
   • Searches: search_alice_001, search_bob_pep_002, search_acme_clean_003, search_refresh_v2
   • Projects: proj_demo_lp
   • Subject canonical IDs: subj_alice, subj_bob, subj_acme
4. Call queryIntelligo with the query string and (optionally) a variables map.
5. Render results in plain language. Translate the JSON back into a human answer. Quote IDs and field names exactly when the user may want to follow up.

Common entry points on Query

• me: Viewer — current user / org context.
• search(id: ID!): Search — one search by id.
• searches(filter, first, offset): [Search!]! — list searches.
• searchesForSubject(canonicalId: ID!): [Search!]! — all searches for one subject across time.
• project(id: ID!): Project — one project (deal/case) by id.
• projects(first, offset): [Project!]! — list projects.

Limits

• Query string: ≤ 8192 bytes.
• Variables JSON: ≤ 4096 bytes.
• Response: ≤ 65536 bytes (server truncates).

If you hit a limit, narrow the query (smaller selection set, smaller first, paginate via offset).

Examples

User: "Show me the latest search for Alice."

query {
  searchesForSubject(canonicalId: "subj_alice") {
    id
    createdAt
    status
    findings { id severity summary }
  }
}

User: "Who am I logged in as?"

query { me { id email org { id name } } }

User: "List the first 5 projects."

query { projects(first: 5) { id name status } }

When NOT to use this skill

• The user asks about Claude itself, the plugin, or troubleshooting — use the onboarding skill instead.
• The user asks "what types/fields exist?" without wanting actual data — use the get-schema skill instead.