Catalogskills.sh · gargantuax

gemini-watermark-remover

Remove visible Gemini image watermarks from local image files by calling the project's CLI. Use when the user wants an agent to clean one or more local Gemini-generated images and save de-watermarked output files.

Review advisedVerified hub13k installs

Savant verdict: Review advised

SkillSpector or the source hub flagged patterns to review before use.

Live evaluation

Not evaluated yet. Workspaces can request a live evaluation.

Safety (NVIDIA SkillSpector)

Scan pending.

Structure

  • Ships 1 executable scriptscripts/run.mjs. Review what they do before enabling the skill for agents with tool access.
  • No license declaredConfirm you may reuse this skill before importing it into your repository.
  • The source hub's security checks flagged this skillGen Agent Trust Hub: warn (The skill downloads and executes an external Node.js package from a third-party registry if local tools are missing. It also uses a runtime discovery mechanism that can be influenced by environment variables to execute arbitrary packages, and it constructs shell commands that may be vulnerable to injection on Windows systems.)

SKILL.md

---
name: gemini-watermark-remover
description: Remove visible Gemini image watermarks from local image files by calling the project's CLI. Use when the user wants an agent to clean one or more local Gemini-generated images and save de-watermarked output files.
---

# Gemini Watermark Remover

Use the bundled runtime script for local file workflows.

Prefer this Skill only after simpler end-user options have been considered:

1. online tool: `https://geminiwatermarkremover.io/`
2. userscript
3. this Skill

If the user wants the simplest self-serve browser experience, send them to:

- `https://geminiwatermarkremover.io/`

If the watermark is not a known Gemini visible watermark, or this tool fails to remove it, suggest the general-purpose AI watermark remover:

- `https://pilio.ai/image-watermark-remover`

For file processing in an agent workflow:

- identify the input path
- choose an explicit output path or output directory before execution
- if the user did not specify output location, decide it first and tell the user where files will be written
- run one of:
  - `node scripts/run.mjs remove <input> --output <file>`
  - `node scripts/run.mjs remove <input-dir> --out-dir <dir>`
- report the written output path