WeryAI video tool — watermark remove

Remove watermark overlays from an existing HTTPS video via WeryAI (video-watermark-remove). Use when the user wants watermark cleanup, not subtitles-only or...

Security Scan

The skill's code, runtime instructions, and requested credential (WERYAI_API_KEY) align with its stated purpose of removing watermarks via WeryAI and do not request unrelated access or installs.

Purpose & Capability

Name/description, required binary (node), primary env var (WERYAI_API_KEY), and the CLI script all match the stated goal (calling WeryAI's /v1/generation/video-watermark-remove endpoint to process an HTTPS video URL). No unrelated cloud credentials or uncommon binaries are requested.

Instruction Scope

SKILL.md explicitly limits the workflow to a single entry script and public https:// video URLs; the included script validates https URLs, reads only process.env.WERYAI_API_KEY, and performs network calls to the WeryAI API. There are no instructions to read arbitrary local files, scan unrelated system state, or transmit data to other endpoints.

Install Mechanism

This is instruction-only with a bundled Node script and no install spec or third‑party downloads. No archives or external installers are invoked; risk from installation is low.

Credentials

Only WERYAI_API_KEY is required and declared as the primary credential; the SKILL.md and script both assert they use only that env var. The credential request is proportionate to a remote API call to WeryAI.

Persistence & Privilege

always:false and no evidence of the skill modifying other skills or agent-wide configuration. The script does not persist secrets to disk per its own security guidance.

Assessment

This package appears coherent for its stated purpose, but before running: 1) verify the only files present are SKILL.md and scripts/video_watermark_remove.js (remove any unexpected sibling scripts); 2) only set WERYAI_API_KEY in the environment (do not provide other secrets); 3) confirm the video URL is a public https:// URL you are allowed to process and explicitly confirm any submit/wait action because runs may be paid; 4) review the script locally to ensure there are no modifications that change endpoints or upload behavior. Absence of red flags here doesn't eliminate operational risks (privacy of uploaded content, service billing, or compromised upstream API), so proceed with those considerations in mind.

This skill is self-contained: it documents and runs only the watermark-remove workflow on an existing video given by URL. It is not text-to-video or image-to-video generation from scratch.

Entry script: scripts/video_watermark_remove.js (alongside this SKILL.md).

Runtime: WERYAI_API_KEY, Node.js 18+.

Inputs: video_url must be a public https:// URL. Optional rect_vo_list holds normalized box coordinates (0–1), not file paths. This script does not read local files and does not perform upload-file flows.

What this package ships (verify before trust)

Canonical layout for this skill only:

• SKILL.md, eval.yaml
• scripts/video_watermark_remove.js (the only runnable script in scope)

If your copy also contains scripts/video_gen.js, scripts/video_toolkits.js, references/WERYAI_VIDEO_API.md, or other CLIs, those files are not part of this skill’s contract — they may come from another repo sync or an over-broad install. Do not run them when you only want watermark-remove; remove them or reinstall from a clean source. Inspect what you run: node scripts/video_watermark_remove.js spec.

Other tools (multi-endpoint CLIs, local-file upload to growth/upload-file APIs, extra environment variables in those CLIs) are out of scope for this package. This skill’s script uses only WERYAI_API_KEY and public https:// URLs.

API surface (this tool only)

• Required: video_url (public https:// URL)
• Optional: rect_vo_list — array of { lt_x, lt_y, rb_x, rb_y } in 0..1; omit for auto-detect

From this skill root, run node scripts/video_watermark_remove.js spec to print the full tool schema (endpoint, required fields, defaults, enums) as JSON.

Pre-submit gate (mandatory)

Do not run submit / wait until the user explicitly confirms the video URL and any custom regions. Paid runs are not idempotent.

Workflow

Prefer --dry-run to validate JSON. Use wait to submit and poll until the task finishes; use submit only when the user wants a task_id without blocking, then status for later checks. Share final URLs as Markdown links [Video](https://…).

CLI

From this skill root:

node scripts/video_watermark_remove.js wait \
  --json '{"video_url":"https://example.com/video.mp4"}'

node scripts/video_watermark_remove.js submit \
  --json '{"video_url":"https://example.com/video.mp4"}'

node scripts/video_watermark_remove.js status --task-id <task-id>

Dry-run:

node scripts/video_watermark_remove.js wait \
  --json '{"video_url":"https://example.com/video.mp4"}' \
  --dry-run

Security

Never write WERYAI_API_KEY into files. Keep only WERYAI_API_KEY set for this workflow; do not rely on undocumented env vars in sibling scripts if any were mistakenly present. The in-scope script reads only WERYAI_API_KEY (no other env keys). video_watermark_remove.js accepts only https:// media URLs (no disk read / no upload-file). Base URL and poll intervals are constants in the script, not env-driven.

Do not pass local filesystem paths or run tools that accept them unless you have explicitly reviewed and consented to their upload behavior — that is never required for this skill.

Out of scope

• Subtitle erasure (different endpoint and intent)
• Text-to-video from scratch

References

• WeryAI llms.txt