بنقرة واحدة
spoke-knowledge-graph
Traverse the SPOKE biomedical knowledge graph to find entity relationships
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Traverse the SPOKE biomedical knowledge graph to find entity relationships
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Built-in self-knowledge about Biorouter. Load this skill whenever the user asks about Biorouter itself: what it is, how it works, who built it, or how to use or configure any of its features (extensions, skills, workflows, scheduler, knowledge bases, models and providers, secrets, CLI, or the desktop app).
Guide for building a Biorouter extension (.brxt file) — covers the required ZIP structure, manifest.json schema, the Python MCP server (pyproject.toml + console-script entry point), cross-platform dependency pitfalls, and optional bundled skills. Load this skill whenever the user wants to build, package, or publish a Biorouter extension.
Guide for authoring a high-quality Biorouter skill — the SKILL.md format and frontmatter, how Biorouter discovers and loads skills, writing a description that triggers reliably, progressive disclosure with supporting files, composing with subagents/workflows/hooks, testing for consistency and robustness, and packaging a skill as a zip. Load this skill whenever the user wants to create, write, improve, test, or publish a Biorouter (or Claude) skill.
Explore the CDW clinical schema, tables, and column relationships
Systematically build and refine patient cohorts from CDW clinical data
Query the OMOP CDM to identify patient phenotypes and clinical concepts
| name | spoke-knowledge-graph |
| description | Traverse the SPOKE biomedical knowledge graph to find entity relationships |
Use this skill when the user wants to explore relationships between biomedical entities (diseases, genes, compounds, pathways, side effects) in the SPOKE graph.
get_spoke_schema to understand available node and edge typesquery_spoke to traverse the relevant subgraph