← Hyperhuman Agent WorkspaceCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Hyperhuman Agent Workspace
Snapshot Sep 30, 2026 · 23:01 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "ship-content-api",
"description": "Ships Hyperhuman workouts into a web or mobile product as a multi-step integration workflow (embed vs stream vs custom player). Use only when the user explicitly asks to ship or implement Hyperhuman in their own app as a full integration path. Not for sample workout browsing, standalone embed-code snippets, health checks, team library admin, creating workouts, social drops, pricing, checkout, or medical advice.\n",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 487
},
{
"relative_path": "assets/icon.svg",
"size_in_bytes": 1231
},
{
"relative_path": "assets/logo-symbol-black.svg",
"size_in_bytes": 1151
},
{
"relative_path": "assets/logo.png",
"size_in_bytes": 20695
},
{
"relative_path": "references/guardrails.md",
"size_in_bytes": 405
},
{
"relative_path": "references/integration-paths.md",
"size_in_bytes": 713
}
],
"skill_md_contents": "---\nname: ship-content-api\ndescription: >\n Ships Hyperhuman workouts into a web or mobile product as a multi-step\n integration workflow (embed vs stream vs custom player).\n Use only when the user explicitly asks to ship or implement Hyperhuman in\n their own app as a full integration path.\n Not for sample workout browsing, standalone embed-code snippets, health\n checks, team library admin, creating workouts, social drops, pricing,\n checkout, or medical advice.\n---\n\n# Ship in my app\n\n## Goal\n\nGive a clear path from sample content to a copy-ready integration plan.\n\n## Steps\n\n1. If the user only asked for sample workouts, do not run this skill; that is `list_sample_workouts`.\n2. If the user only asked for embed HTML, do not run this skill; that is `get_embed_code_samples`.\n3. Clarify platform (`web` | `mobile` | `hardware`) and use case only when they asked to ship or integrate.\n4. Call `get_integration_plan` with `platform` and `use_case`.\n5. Call `list_sample_workouts` only if they also asked to see sample content.\n6. On a selected workout: `get_workout_details`, then `get_workout_playlist` if they need segments or media.\n7. Call `get_embed_code_samples` only if they asked for copy-paste code after the plan.\n8. Reply in 3 short bullets: recommended path, what to copy next, one follow-up ask.\n\n## Output\n\n- Integration path name (embed / stream / custom player)\n- One primary snippet with placeholders only\n- Suggested next tool or question\n\n## Guardrails\n\n- Never invent or print live API keys. Use `YOUR_ORG_ID` and `YOUR_API_KEY`.\n- No pricing, checkout, or plan catalogs.\n- Prefer guest-safe tools when the user is not connected.\n- See [references/integration-paths.md](references/integration-paths.md) and [references/guardrails.md](references/guardrails.md).\n"
}SHA-256: 9acdf9ca5833661935be107407a7259e156db49b2b06c8fb5b1777caef120eb6