tooluniverse-clinical-guidelines
Search and retrieve clinical practice guidelines from 12+ authoritative sources — NICE, WHO, NCCN, AHA, ADA, SIGN, USPSTF, IDSA, NIH consensus, ESMO/ESC/EASL European societies, and US specialty associations. Use for evidence-graded treatment recommendations, dosing protocols, screening guidance, and authoritative-source-prioritized clinical guidance (NICE/WHO ranked above society guidelines).
What this skill does
# Clinical Guidelines Search & Retrieval ## Guideline Hierarchy Not all guidelines carry equal weight. Evaluate sources in this order: 1. **NICE and WHO** — Evidence-graded, regularly updated, rigorous systematic review process. NICE guidelines include explicit recommendation strength (e.g., "offer" vs "consider"). 2. **Society guidelines (AHA, ADA, NCCN, SIGN)** — Expert-consensus panels within a specialty. May lag behind the latest evidence by 1-3 years. Strong within their domain but narrower scope. 3. **Aggregator databases (GIN, TRIP, OpenAlex)** — Index guidelines from multiple societies. Good for breadth and discovery, but you must verify the original source. 4. **Literature databases (PubMed, EuropePMC)** — Return guideline-related publications, not curated guideline text. Useful as a fallback, not a primary source. **Always check publication date.** A 2015 guideline may be superseded by a 2024 update. When presenting results, include the year prominently and note if newer guidance may exist. --- ## COMPUTE, DON'T DESCRIBE When analysis requires computation (statistics, data processing, scoring, enrichment), write and run Python code via Bash. Don't describe what you would do — execute it and report actual results. Use ToolUniverse tools to retrieve data, then Python (pandas, scipy, statsmodels, matplotlib) to analyze it. ## Search Strategy ### Step 1: Start Narrow, Then Broaden 1. Search the **condition name + "guideline"** in NICE, TRIP, and GIN simultaneously (parallel calls). 2. If the question targets a specialty, add the society tool: AHA for cardiology, ADA for diabetes, NCCN for oncology, CPIC for pharmacogenomics. 3. If initial searches return nothing, broaden to the disease category (e.g., "heart failure" instead of "HFpEF with SGLT2 inhibitors"). 4. If society-specific tools fail, fall back to PubMed/EuropePMC with `[condition] guideline [year]`. ### Step 2: Search at Least 3 Sources Always query a minimum of 3 databases to catch guidelines that one source may miss. Prioritize: **NICE > GIN > TRIP > Society-specific > Literature databases**. ### Step 3: Retrieve Full Text When Available After identifying relevant guidelines from search results, use full-text tools to get recommendation details before synthesizing. --- ## Diagnostic Test Selection Reasoning When a clinical question asks "which test should be ordered?" or "what is the most appropriate next diagnostic step?", apply this reasoning framework BEFORE searching guidelines. ### Step 1: What Is the Clinical Question Actually Asking? Diagnostic tests serve different purposes. Identify which one the question demands: - **Screening**: Detect disease in an asymptomatic population. Prioritize SENSITIVITY (minimize false negatives). Example: ANA for SLE screening. - **Confirmation**: Confirm a suspected diagnosis. Prioritize SPECIFICITY (minimize false positives). Example: anti-dsDNA or anti-Smith for SLE confirmation. - **Differentiation**: Distinguish between two diagnoses that look similar. Choose the test that is POSITIVE in one and NEGATIVE in the other. Example: ASO titers to distinguish PSGN from SLE nephritis (both have low complement and hematuria, but only PSGN has elevated ASO). - **Staging/Prognosis**: Determine disease severity after diagnosis is established. Example: renal biopsy ISN/RPS class for lupus nephritis. - **Monitoring**: Track response to treatment. Example: anti-dsDNA titers and complement levels in SLE. ### Step 2: Match the Test to the Diagnostic Gap Ask: "What piece of information am I MISSING that would change management?" ### Step 3: Sensitivity vs Specificity Decision Matrix | Scenario | Prioritize | Reasoning | |----------|-----------|-----------| | Ruling OUT a dangerous condition | High sensitivity | A negative result reliably excludes the disease | | Confirming before invasive treatment | High specificity | A positive result reliably confirms the disease | | Differentiating two similar conditions | Test unique to one | Choose marker present in condition A but absent in condition B | | Emergency with life-threatening DDx | Fastest available test | Speed trumps perfect accuracy in acute settings | ### Step 4: Common Test Selection Pitfalls 1. **Ordering a test that is positive in BOTH conditions on the differential** — C3/C4 is low in both SLE and PSGN; it does not differentiate. Always ask: "Would this test result change my differential?" 2. **Ordering a screening test when a confirmatory test is needed** — ANA is sensitive but not specific for SLE. If you already suspect SLE, order anti-dsDNA or anti-Smith (specific). 3. **Skipping the simple test for the exotic one** — ASO titers are cheap and fast. Do not jump to renal biopsy before checking whether streptococcal infection explains the presentation. 4. **Forgetting temporal context** — PSGN complement normalizes in 6-8 weeks; SLE complement stays persistently low. A single complement level is less useful than a trend. 5. **Ignoring pre-test probability** — A test with 95% specificity still has a 50% false-positive rate if the pre-test probability is only 5%. Consider the clinical picture first. --- ## Lab Test Interpretation Strategy - Always consider **pre-test probability** before interpreting any result. A positive test in a low-prevalence population has a high false-positive rate regardless of test accuracy. - **SnNOut**: A highly **Se**nsitive test, when **N**egative, rules **Out** the disease. Use sensitive tests for screening. - **SpPIn**: A highly **Sp**ecific test, when **P**ositive, rules **In** the disease. Use specific tests for confirmation. - For **conflicting results** (e.g., one test positive, another negative): repeat the discordant test, order a different confirmatory test, or re-evaluate the clinical picture and pre-test probability. - **Likelihood ratios** trump sensitivity/specificity alone. LR+ >10 or LR- <0.1 meaningfully shift post-test probability. --- ## Surgical Decision Making - **Indications**: Determine whether surgery is necessary. Absolute indications (e.g., perforated viscus, acute limb ischemia) require immediate action; relative indications (e.g., symptomatic gallstones) allow shared decision-making. - **Timing**: Emergent (within minutes-hours, life/limb threat), urgent (within 24-72 hours, deterioration risk), elective (scheduled, optimized pre-operatively). - **Approach**: Choose the least invasive option that achieves the therapeutic goal. Laparoscopic before open, endovascular before surgical, unless contraindicated by anatomy or urgency. --- ## Applying Guidelines to Patients Guidelines give **population-level recommendations**. When presenting findings: 1. **Cite the source explicitly** — "Per the 2024 ADA Standards of Care, Section 9..." not "guidelines recommend..." 2. **Note patient-specific modifiers** — Comorbidities, drug interactions, renal/hepatic function, age, pregnancy, and patient preferences may all change the recommendation. 3. **Flag when evidence is weak** — Grade D / expert consensus recommendations should be presented differently from Grade A / high-confidence ones. 4. **Identify conflicts between guidelines** — When NICE and ADA disagree, present both positions and note the discrepancy. 5. **State limitations** — If the patient's scenario falls outside the guideline's studied population, say so explicitly. --- ## Tool Workflow ### General Guideline Search (Parallel Calls) | Tool | Key Parameters | Notes | |------|---------------|-------| | `NICE_Clinical_Guidelines_Search` | `query`, `limit` (both required) | Best general source; returns list directly | | `GIN_Guidelines_Search` | `query`, `limit` (both required) | Best multi-society aggregator | | `TRIP_Database_Guidelines_Search` | `query`, `limit`, `search_type='guidelines'` (all required) | Must include search_type | | `WHO_Guidelines_Search` | `query`, `limit` | Limited topic filtering; may return unrelated WHO docs | | `CMA_Guidelines_Se
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.