Nano Banana 2
Analysis
The skill appears to be a coherent NanoPhoto image API integration, but it uses your NanoPhoto API key, can spend service credits, and sends prompts or public image URLs to NanoPhoto.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Credits are pre-deducted and refunded automatically if generation fails.
Submitting generation jobs can spend NanoPhoto credits, which is disclosed and purpose-aligned but is still a cost-bearing action.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Primary credential: `NANOPHOTO_API_KEY` ... Resolution order in the bundled script: `--api-key` → `NANOPHOTO_API_KEY` environment variable → `~/.openclaw/openclaw.json` skill env
The skill clearly declares one NanoPhoto credential and a bounded fallback location for retrieving it; this is expected for the integration but still grants account-level API access.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
`POST https://nanophoto.ai/api/nano-banana-2/generate` ... `prompt` | string | Yes ... `inputImageUrls` | string[] | Conditional | Required for `edit`; public URLs only; max 14
The API workflow sends prompts and optional input image URLs to the external NanoPhoto service.
