mirror of https://git.openapi.site/https://github.com/desirecore/market.git synced 2026-06-06 05:50:41 +08:00

Files

xyx 4f7037a6b6 fix: replace hardcoded ~/.desirecore paths with ${DESIRECORE_ROOT} variable (#16 )

## Summary

- 将所有技能文件中的硬编码 `~/.desirecore/` 和 `$HOME/.desirecore/` 路径替换为
`${DESIRECORE_ROOT}/` 变量
- 递增 manifest.json version 至 1.2.1

## Why

dev 模式下 `DESIRECORE_HOME=~/.desirecore-dev`，硬编码路径导致技能读取错误的端口文件和目录。主仓库的
`variable-substitutor.ts` 会在运行时将 `${DESIRECORE_ROOT}` 替换为实际根目录。

## Test plan

- [ ] `npm run dev` 启动后触发任意技能，确认端口路径解析为
`~/.desirecore-dev/agent-service.port`
- [ ] prod 模式确认路径为 `~/.desirecore/agent-service.port`

🤖 Generated with [Claude Code](https://claude.com/claude-code)

2026-05-29 15:36:19 +08:00

8.8 KiB

Raw Blame History

name, description, license, version, type, risk_level, status, disable-model-invocation, provider, tags, requires, metadata, market

name

description

license

version

type

risk_level

status

disable-model-invocation

provider

minimax-video-gen Skill

Mandatory Rules (violation will cause failure)

Must use HTTPS to access agent-service — https://127.0.0.1:${PORT} with -k to skip certificate verification
Use Bash curl throughout — do not use the HttpRequest tool or Python
Polling interval is 10 seconds — use sleep 10 to wait

Full Execution Flow

Prerequisites

The user has already configured and enabled a MiniMax Provider (regular API or Token Plan) in Resource Manager → Compute and entered the API Key
agent-service is running

Core Concept: Three-Step Asynchronous Flow

MiniMax video generation uses an asynchronous task model:

Submit task: POST to create a video generation task and receive a task_id
Poll status: query the task status with task_id until status is "Success" or "Fail"
Download video: use file_id to obtain the download URL

Model Selection and Fallback Strategy

Model	Supported Modes	Characteristics	Use Case
MiniMax-Hailuo-2.3	Text-to-video + image-to-video	Highest quality, default first choice	Default when the user doesn't specify
MiniMax-Hailuo-2.3-fast	Image-to-video only	Fast, 50% lower cost	Fallback when quota is insufficient in image-to-video scenarios

Fallback rules (mandatory):

Use MiniMax-Hailuo-2.3 by default
When text-to-video (T2V) quota is insufficient: MiniMax-Hailuo-2.3-fast does not support text-to-video and cannot be used as a fallback. Inform the user directly that the quota is insufficient and suggest waiting for the quota to reset or switching to another video generation service (such as Kling)
When image-to-video (I2V) quota is insufficient: fall back to MiniMax-Hailuo-2.3-fast and inform the user "switched to the fast model for generation"
If the user is doing image-to-video and explicitly requests fast generation, use MiniMax-Hailuo-2.3-fast directly

Step 1: Submit a Text-to-Video Task

PORT=$(cat ${DESIRECORE_ROOT}/agent-service.port)
curl -sk -X POST "https://127.0.0.1:${PORT}/api/media-proxy" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "minimax",
    "serviceType": "video_gen",
    "endpoint": "/video_generation",
    "body": {
      "model": "MiniMax-Hailuo-2.3",
      "prompt": "Video content described by the user"
    },
    "responseType": "json"
  }'

Optional parameters (add to the body):

"duration": video length in seconds (6 or 10)
"resolution": "768P" or "1080P"

Extract data.task_id from the JSON response.

Step 1 (alternative): Image-to-Video

PORT=$(cat ${DESIRECORE_ROOT}/agent-service.port)
curl -sk -X POST "https://127.0.0.1:${PORT}/api/media-proxy" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "minimax",
    "serviceType": "video_gen",
    "endpoint": "/video_generation",
    "body": {
      "model": "MiniMax-Hailuo-2.3",
      "prompt": "Describe the dynamic changes of the scene in the image",
      "first_frame_image": "https://image-URL"
    },
    "responseType": "json"
  }'

Step 2: Poll the Task Status

Call once every 10 seconds until status is "Success" or "Fail". Replace TASK_ID with the task_id returned in Step 1.

PORT=$(cat ${DESIRECORE_ROOT}/agent-service.port)
TASK_ID="task_id returned from step 1"
curl -sk -X POST "https://127.0.0.1:${PORT}/api/media-proxy" \
  -H "Content-Type: application/json" \
  -d "{
    \"provider\": \"minimax\",
    \"serviceType\": \"video_gen\",
    \"endpoint\": \"/query/video_generation?task_id=${TASK_ID}\",
    \"method\": \"GET\",
    \"responseType\": \"json\"
  }"

Polling response (in progress):

{
  "success": true,
  "data": {
    "task_id": "task_xxx",
    "status": "Processing",
    "file_id": ""
  }
}

Polling response (completed):

{
  "success": true,
  "data": {
    "task_id": "task_xxx",
    "status": "Success",
    "file_id": "file_xxx"
  }
}

Step 3: Get the Video Download URL

Replace FILE_ID with the file_id from the completed response in Step 2.

PORT=$(cat ${DESIRECORE_ROOT}/agent-service.port)
FILE_ID="file_id returned from step 2"
curl -sk -X POST "https://127.0.0.1:${PORT}/api/media-proxy" \
  -H "Content-Type: application/json" \
  -d "{
    \"provider\": \"minimax\",
    \"serviceType\": \"video_gen\",
    \"endpoint\": \"/files/retrieve?file_id=${FILE_ID}\",
    \"method\": \"GET\",
    \"responseType\": \"json\"
  }"

Extract data.file.download_url from the response.

Step 4: Download and Upload to media-store

The download URL is valid for 24 hours; you must download immediately and save it to the local media-store.

PORT=$(cat ${DESIRECORE_ROOT}/agent-service.port)
VIDEO_URL="download_url obtained in step 3"
curl -sL "$VIDEO_URL" -o /tmp/minimax-video.mp4 && \
curl -sk -X POST "https://127.0.0.1:${PORT}/api/media/upload" \
  -F "file=@/tmp/minimax-video.mp4;type=video/mp4"

Extract the mediaId field from the JSON response.

Step 5: Display the Video Using the dc-media Protocol

Write Markdown image syntax directly in your reply (the frontend will automatically recognize the video extension and render a player):

![Video description](dc-media://replace-with-mediaId)

Error Handling

status: "Fail": video generation failed; explain to the user
success: false + error: "No matching provider found": No enabled MiniMax provider with video_gen service found
success: false + error: "API Key not configured": API Key has not been entered
Insufficient quota (errors related to statusCode: 429, insufficient_quota, balance): text-to-video cannot fall back (the Fast model does not support T2V); inform the user of insufficient quota; image-to-video can switch to MiniMax-Hailuo-2.3-fast and retry from Step 1
Polling exceeds 10 minutes without completion: inform the user that the task may have timed out

Notes

MiniMax video generation is asynchronous and typically takes 2–10 minutes
A polling interval of 10 seconds is recommended
The download URL is valid for 24 hours
If the user does not explicitly request otherwise, by default do not pass duration or resolution (use API defaults)

8.8 KiB Raw Blame History Unescape Escape