---
name: seedance-2-5-prompts
description: Search and adapt TapVid's public Seedance 2.5 prompt library, then optionally continue with TapVid MCP after explicit user confirmation.
---

# TapVid Seedance 2.5 prompt library

Use this skill when a user wants to find, compare, or adapt a Seedance 2.5 video prompt. The library contains 36 editorial templates and 120 community prompts with attribution.

## Important boundaries

- Read the public prompt feeds on demand. This does not train Codex or any other Agent on the library.
- This corpus has not been model-benchmarked or tested by TapVid on Seedance 2.5.
- TapVid MCP creates videos through TapVid's workflow. It is not a native Seedance 2.5 model connection.
- Do not claim that a prompt has been verified on a model unless a cited source explicitly establishes that fact.

## Public sources

- Editorial feed: https://tapvid.ai/video-prompts/seedance-2-5/feed?locale=<locale>
- Community feed: https://tapvid.ai/video-prompts/seedance-2-5/community-feed?locale=<locale>
- Supported locales: de, en, es, ja, ko, zh-CN, zh-TW
- TapVid MCP guide: https://tapvid.ai/api-mcp
- TapVid MCP endpoint: https://mcp.tapvid.ai/mcp

Fetch both feeds for the user's locale. If a request fails, report its URL and HTTP status. Do not silently say that all 156 prompts were searched.

## Prompt workflow

1. Determine the subject, use case, style, aspect ratio, duration, available source assets, approved copy, and hard constraints. Do not ask again for facts the user already supplied.
2. Parse the two JSON feeds outside the conversation when possible. Do not paste all 156 records into the chat.
3. Rank records by title, summary, category, use case, styles, and subjects. Inspect no more than five leading candidates before choosing or combining a structure.
4. Preserve the user's product identity, factual copy, numbers, legal wording, approved copy, and asset references. Leave a clear placeholder rather than inventing an unknown fact.
5. For editorial records, preserve the CC BY 4.0 source reference. For community records, preserve the original author and source URL, and follow the separate rights notice returned by the feed.
6. Return the adapted prompt, the source records used, unresolved placeholders, and the constraints to check before generation.

## Optional TapVid MCP handoff

If TapVid MCP is unavailable, stop after returning the adapted prompt and direct the user to https://tapvid.ai/api-mcp.

If TapVid MCP is available:

1. Call get_account first as a read-only account and credit check.
2. Call upload_material only for assets the user supplied or explicitly approved.
3. Explain that create_video may consume credits. Call create_video only after the user explicitly requests generation and gives explicit confirmation for that paid action.
4. Use get_video_status to monitor a confirmed job and get_video_download only when the completed result is requested.
5. Do not automatically retry create_video after a timeout, network interruption, or other ambiguous failure. Check status or ask the user before any further potentially paid action.
6. Preserve stable errors such as insufficient credits or invalid material in the response instead of hiding the error code.

Never request, print, store, or place credentials in the prompt library. Follow the MCP client's own secure connection flow.