xiaohongshu
xiaohongshu
initiate-new-disorder-creation
Skill for initiating new disorder YAML files in the dismech knowledge base. Use this skill when the user asks to create a new disorder entry. Also useful for enhancing existing entries.
Full skill instructions
Guide the creation of new disorder YAML files in the dismech knowledge base. This skill emphasizes a research-first approach to ensure scientific accuracy and prevent AI hallucinations by requiring deep research queries before file creation.
kb/disorders/This skill can also be consulted for ongoing curation of existing disorders.
Choose the clinically preferred name for the disorder, use title case (e.g. Foo Bar Syndrome).
For file names, spaces will. be replaced by underscores, and characters such as apostrophes removed.
ls kb/disorders/*yaml
If it exists, edit the existing file instead of creating a new one.
Create an initial yaml file using the underscore form of the disease, e.g.
kb/disorders/Foo_Bar.yaml:
name: Foo Bar
category: Complex
disease_term:
term:
id: MONDO:nnnnnnn
label: foo bar ## mondo name will follow OBO case conventions
parents:
<yaml list of strings>
has_subtypes:
<optional yaml list of Subtype objects>
pathophysiology:
<yaml list of Pathophysiology objects>
phenotypes:
<yaml list of Phenotype objects>
biochemical:
<optional yaml list of Biochemical objects>
genetic:
<optional yaml list of Genetic objects>
environmental:
<optional yaml list of Environmental objects>
treatments:
<optional yaml list of Treatment objects>
datasets:
The objects must follow the LinkML schema in src/dismech/schema.
It can be validated with just validate kb/disorders/Foo_Bar.yaml
This first pass should use textbook knowledge about the disease: you will later refine this.
Execute at least one deep research query. Always do this via the just command, do
not perform your own deep research.
Depending on user preference, use one or more of the following commands
just research-disorder perplexity DISORDER_NAMEjust research-disorder falcon DISORDER_NAMEjust research-disorder openai DISORDER_NAMEjust research-disorder cyberian DISORDER_NAMEUse the filesystem-friendly name here.
On completion (may be several minutes, be patient), this will create a file here:
./research/DISORDER_NAME.md
You MUST read this before progressing.
Use the results of deep research to enhance the yaml file, providing evidence for as many assertions as possible.
Find the pubmed IDs or DOIs for the papers in the deep research and retrieve these:
just fetch-reference PMID:nnnnnnnjust fetch-reference DOI:...You can also find additional references relevant to individual assertions, on top of what is in the deep research.
Then use this to provide snippets/excerpts and explanations for assertions. For example, for a phenotype assertion:
phenotypes:
- name: <Phenotype Name>
description: <Description from research>
evidence:
- reference: PMID:XXXXXXXX
supports: <SUPPORT | REFUTE | PARTIAL>
snippet: "<Exact quote from abstract>"
explanation: "<Why this supports the phenotype>"
The same generic evidence list schema is used for most types.
Add term objects using ontology term IDs; for example, for a pathophsyiology object, it might look like this:
pathophysiology:
- name: <Mechanism Name>
description: >
<Detailed mechanism description from research>
cell_types:
- preferred_term: <Cell Type>
term:
id: CL:XXXXXXX
label: <exact CL label>
biological_processes:
- preferred_term: <Process Name>
term:
id: GO:XXXXXXX
label: <exact GO label>
Consult the LinkML schema to see what terms are appropriate for any given object type. These will be validated.
You can use OAK commands to find relevant terms.
General term search (use mondo for diseases)
uv run runoak -i sqlite:obo:mondo info "l~<disease name>"
starts-with queries (use hp for phenotypes)
uv run runoak -i sqlite:obo:hp info "l^<phenotype>"
exact:
uv run runoak -i sqlite:obo:cl info CL:nnnnnnn
relationships (up and down):
uv run runoak -i sqlite:obo:go relationships --direction both GO:nnnnnnn
Strict validation check (adherence to schema, term and reference checks):
just validate kb/disorders/<Disease_Name>.yaml
Compliance report (completeness, term and evidence coverage):
just compliance kb/disorders/<Disease_Name>.yaml
Convert the disease name to a file-safe format:
Examples:
Type_2_Diabetes.yamlAlzheimers_Disease.yamlCOVID-19.yamlA new disorder file MUST include at minimum:
| Field | Source | Notes |
|---|---|---|
name | - | Human-readable disease name |
category | Research | Mendelian, Complex, Infectious, etc. |
disease_term | OAK lookup | MONDO term binding |
phenotypes (1+) | Research | At least one phenotype with HPO term |
pathophysiology (1+) | Research | At least one mechanism |
evidence (1+) | Research | At least one PMID reference |
All evidence items MUST:
NEVER fabricate PMIDs or paraphrase snippets.
info "l~<term>"just validate-references <file>--fix-threshold 0.80 to auto-repair minor mismatchesname, category, and at least one pathophysiology entryUse all loaded skills, including:
Before finalizing a new disorder file, verify:
just validate passesjust validate-terms-file passesjust validate-references passesxiaohongshu
technical spec
product ux expert
database patterns
Conduct multi-agent task orchestration and workflow coordination.
Initialize project with Conductor artifacts (product definition,
Expert in web animations, transitions, and motion design using Framer Motion and CSS
Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...
PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.
Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...
Display project status, active tracks, and next actions
Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.
Generate, edit, and beat-sync AI video with leading models in one workspace.
The world's fastest calendar for remote work
Transform Your Design with AI Designer by ImgCreator.ai
Revolutionizing Video Production with AI-Powered Creativity
Extend an image past the frame and let AI fill the new aspect ratio.
Discover your celebrity doppelgänger with StarByFace!
ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.
Opus.ai: Revolutionize Your Web Experience