v1.0.0

GPT-4o-image

BenignClawScan verdict for this skill. Analyzed May 1, 2026, 6:49 AM.

Analysis

This is a straightforward PoYo image-generation API helper that uses a PoYo API key and sends user-provided payloads to PoYo, with no evidence of hidden persistence, exfiltration, or destructive behavior.

GuidanceThis skill appears safe for its stated purpose. Before installing, make sure you are comfortable giving it a PoYo API key, sending prompts and reference image URLs to PoYo, and potentially consuming PoYo credits when jobs are submitted.

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.

Abnormal behavior control

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.

Tool Misuse and Exploitation

SeverityLowConfidenceHighStatusNote

SKILL.md

Use `scripts/submit_gpt_4o_image.sh` to submit a raw JSON payload from the shell.

The skill exposes a shell/curl workflow that can submit arbitrary JSON payloads to the PoYo generation endpoint. This is purpose-aligned, but users should ensure the payload is intended before submission.

User impactA submitted payload may start an external generation job and may include prompts, image URLs, or callback settings.

RecommendationReview the final payload, model ID, image URLs, and callback_url before running the helper or allowing the agent to submit a job.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityLowConfidenceHighStatusNote

scripts/submit_gpt_4o_image.sh

api_key="${POYO_API_KEY:-${1:-}}" ... -H "Authorization: Bearer $api_key"

The helper uses a PoYo API key as a Bearer token to submit requests. This is necessary for the stated PoYo integration, but it grants access to the user's PoYo account/API quota.

User impactThe agent can submit PoYo generation jobs using the configured API key, which may consume account credits or quota.

RecommendationUse a dedicated or scoped PoYo API key if available, prefer setting POYO_API_KEY over passing the key on the command line, and monitor PoYo usage.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Insecure Inter-Agent Communication

SeverityInfoConfidenceHighStatusNote

references/api.md

`image_urls` (string[], optional) — Reference image URLs ... `callback_url` (string, optional) — Webhook callback URL for result notifications

The API workflow may send user-provided image URLs and callback destinations to an external provider. This is disclosed and expected for image editing/status notification, but it is still an external data flow.

User impactPrompts, reference image URLs, and callback URLs included in the payload are shared with PoYo and possibly with the configured callback receiver.

RecommendationAvoid including private images, secrets, or internal callback URLs unless you are comfortable sharing them with PoYo and the callback endpoint.