Fitness Challenge Video

Fitness challenges get 3x more social media engagement than standard workout posts. Your 30-day challenge, transformation journey, and weekly workout documen...

Security Scan

The skill's purpose (editing/assembling workout videos) is plausible, but metadata and runtime instructions are vague and internally inconsistent (it requests a NEMO_TOKEN and references a nemovideo config path while providing no upload endpoints or concrete behavior), so it's unclear how your files and token would be used.

Purpose & Capability

The skill's name and description match a service that would plausibly need an API token (NEMO_TOKEN) to upload/process videos. However the registry listing earlier shows no required config paths while the SKILL.md metadata includes configPaths [~/.config/nemovideo/], which is an inconsistency. That config path would imply the skill might read/write a local service config, which is not explained by the description.

Instruction Scope

SKILL.md is high-level and open-ended: it tells the agent to 'upload your workout footage' and 'assemble' videos but gives no API endpoints, no explicit instructions for how uploading happens, and no constraints on what files to read. This vagueness gives the agent broad discretion to request, read, or transmit user files and credentials without clear boundaries or auditing instructions.

Install Mechanism

There is no install spec and no code files — this is instruction-only, which minimizes disk-write/installation risk. No third-party downloads or package installs are requested.

Credentials

The skill only requires a single environment variable (NEMO_TOKEN), which is proportionate for a hosted video-processing API. But the SKILL.md metadata's configPaths entry (not reflected in the registry's 'Required config paths') raises the possibility of local config access; the token and potential config access should be explained by the author.

Persistence & Privilege

always:false and no install steps are defined. The skill does not request permanent presence or modifications to other skills or global agent settings.

What to consider before installing

Before installing, ask the publisher for specifics: which NemoVideo API/endpoint will be used, exactly how NEMO_TOKEN is used and what permissions it grants, whether footage is uploaded to a third-party server and how long it's stored, and whether the skill will read any local config at ~/.config/nemovideo/. Prefer scoped or revocable tokens and avoid supplying your primary account credentials. If possible, test with a throwaway token and non-sensitive sample videos first. If the author cannot explain where files are uploaded and how credentials are used, treat the skill as risky and do not provide real tokens or private footage.

Fitness Challenge Video — Every Workout Documented, Every Week Published

Use Cases

1. 30-Day Challenge Recaps — Weekly summary videos for ongoing fitness challenges, showing days 1-7, 8-14, etc. with progress notes and motivational messaging for challenge participants.

2. Personal Trainer Client Programs — Challenge documentation videos for PT clients, showing their workout consistency and progress for motivation and social proof marketing.

3. Transformation Journey Documentation — Long-form transformation content that compresses weeks of training into shareable progress videos at 30, 60, and 90-day milestones.

4. Gym Challenge Marketing — Promotional challenge videos for gym membership acquisition campaigns, showing real member participation and results from past challenges.

How It Works

Upload your workout footage and specify the challenge structure and current progress day. Fitness Challenge Video assembles the recap, adds music and day overlays, and exports challenge videos for every platform.