360 Secure SkillHub
360 安全技能中心

execute-media-generation

按团队已批准的生成包与显式 provider 能力路由提交图像、视频、音频生成请求,维护幂等键、作业状态、成本记录、重试与媒体落盘血缘;拒绝质量门未通过或路由不支持的请求,不确认的 provider 响应不会被当作成功媒体。

分类:创作
zhangzhangco
热度 0.00
最近更新 2026-11-01 17:19:50

安装

发给 Agent
帮我安装这个技能:npx secure-skills-cli add zhangzhangco/film-production-skills/execute-media-generation
兼容性
通用兼容
联网要求
需要联网
数据出网
必须出网
Metadata
name
execute-media-generation
description
Execute approved image, video, and audio generation requests through explicit provider capability profiles, while preserving idempotency, job state, cost records, media lineage, retries, and failure diagnostics. Use when a film-production workflow has a validated generation package that must be submitted, resumed, canceled, or reconciled with provider results.

Execute Media Generation

Submit approved requests without changing their narrative, identity, camera, or continuity meaning.

Inputs

Read the shared request envelope and validate payload against schemas/input.schema.json.

Require a generation package produced by compile-generation-prompts. Require an explicit provider route for every request that will be executed. A dry run may continue without credentials but must not report generated media.

Workflow

  1. Audit the upstream quality gate, request IDs, reference roles, and provider capability profiles.
  2. Refuse requests whose required gate failed or whose route does not support the requested mode.
  3. Derive one stable idempotency key for each provider submission.
  4. Estimate cost and enforce project concurrency, retry, and spend limits before submission.
  5. Submit requests without rewriting their semantic payload.
  6. Normalize provider states into queued, running, succeeded, failed, canceled, or blocked.
  7. Reconcile callbacks and polls without creating duplicate jobs.
  8. Persist successful media before reporting success, then attach checksums and lineage.
  9. Preserve useful completed jobs when another request fails or a targeted retry is requested.

Output rules

Return:

  • skill: execute-media-generation
  • data.jobs
  • data.media_assets
  • data.cost_summary
  • data.execution_gate

Every job must reference its compiled request, provider, attempt, and idempotency key. Every media asset must reference its producing job. Report actual provider errors as diagnostics; never turn an unconfirmed provider response into a successful media asset.

Boundaries

  • Do not redesign prompts or production decisions.
  • Do not expose provider credentials in results, logs, or diagnostics.
  • Do not retry content-policy failures automatically.
  • Do not exceed declared concurrency, retry, or cost limits.
  • Do not report temporary provider URLs as durable media unless they have been persisted.

Read references/field-guide.md for state transitions, retry classes, persistence, and cost rules.