
civic-skill
โ Officialโ 4,081by openai ยท part of openai/plugins
Submit compact CIViC GraphQL requests for cancer variant interpretation schema inspection and targeted evidence retrieval. Use when a user wants concise CIViC summaries
๐ฅ๐ฅ๐ฅโ VerifiedFreeQuick setup
๐งฉ One of 7 skills in the openai/plugins package โ works on its own, and pairs well with its siblings.
This is the playbook your agent receives when the skill activates โ you don't need to read it to use the skill, but it's here to audit before installing.
Operating rules
- Use
scripts/civic_graphql.pyfor all CIViC GraphQL work. - Keep selection sets narrow and start with schema or targeted entity queries.
- Use
query_pathfor longer GraphQL documents instead of pasting large inline queries. - Re-run requests in long conversations instead of relying on older tool output.
Execution behavior
- Return concise markdown summaries from the script JSON by default.
- Return raw JSON only if the user explicitly asks for machine-readable output.
- Prefer sanity, schema, and targeted evidence queries over broad graph dumps.
Input
- Read one JSON object from stdin.
- Required field:
queryorquery_path - Optional fields:
variables,max_items,max_depth,timeout_sec,save_raw,raw_output_path - Common CIViC patterns:
{"query":"query { __typename }"}{"query":"query { __schema { queryType { fields { name } } } }","max_items":20}
Output
- Success returns
ok,source,top_keys, a compactsummary, andraw_output_pathwhensave_raw=true. - Failure returns
ok=falsewitherror.codesuch asinvalid_json,invalid_input,network_error,invalid_response, orgraphql_error.
Execution
echo '{"query":"query { __typename }"}' | python scripts/civic_graphql.pyReferences
- No additional runtime references are required; keep the import package limited to this file and
scripts/civic_graphql.py.
Copy & paste โ that's it
npx skills add openai/plugins --skill "civic-skill" --full-depthRun this in your project โ your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.