
bgee-skill
โ Officialโ 4,081by openai ยท part of openai/plugins
Submit compact Bgee SPARQL requests for healthy wild-type expression metadata and ontology-aware lookup patterns. Use when a user wants concise Bgee summaries; save raw results only on request.
๐ฅ๐ฅ๐ฅโ 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/sparql_request.pyfor all Bgee SPARQL work. - Start with small
SELECTorASKqueries and addLIMITearly. - Prefer ontology-aware, healthy wild-type expression questions over broad triple dumps.
- Use
query_pathfor longer SPARQL 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 SPARQL JSON by default.
- Return raw results only if the user explicitly asks for machine-readable output.
- Default to JSON result format unless the user explicitly asks for text output.
Input
- Read one JSON object from stdin.
- Required field:
queryorquery_path - Optional fields:
method,params,response_format,max_items,max_depth,timeout_sec,save_raw,raw_output_path - Common Bgee patterns:
{"query":"ASK {}"}{"query":"SELECT * WHERE { ?s ?p ?o } LIMIT 3","max_items":3}
Output
- Success returns
ok,source, a compactsummary, andraw_output_pathwhensave_raw=true. - Failure returns
ok=falsewitherror.codesuch asinvalid_json,invalid_input,network_error, orinvalid_response.
Execution
echo '{"query":"ASK {}"}' | python scripts/sparql_request.pyReferences
- No additional runtime references are required; keep the import package limited to this file and
scripts/sparql_request.py.
Copy & paste โ that's it
npx skills add openai/plugins --skill "bgee-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.