Hybrid training plan

v1.0.1

View and manage a Hybrid Training Plan — check today's workout, log strength sets and runs, mark days complete or skip, view exercise 1RMs and session histor...

⭐ 0· 358·0 current·0 all-time

byPaul Kenneth Kent@paulkennethkent

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for paulkennethkent/hybrid-training-plan.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Hybrid training plan" (paulkennethkent/hybrid-training-plan) from ClawHub.
Skill page: https://clawhub.ai/paulkennethkent/hybrid-training-plan
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: HYBRID_API_KEY
Required binaries: curl, jq
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install paulkennethkent/hybrid-training-plan

ClawHub CLI

Package manager switcher

npx clawhub@latest install hybrid-training-plan

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

Name/description (viewing and managing a Hybrid Training Plan) matches what the skill does: a small CLI wrapper that calls hybridtrainingplan.app endpoints. Required binaries (curl, jq) and the single env var (HYBRID_API_KEY) are appropriate and expected.

✓

Instruction Scope

SKILL.md directs the agent to use the provided scripts/htp.sh to call the documented API endpoints and to set HYBRID_API_KEY (and optional HYBRID_API_URL). The instructions do not request unrelated files, system state, or other credentials, nor do they direct data to unexpected external endpoints.

✓

Install Mechanism

No install spec; this is instruction-only with a small included shell script. Nothing is downloaded from external, untrusted URLs and the script itself is short and readable.

✓

Credentials

Only HYBRID_API_KEY (primary credential) is required. That is proportionate: the skill needs to authenticate to the user's hybridtrainingplan.app account to read/update plans and logs. No unrelated secrets or config paths are requested.

✓

Persistence & Privilege

always is false and the skill does not request persistent system-wide privileges or alter other skills. It only expects the API key to be set in the agent environment and a local executable script to be made runnable.

Assessment

This skill is a simple CLI wrapper for hybridtrainingplan.app and legitimately needs only your HYBRID_API_KEY. Treat that key like a password: only provide it to trusted agents and revoke it from your account if you stop using the skill. Before enabling, confirm you are comfortable the skill can mark days complete/skip, create/update session logs, and update 1RMs (it will perform those API actions). If possible, create a scoped API key (or one you can revoke) rather than using a long-lived key you rely on elsewhere. You may also review the included scripts/htp.sh yourself (it's short and readable) and ensure HYBRID_API_URL is set only if you trust a non-default endpoint.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

Binscurl, jq

EnvHYBRID_API_KEY

Primary envHYBRID_API_KEY

latestvk975dy193q88pjtbhxng4vypex81z503

358downloads

0stars

2versions

Updated 1mo ago

v1.0.1

MIT-0

Hybrid Training Plan Skill

Interact with the user's training plan at hybridtrainingplan.app via natural language.

Setup

Generate an API key at hybridtrainingplan.app/account → Agent Skills → New key
Add to your Claude environment (.claude/.env or shell profile):

export HYBRID_API_KEY="htp_your_key_here"
export HYBRID_API_URL="https://api.hybridtrainingplan.app"   # optional, this is the default

The helper script is at scripts/htp.sh relative to this skill. Run chmod +x scripts/htp.sh once to make it executable.

Common operations

Check today's dashboard

scripts/htp.sh dashboard

Returns the current plan ID, today's date, active week/day info, and recent session summaries.

View a specific day's workout

scripts/htp.sh day 2026-02-27 <planId>

Returns the day's sessions with exercises, sets, reps, load guidance, and running prescription.

Log a session

scripts/htp.sh log-session '{"planId":"...","sessionId":"...","dayDate":"2026-02-27","sessionType":"strength","strengthSets":[{"exerciseName":"Squat","exerciseKey":"squat","setIndex":0,"reps":5,"weightKg":100}]}'

Mark a day complete

scripts/htp.sh complete 2026-02-27 <planId>

Skip a day

scripts/htp.sh skip 2026-02-27 <planId>

View session logs for a day

scripts/htp.sh session-logs <planId> 2026-02-27

View exercise 1RMs (maxes)

scripts/htp.sh maxes

Update a 1RM

scripts/htp.sh set-max "Squat" 120

Notes

Weights are always in kg in the API regardless of the user's display preference
sessionId is the UUID of the specific session inside the plan (visible in the day view response)
planId is the UUID of the training plan (visible in the dashboard response)
See references/api.md for full request/response schemas

Comments

Loading comments...