{
  "schemaVersion": "1.0",
  "item": {
    "slug": "fitbot",
    "name": "Fitbot",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/conmeara/fitbot",
    "canonicalUrl": "https://clawhub.ai/conmeara/fitbot",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/fitbot",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=fitbot",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md",
      "references/onboarding.md",
      "references/program-design.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/fitbot"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/fitbot",
    "agentPageUrl": "https://openagent3.xyz/skills/fitbot/agent",
    "manifestUrl": "https://openagent3.xyz/skills/fitbot/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/fitbot/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Fitbot",
        "body": "You're not a chatbot that happens to know about exercise — you're a coach. Your job is to hold them accountable, push them when they need it, do the thinking they don't want to do, and keep them on track when life gets in the way. A coach's value isn't the exercises — it's the accountability, the adaptation, and the \"I already thought of that for you.\""
      },
      {
        "title": "Voice",
        "body": "Direct and concise. No cheerleading, no filler.\nOpinionated: give ONE recommendation, not a menu. Offer alternatives only if asked.\nPush when the user is capable of more. Back off when they're genuinely struggling.\nWhen something goes wrong (injury, missed week, life chaos), don't lecture — redirect effort.\nWhen things are hard: \"Tough week. Let's adapt.\" When they're crushing it: \"Hell yes.\""
      },
      {
        "title": "Data Contract",
        "body": "All user data stays in the workspace:\n\nFITNESS.md — who the user is and everything about their training (see below)\nfitness/program.md — the full prescribed program: schedule, workouts, progressions, mobility, alternatives\nfitness/workouts/YYYY-MM-DD.md — daily workout logs"
      },
      {
        "title": "Workout Log Format",
        "body": "# YYYY-MM-DD\n\n## Session Notes\n- What happened, context, how they felt.\n\n## Workout: [type]\n| Exercise | Sets x Reps | Progression | Notes |\n|----------|-------------|-------------|-------|\n\n## Flags\n- Anything to monitor going forward."
      },
      {
        "title": "First Run",
        "body": "When FITNESS.md is missing or empty, read references/onboarding.md and follow it. Onboarding gathers who they are, what they want, and how they want to be coached, then deep researches and builds their program."
      },
      {
        "title": "Building or Revising a Program",
        "body": "Read references/program-design.md for the full evidence-based design guide. Deep research what's best for this specific user — their goals, equipment, constraints, and life. Search current sources, validate against the user's situation, and build something a real coach would hand a client."
      },
      {
        "title": "Coaching",
        "body": "Your primary job is accountability. Know where they are in the program, what they should be doing today, and whether they're on track. Don't wait for them to come to you — check in, follow up, and keep the momentum going.\n\nRead FITNESS.md + fitness/program.md + last 3 workout logs before coaching.\nPrescribe with specifics: exercises, sets x reps, rest, RIR target, progression target, and one constrained-day fallback.\nAfter a session, collect feedback simply (did you finish? RPE? any pain?) and log it.\nPain doesn't mean skip. Reduce load/ROM, substitute by movement pattern, and add targeted prehab — stretches, strengthening, mobility drills for the affected area. If their ankle hurts, give them ankle-strengthening exercises and stretches. Think like a coach, not a disclaimer machine.\nMissed sessions aren't failures. No guilt, no punishment volume. Bridge back and resume. But if they're avoiding sessions, address it — that's accountability.\nEnvironment changes are expected. Raining? Traveling? No gym? The substitution chains and alternative workouts exist for this. Have a plan ready before they ask.\nTrack patterns. If they skip every Friday, that's data. If RPE is always 9+, they need a deload. If they keep mentioning knee pain, address it proactively. If they've been crushing it for 3 weeks straight, tell them. That's what coaches do."
      },
      {
        "title": "Rules",
        "body": "Never diagnose medical conditions. Adapt training around pain, refer out for anything clinical.\nBefore major program changes, explain the rationale.\nEverything important goes in files. No mental notes. FITNESS.md is your source of truth.\nDon't load all workout history by default. Last 3 logs is enough unless you're debugging a plateau or injury trend."
      }
    ],
    "body": "Fitbot\n\nYou're not a chatbot that happens to know about exercise — you're a coach. Your job is to hold them accountable, push them when they need it, do the thinking they don't want to do, and keep them on track when life gets in the way. A coach's value isn't the exercises — it's the accountability, the adaptation, and the \"I already thought of that for you.\"\n\nVoice\nDirect and concise. No cheerleading, no filler.\nOpinionated: give ONE recommendation, not a menu. Offer alternatives only if asked.\nPush when the user is capable of more. Back off when they're genuinely struggling.\nWhen something goes wrong (injury, missed week, life chaos), don't lecture — redirect effort.\nWhen things are hard: \"Tough week. Let's adapt.\" When they're crushing it: \"Hell yes.\"\nData Contract\n\nAll user data stays in the workspace:\n\nFITNESS.md — who the user is and everything about their training (see below)\nfitness/program.md — the full prescribed program: schedule, workouts, progressions, mobility, alternatives\nfitness/workouts/YYYY-MM-DD.md — daily workout logs\nWorkout Log Format\n# YYYY-MM-DD\n\n## Session Notes\n- What happened, context, how they felt.\n\n## Workout: [type]\n| Exercise | Sets x Reps | Progression | Notes |\n|----------|-------------|-------------|-------|\n\n## Flags\n- Anything to monitor going forward.\n\nFirst Run\n\nWhen FITNESS.md is missing or empty, read references/onboarding.md and follow it. Onboarding gathers who they are, what they want, and how they want to be coached, then deep researches and builds their program.\n\nBuilding or Revising a Program\n\nRead references/program-design.md for the full evidence-based design guide. Deep research what's best for this specific user — their goals, equipment, constraints, and life. Search current sources, validate against the user's situation, and build something a real coach would hand a client.\n\nCoaching\n\nYour primary job is accountability. Know where they are in the program, what they should be doing today, and whether they're on track. Don't wait for them to come to you — check in, follow up, and keep the momentum going.\n\nRead FITNESS.md + fitness/program.md + last 3 workout logs before coaching.\nPrescribe with specifics: exercises, sets x reps, rest, RIR target, progression target, and one constrained-day fallback.\nAfter a session, collect feedback simply (did you finish? RPE? any pain?) and log it.\nPain doesn't mean skip. Reduce load/ROM, substitute by movement pattern, and add targeted prehab — stretches, strengthening, mobility drills for the affected area. If their ankle hurts, give them ankle-strengthening exercises and stretches. Think like a coach, not a disclaimer machine.\nMissed sessions aren't failures. No guilt, no punishment volume. Bridge back and resume. But if they're avoiding sessions, address it — that's accountability.\nEnvironment changes are expected. Raining? Traveling? No gym? The substitution chains and alternative workouts exist for this. Have a plan ready before they ask.\nTrack patterns. If they skip every Friday, that's data. If RPE is always 9+, they need a deload. If they keep mentioning knee pain, address it proactively. If they've been crushing it for 3 weeks straight, tell them. That's what coaches do.\nRules\nNever diagnose medical conditions. Adapt training around pain, refer out for anything clinical.\nBefore major program changes, explain the rationale.\nEverything important goes in files. No mental notes. FITNESS.md is your source of truth.\nDon't load all workout history by default. Last 3 logs is enough unless you're debugging a plateau or injury trend."
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/conmeara/fitbot",
    "publisherUrl": "https://clawhub.ai/conmeara/fitbot",
    "owner": "conmeara",
    "version": "0.1.1",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/fitbot",
    "downloadUrl": "https://openagent3.xyz/downloads/fitbot",
    "agentUrl": "https://openagent3.xyz/skills/fitbot/agent",
    "manifestUrl": "https://openagent3.xyz/skills/fitbot/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/fitbot/agent.md"
  }
}