@acedatacloud/skills 2026.816.2 → 2026.816.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@acedatacloud/skills",
|
|
3
|
-
"version": "2026.816.
|
|
3
|
+
"version": "2026.816.3",
|
|
4
4
|
"description": "Agent Skills for AceDataCloud AI services — music, image, video generation, LLM chat, web search. Compatible with Claude Code, GitHub Copilot, Gemini CLI, OpenAI Codex, and 30+ AI coding agents.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"agent-skills",
|
|
@@ -74,6 +74,7 @@ Every topic block must keep this schema: `TOPIC`, `FAMILY`, `SERVICE`, `APIS`, `
|
|
|
74
74
|
- PROMISE: Seedance 2.0 preserves a referenced person/character and can follow audio/video references at high resolution.
|
|
75
75
|
- DEMOS:
|
|
76
76
|
- `seedance-character-reference`: use a safe fictional/non-private character reference across a new scene; compare identity at start/middle/end.
|
|
77
|
+
- `seedance-image-reference-control`: use a public fictional product/interface image as `reference_image`; prove visible structure/text treatment remains recognizable while the accepted MP4 adds requested camera motion. Show the exact reference URL, request, and start/middle/end decoded output frames; do not claim person/character identity or motion-reference input.
|
|
77
78
|
- `seedance-motion-reference`: supply reference video for motion/camera language and show the generated reinterpretation.
|
|
78
79
|
- `seedance-audio-reference`: pair a character image and safe reference audio; verify motion/audio result without identity claims about real people.
|
|
79
80
|
- EVIDENCE: actual reference media at a provider-downloadable public HTTPS URL, accepted output MP4, frame/contact sheet, minimal multimodal request, task lifecycle. Remote video APIs must never receive `data:`, `blob:`, or local-file reference URLs; upload references first and verify HTTPS reachability.
|