确定性世界演化视频生成

SKILL前端设计

原名 SPL新一代视频生成服务,世界自己演,影片能验真。 · 标识 second-reality-video-pro

前端设计 未标注权限 许可证不明确
安装这个技能

用世界按自身规则演化的方式生成视频,摄像机只决定取景,同一种子与机位结果一致,减少反复抽卡产生的废片,适合需要稳定成片的视频制作。

一句话选型结论

按资料字段整理

确定性世界演化视频生成是前端设计类的 Agent Skill,安装方式未标注,权限级别未标注,许可证不明确,有可直接复制的安装命令。技能本质是给模型读的说明书,效果取决于模型与客户端;装完先用一个小任务验证,再放进正式流程。

分类前端设计 安装方式未标注 权限级别未标注权限 许可证许可证不明确
累计安装 未标注 本周 未标注
GitHub 星标 未标注 仓库 未标注
下载量 未标注 技能市场下载数
权限级别 未标注权限 安装前请确认风险范围
许可证 许可证不明确 未说明

安装

未标注
在支持 Skills 的客户端里执行,装完问一句「你有哪些技能」验证
skillhub install user_2cbe9405/second-reality-video
  1. 1
    确认客户端支持

    确认你的客户端支持 Skills(Claude、Codex、Cursor 等),并升级到较新的版本。

  2. 2
    拿到技能文件

    执行上面的命令安装;也可以把仓库里的 SKILL.md 手动放进客户端的 skills 目录。

  3. 3
    刷新技能列表

    重新打开客户端,或刷新技能列表,让新放进来的技能被加载。

  4. 4
    验证是否生效

    问一句「你有哪些技能」,确认列表里出现它,再拿一个小任务试跑。

技能档案

前端设计
字段来自技能仓库与公开索引,中文说明由本站标注
作者 / 维护方user_2cbe9405仓库 未标注 · 版本 未标注
宿主客户端未标注技能可被这些客户端加载
安装方式未标注安装包 community
权限级别未标注权限安装前请确认风险范围
许可证未说明许可证不明确,商用前请自行确认条款
仓库可用性available技能仓库当前是否可访问
最近核验2026-11-06上游最后核验时间 · 数据更新 2026-11-06
正文体量11.5 KBSKILL.md 原文大小,越大说明说明书写得越细

能做什么

0 项能力
上游给出的能力概览与适用场景
生成可控剧情短片复现同一镜头画面减少废片反复重生成

典型使用场景

3 类
按分类整理的常见用法,具体以 SKILL.md 为准
出页面与组件

按描述生成页面结构和组件草稿。

调整样式与布局

改间距、配色与响应式布局。

生成设计说明

把设计稿整理成开发能接的说明。

选择建议

装之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有可直接复制的安装命令,不用自己翻文档找入口。

先想清楚的地方

  • 没有标注权限级别,实际能做什么要装好后确认。
  • 许可证不明确,商用或二次分发前先到仓库确认条款。
  • 没有做站内核验,内容以作者仓库为准。
  • 技能只是说明书,实际效果取决于模型与客户端,装完先用小任务试一遍。

更适合

  • 需要在前端设计场景里给模型补一套做法的人。
  • 愿意先读一遍 SKILL.md、确认它会让模型做什么的人。

不太适合

  • 对许可证要求很严、必须明确可商用的人。
  • 只想装完就自动变强、不打算看说明书的人。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
技能权限级别安装方式累计安装宿主客户端安装命令
确定性世界演化视频生成当前 未标注权限 未标注 未标注 未标注 有
前端设计 只读 GitHub 仓库 882.3 万 Codex、Claude、Cursor 有
Vercel 组合模式 联网访问 GitHub 仓库 385.9 万 Codex、Claude、Cursor 有
Vercel React native skills 前端 只读 GitHub 仓库 246.9 万 Codex、Claude、Cursor 有
adapt 搜索 浏览器控制 GitHub 仓库 202.7 万 Codex、Claude、Cursor 有
使用我的浏览器 浏览器控制 GitHub 仓库 184.8 万 Codex、Claude、Cursor 有

SKILL.md 全文

11.5 KB
模型实际读到的说明书原文,来自技能仓库

Second Reality Video · Reproducible World Film

> A deterministic video pipeline. Persistent world state becomes film; the camera picks framing, never story:
> frame = render(state, shot). Same seed and shots give byte-identical pixels anyone can recompute.

This skill talks to the hosted Second Reality Video render service. It is the client half of a
pay-per-render product: the world simulation and the deterministic renderer live on the service side,
so the package you install contains no engine source — only the orchestration script, the API
contract and the operating notes.

What it does

  1. Sends a render request (world id, genesis seed, agent count, tick range, shot plan, framing).
  2. Receives HTTP 402 with a Payment-Needed bill when the order is not paid yet.
  3. Hands the bill to the official Alipay payment capability — the script never touches payment
    keys and never signs anything itself.
  4. Retries the same request on the same order with the Payment-Proof credential.
  5. Polls the job and downloads: world.mp4, hashes.txt (per-frame sha256), frames.jsonl,
    identity_assets.json, manifest.json (signed reproducibility anchor) and audit_report.txt
    (per-dimension audit verdicts).

Pricing

Charged per successful render, via Alipay AI pay-per-use (按量付费). This price must be identical in all three places: the Alipay service registration, the

server-side bill amount, and the price shown on the SkillHub listing.

Tier Covers Price (CNY / call) Alipay service_id
standard ≤60 s, ≤1920×1080, ≤10 agents 10.00 API_7D60C7FE970E4DA4

Single tier, single price: one Alipay service registration (API_7D60C7FE970E4DA4, 10.00 CNY per
call). Sandbox runs use api_mock_service_id and 0.01 CNY per call. The authoritative value always
comes from the service's /api/v1/pricing response.

Paid call flow

probe    → POST /api/v1/render                → 402 + Payment-Needed (bill, base64url)
pay      → hand bill to official alipay-bot   → user pays
complete → same request + Payment-Proof       → 200 + content + Payment-Validation
         → GET /api/v1/render/{order}/artifacts/{name} → film + signed manifest + audit

Rules this client follows, and you should keep following:

  • Reuse the order. After payment, replay the identical request body on the identical order.
    Never rebuild the request with different parameters — that creates a second bill.
  • Never pay twice. If the payment state is unknown, run status (server-side order lookup)
    before doing anything else.
  • No receipt. On the success path the result is the receipt; do not append a separate
    "payment successful" message.
  • The script is not the payer. Payment goes through the official capability; the script only
    transports the bill and the credential.

Dependencies

Package Side Purpose
@alipay/alipay-aipay seller server-side Alipay pay-per-use integration (402 bills, verification, fulfillment) — not bundled here
@alipay/agent-payment buyer lets the agent pay through alipay-payment-skill / alipay-bot

Install the buyer-side capability once:

npx -y @alipay/agent-payment@latest install

The client script itself has no runtime npm dependency (Node ≥ 18, global fetch only).

Input parameters

Flag Default Meaning
--api-base $SRV_API_BASE base URL of the render service
--world-id sr-video-demo world identifier (part of the reproducibility key)
--seed 42 genesis seed
--agents 10 number of souls in the world
--ticks 0-599 tick range; 10 ticks = 1 s of film
--resolution 1280x720 output resolution
--fps 30 must be an integer multiple of 10 (the engine's fixed time base)
--shot demo shot-plan preset name
--samples 3 how many still frames are dumped for eyeball review
--service-id auto force a pricing tier
--state-dir .state where the session state (bill + original request) is kept
--session-id default session key; the state file is .state/<session-id>.json
--payment-proof — credential returned by the official payment capability
--out-dir ./out where artifacts are written

Outputs

File Contents
world.mp4 the H.264 film
hashes.txt one sha256 per frame, in order — the pixel-layer reproduction anchor
frames.jsonl per-frame backing record (digest, tick, sub-frame)
identity_assets.json soul_hash → appearance asset evidence (identity constancy)
manifest.json Ed25519-signed RenderManifest: world params, content digests, renderer provenance, audit verdict
audit_report.txt 25-dimension constitutional audit, one verdict per dimension

What is guaranteed

Layer Anchor Nature
State content_digest sequence deterministic, byte-verifiable
Pixels (R1) per-frame sha256 deterministic, byte-verifiable
Container world.mp4 sha256 corroborative only — not stable across ffmpeg versions
Pixels (R2) weights / sampling seed / hardware not implemented (Phase 2)

The container hash is not a reproducibility claim: H.264 output is not bit-stable across ffmpeg
builds. The frame hashes are the anchor. See references/determinism.md.

API contract

Method Path Purpose
GET /health liveness
GET /api/v1/pricing tiers, limits and display prices
POST /api/v1/render the resource endpoint (402 → pay → retry with Payment-Proof → 200)
GET /api/v1/render/{out_trade_no}/artifacts/{name} download one delivered artifact

Request body (all fields optional except the tick range):

{
  "world_id": "sr-video-demo",
  "genesis_seed": 42,
  "agent_count": 10,
  "tick_from": 0,
  "tick_to": 599,
  "framing": { "resolution": [1280, 720], "fps": 30 },
  "shot": { "preset": "demo" },
  "samples": 3,
  "tier": "R1"
}

The unpaid response is HTTP 402 with a Payment-Needed header (base64url of the bill JSON, protocol +
method two layers). The paid response is HTTP 200 with the resource content and a
Payment-Validation header proving resource ownership. Full details: references/api.md.

Running it

# 1) 拿账单(未付款会返回退出码 2,并落盘会话状态)
node scripts/second-reality-video-paid.mjs probe \
  --api-base https://api.example.com --world-id sr-video-demo \
  --seed 42 --agents 10 --ticks 0-599 --resolution 1280x720 --fps 30 \
  --shot demo --state-dir .state --session-id demo-001

# 2) 把账单交给官方支付能力(脚本只输出付款请求,不自己付)
node scripts/second-reality-video-paid.mjs pay --state-dir .state --session-id demo-001

# 3) 付款后复用同一请求 + Payment-Proof 取回产物
node scripts/second-reality-video-paid.mjs complete \
  --state-dir .state --session-id demo-001 \
  --payment-proof '<官方支付返回的凭证>' --out-dir ./out

# 状态不明时先查单,不要重新下单
node scripts/second-reality-video-paid.mjs status --state-dir .state --session-id demo-001

One-shot equivalent:

node scripts/second-reality-video.mjs --api-base https://api.example.com \
  --ticks 0-599 --state-dir .state --session-id demo-001 \
  --payment-proof '<凭证>' --out-dir ./out

Install / local load / package

# 安装到本地 skills 目录
skillhub install second-reality-video

# 本地加载(开发态):把本目录放进 skills 根目录后由 Agent 加载
# 打包上传:目录或 zip 均可,.skillhubignore 已排除 .state/ .env node_modules/
skillhub publish . --version 1.0.0

Runtime requirements: Node ≥ 18, network access to the service base URL, and the buyer-side Alipay
payment capability installed (npx -y @alipay/agent-payment@latest install).

Acceptance matrix

Run against the service in sandbox mode before going live. The client half has been exercised
end-to-end against the bundled protocol simulator (402 → credential → 200 + Payment-Validation →
artifacts with matching sha256); the service half still needs a green sandbox run on the Alipay
side before publishing.

# Case Expected
1 Unpaid request HTTP 402, Payment-Needed header present, exit code 2
2 Payment in progress no new order, no new bill, same out_trade_no
3 Paid retry HTTP 200, content with artifacts, Payment-Validation valid, artifacts downloadable with matching sha256
4 Invalid / expired proof HTTP 402, no artifacts delivered, order still open for a new payment
5 Same-order retry identical out_trade_no, no second charge, no second delivery

Files

  • payment/gateway.py — the A2M gateway: 402 Payment-Needed bill, payment.verify, fulfillment.confirm, SQLite order store
  • payment/service.py — the business hook: turns a paid request into the rendered resource
  • payment/requirements.txt — alipay-sdk-python, pycryptodome
  • scripts/second-reality-video-paid.mjs — probe / pay / complete / status / pricing
  • scripts/second-reality-video.mjs — one-shot wrapper around the three stages
  • references/api.md — full API contract, bill and proof structures, error codes
  • references/shot-files.md — shot-plan schema and the hard constraints
  • references/determinism.md — what is byte-verifiable, what is only corroborative
  • references/licensing.md — dual-track licence terms
  • package.json — entry points and engine requirement (Node ≥ 18)
  • PACKING.md — the packaging rules: which entries the upload may contain, and what must never
    ship (.state/, .env, node_modules/, logs). SkillHub rejects dotfiles, so the exclusion
    list lives in a normal file.

Notes

  • The engine is not in this package on purpose. If you need a self-hosted instance, that is a
    separate commercial engagement (see references/licensing.md).
  • Your session state (.state/<id>.json) contains the bill and the original request. It is written
    with 0600 permissions on POSIX systems and is excluded from the uploaded package.
  • You are responsible for how the rendered film is used. This skill renders simulated worlds; it
    does not verify real-world claims, and it is not a substitute for editorial or legal review.

常见问题

5 问
答案由本站依据条目字段整理
确定性世界演化视频生成怎么安装?

在支持 Skills 的客户端里执行:skillhub install user_2cbe9405/second-reality-video。安装方式为未标注。装完刷新技能列表或重开客户端。

确定性世界演化视频生成支持哪些客户端?

资料没有标注宿主客户端,但只要客户端支持 Skills(Claude、Codex、Cursor 等),一般都能加载。

确定性世界演化视频生成权限高吗,安全吗?

权限级别为未标注权限。安装前先看它会读取或写入哪些内容。

确定性世界演化视频生成收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于技能本身和所用的模型或客户端,正式使用前按作者说明确认。

确定性世界演化视频生成用什么许可证?

许可证标注为 未说明(许可证不明确)。商用或二次分发前请到仓库确认条款原文。

热门专题

按场景挑技能
全部专题 →

技能内容以作者仓库为准;分类、权限级别与许可证状态的中文说明为中文整理,最近核验 2026-11-06。