AI Gender Swap

Transform photos and images into Studio Ghibli-style artwork using AI via Media.io OpenAPI. Applies the iconic hand-drawn, painterly aesthetic of Ghibli film...

Security Scan

This instruction-only skill is internally consistent: it only needs curl and a single MEDIAIO_API_KEY to call Media.io OpenAPI endpoints for asynchronous gender-swap image generation.

Purpose & Capability

The skill's name/description (Media.io gender-swap in Ghibli style) matches the declared requirements: one HTTP client binary (curl) and one service API key (MEDIAIO_API_KEY). Required endpoints and the model code referenced correspond to Media.io's generation API; there are no unrelated credentials, binaries, or configuration paths requested. Note: the skill's source is listed as unknown in the registry metadata, but the SKILL.md points to Media.io endpoints and the platform docs URL.

Instruction Scope

SKILL.md provides concrete, narrow runtime instructions: call credits endpoint, submit create-task with an image URL, poll result endpoint, and return output URLs. It requires the caller to provide an externally reachable image URL (explicitly excludes local-only uploads). The instructions do not ask the agent to read arbitrary system files, other environment variables, or to send data to off-network endpoints. The doc also includes basic safety guidance (validate URL, avoid logging raw API keys).

Install Mechanism

There is no install spec and no code files—this is instruction-only. That minimizes disk writes and arbitrary code execution risk; the only runtime dependency is curl which is a reasonable, minimal requirement for making HTTP requests.

Credentials

Only MEDIAIO_API_KEY is required and is declared as the primary credential. That aligns with the skill's purpose (calling Media.io APIs). No unrelated secrets or multiple service credentials are requested.

Persistence & Privilege

The skill is not marked always:true and has no install-time modifications or requests for system-wide config. The default ability for the agent to invoke the skill autonomously is unchanged and is normal for skills; it is not combined with broad credential or persistence demands.

Assessment

This skill appears coherent, but before installing: 1) Only provide an API key scoped to Media.io (avoid reusing high-privilege or long-lived keys). 2) Verify the MEDIAIO_API_KEY is from your Media.io account and check Media.io's billing/credit implications (the skill checks credits before generation). 3) The API expects an externally reachable image URL—do not supply private/local file URLs unless you host them temporarily for the service. 4) Review Media.io's privacy and retention policy for generated images (output URLs may be signed/temporary). 5) Because the registry lists an unknown source, consider verifying the owner/publisher or obtaining the SKILL.md from a trusted source (Media.io docs) if you require stronger provenance assurance.

Media.io AI Gender Swap Skill

Overview

This skill calls Media.io OpenAPI to run image gender swap using model code effects_image_gender_swap_female. The API is asynchronous:

1. Submit generation request and get task_id.
2. Poll task result endpoint until the task is finished.

When To Use

• The user wants to transform a portrait from male to female style using Media.io.
• The user can provide an image URL reachable by Media.io servers.
• The user wants task-based generation with polling.

When Not To Use

• The user asks for local file upload only (this API expects image URL input).
• The user asks for non-Media.io providers.
• The user asks for real-time synchronous image output in one call.

Requirements

Environment Variables

Variable	Required	Description
MEDIAIO_API_KEY	Yes	Media.io OpenAPI key, used in header X-API-KEY.

Base Headers

• Content-Type: application/json
• X-API-KEY: $MEDIAIO_API_KEY

Supported Endpoints

1) Query Credits

• Method: POST
• Endpoint: https://openapi.media.io/user/credits
• Body: {}
• Purpose: check available credits before generation.

2) Create Gender Swap Task

• Method: POST
• Endpoint: https://openapi.media.io/generation/effects/effects_image_gender_swap_female
• Body:

{
	"data": {
		"image": "https://example.com/input.jpg"
	}
}

• Required field:
  • data.image (string URL)
• Image constraints from API doc:
  • Format: PNG, JPEG, JPG
  • File size: 0.0 MB to 19.5 MB
  • Resolution: 300x300 to 4000x4000
  • Aspect ratio: 1:2 to 2:1

3) Query Task Result

• Method: POST
• Endpoint: https://openapi.media.io/generation/result/{task_id}
• Body: {}
• Path parameter:
  • task_id (string, required)

Request and Response Contract

Common Success Envelope

{
	"code": 0,
	"msg": "",
	"data": {},
	"trace_id": "..."
}

Create Task Response

• On success, data.task_id is returned.

Task Result Response

• data.status can be one of the following values:
  • waiting: queued
  • processing: running
  • completed: completed successfully
  • failed: failed
  • timeout: timed out
• data.reason: provides additional context (e.g., success or error message)
• When status is completed:
  • data.result is an array of output objects with generated image URLs
  • Each result object contains val (internal path), preview (public HTTPS URL), and status (completion status)

Standard Invocation Flow

1. Call user/credits to verify balance.
2. Call effects_image_gender_swap_female with data.image.
3. Extract task_id.
4. Poll generation/result/{task_id} every 3 to 5 seconds.
5. Stop when status is completed or failed.
6. Return output URLs from data.result when completed.

cURL Examples

Query Credits

curl --request POST \
	--url https://openapi.media.io/user/credits \
	--header 'Content-Type: application/json' \
	--header "X-API-KEY: $MEDIAIO_API_KEY" \
	--data '{}'

Create Gender Swap Task

curl --request POST \
	--url https://openapi.media.io/generation/effects/effects_image_gender_swap_female \
	--header 'Content-Type: application/json' \
	--header "X-API-KEY: $MEDIAIO_API_KEY" \
	--data '{
	"data": {
		"image": "https://example.com/input.jpg"
	}
}'

Query Task Result

curl --request POST \
	--url https://openapi.media.io/generation/result/<task_id> \
	--header 'Content-Type: application/json' \
	--header "X-API-KEY: $MEDIAIO_API_KEY" \
	--data '{}'

Successful Response Example

{
	"code": 0,
	"msg": "",
	"data": {
		"task_id": "effect-86f0f82a-36dc-4a7c-928a-721a18ef482f",
		"status": "completed",
		"reason": "success",
		"result": [
			{
				"val": "aicloudtmp/550160908/3/202603/1/combo_tm_alg-20260317165022-802800-60eb3-dwt.png",
				"preview": "https://url_to_generated_image.png",
				"status": "completed"
			}
		]
	},
	"trace_id": "a18315ba568b5c34407808d12cbc8457"
}

Response fields when status is completed:

• data.task_id: unique task identifier
• data.status: completed indicates successful completion
• data.reason: success indicates no error occurred
• data.result: array of output objects, each containing:
  • val: internal file path of the generated image
  • preview: publicly accessible HTTPS URL for the generated image with expiration and signature
  • status: completed for each result item

Error Handling Guidance

• Treat code != 0 as failure.
• Typical authentication errors:
  • 374004: not authenticated. Apply for an APP KEY at https://developer.media.io/.
• Typical request validation error:
  • 490000: params error
• Typical billing/credits error:
  • 490505: insufficient credits. Recharge before invoking generation APIs.
• Always include trace_id in logs for troubleshooting.

Agent Behavior Requirements

• Validate that input contains a non-empty image URL before calling the create endpoint.
• Do not claim immediate output after task creation; always poll by task_id.
• If credits are insufficient, return a clear message and stop instead of retry loops.
• Avoid exposing raw API keys in logs or responses.

Safety and Compliance Notes

• Only process user-provided or user-authorized images.
• Do not imply identity verification or biometric certainty from generated images.
• Generated output is synthetic media and should be presented as edited content.

References

• Media.io platform: https://developer.media.io/
• API documentation: https://platform.media.io/docs/