← PhysioKeysCONTENT HISTORY

Update to PhysioKeys

Snapshot Nov 9, 2026 · 00:20 UTC · version 1.2.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save PhysioKeys and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when a user asks to compare rehabilitation interventions, exercise approaches or treatment alternatives using published research, including which approach is better and where results differ.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 251
    }
  ],
  "name": "compare-interventions",
  "skill_md_contents": "---\nname: compare-interventions\ndescription: Use when a user asks to compare rehabilitation interventions, exercise approaches or treatment alternatives using published research, including which approach is better and where results differ.\n---\n\n# Compare interventions\n\nRead [the evidence and tool contract](../../references/evidence-workflows.md) first.\n\n1. Establish the condition/population, alternatives and outcomes. Use a supplied comparison directly; clarify only a difference that would change which evidence applies.\n2. Choose depth from the shared [adaptive search and reading budgets](../../references/evidence-workflows.md#adaptive-search-and-reading-budgets). If the comparison is limited to supplied or selected papers, skip discovery and read that set. For discovery, start with one search naming both alternatives and the condition, using the [source-selection policy](../../references/evidence-workflows.md#source-selection-and-pubmed-approval) and the live schema's supported result maximum. Prefer relevant direct comparisons. Refine to fill an identified comparator, outcome or follow-up gap within the whole-task budget. Read chosen papers in batches using the shared [exact-article full-text fallback](../../references/evidence-workflows.md#exact-article-full-text-fallback) for their access and provenance. A thorough comparison can require more than five papers. Use the shared source-specific ledger for larger comparisons.\n3. Build a readable comparison table, combining columns where helpful, that preserves source/citation, population and sample size if reported, intervention and comparator, outcome/measure, follow-up, reported result/uncertainty, and evidence access. Use “not reported in available text” for missing facts instead of invented values. If no relevant paper was returned, give a short explanation of the search limits rather than an empty table.\n4. Separate **direct comparative findings** from **indirect evidence**. Two trials against different controls do not establish which intervention is superior. Compare like outcomes and timepoints; do not pool or rank incompatible populations, scales or follow-up periods. A statistically nonsignificant result does not establish equivalence.\n5. Explain what the evidence supports for the user's general research question, what prevents a fair comparison, and what a useful head-to-head study would need to resolve. Do not manufacture a winner, numerical effect, formal certainty grade or patient-specific recommendation.\n6. State source coverage, search-call count, unique candidates screened, papers actually read/included and access limitations, sized to the request. Report any host fallback attempts separately. Do not turn screened snippets into claims of completed reading. If asked to save cited papers, use only verified PMIDs and the existing save tool, report each actual outcome, and identify UUID-only sources that cannot be saved through that tool. Do not save merely because a paper was cited.\n\nExample: eccentric loading versus heavy slow resistance for Achilles tendinopathy. A 12-week pain trial against waitlist and a 6-week function trial against usual care belong in separate rows; their results cannot determine a treatment winner.\n"
}

SHA-256 of public snapshot: cf0d5a6a868d67ba252b29c54b69219bef9350199715290dd9b0f2215c75c490