跳到正文
cccskills
免费在 GitHub 公开

fixed-view-visual-benchmark

Use when a visual needs repeatable fixed-view rendering and independent rubric scoring. Not for free-form visual review or subjective critique.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(2)

  • SKILL.md4.1 KB
  • agents/openai.yaml168 B

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Fixed-view visual benchmark

Contract

FieldBound contract
TriggerA visual needs repeatable fixed-view rendering and independent rubric scoring.
AuthorityHuman-gated: asks for capture consent before rendering; otherwise reversible local: writes only named local artifacts; rollback is undo. No remote mutation.
Side effectFixed-view visual benchmark: renders and scores the fixed view against the frozen rubric.
DoneThe saved render clears the frozen rubric threshold.
StopStalled; render blocked; budget exhausted. Bound: fixed view rig, rubric threshold, render budget.

Inputs

  • Fixed view rig (required): camera position and orientation, scene definition, render settings (resolution, samples, lighting, post-processing). All parameters that affect the rendered output must be named and frozen.
  • Frozen rubric threshold (required): the minimum aggregate score that defines a passing render, plus the rubric dimensions and their weights.
  • Render budget (required): the maximum render attempts or time allowed, declared before work begins.

Procedure

  1. Bind the fixed view rig, rubric threshold, and render budget. Freeze all three before any mutation. Done when: the rig, threshold, and budget are named and frozen.
  2. Capture consent. Ask for and record explicit human consent before rendering. Done when: consent is recorded.
  3. Render the fixed view through a specified rendering interface with reproducibility controls. The interface must accept the frozen rig parameters and produce a deterministic output: same camera, same scene, same settings, same result. Record the interface name, version, and the exact parameter set used. If the interface is non-deterministic (stochastic sampling, temporal effects), declare the seed or averaging strategy that makes repeated renders comparable. Done when: a render is produced from the frozen rig with the interface and parameters recorded.
  4. Score the render against the frozen rubric independently. The rubric defines scoring dimensions (for example: composition, lighting accuracy, material fidelity, geometric correctness), each with a weight summing to 1.0 and a 0–10 scale per dimension. The aggregate score is the weighted sum. Score each dimension against the rubric criteria, not against the previous render. Record per-dimension scores, the aggregate, and the threshold. Done when: the rubric score is recorded with per-dimension breakdown.
  5. Stop at success (aggregate score clears the threshold), any non-success terminal, or the bound. Done when: a terminal class is reached and named.
  6. Persist the run record to .outline/loops/fixed-view-visual-benchmark/<run_id>/ when durable. Emit receipt.json before return. Done when: the receipt is written with the saved render path, per-dimension scores, aggregate, threshold, and terminal class.

Failure and recovery

  • Stagnation: repeated renders do not improve the score. Terminal stalled; report the score plateau and the renders attempted.
  • Render blocked: the rig cannot produce a render through the specified interface. Terminal blocked; report the blocking condition.
  • Budget exhausted: the render budget is spent before the threshold is cleared. Terminal capped; report the best score achieved. Budget exhaustion is never success unless it is the predeclared success predicate.
  • Non-deterministic output without declared seed: if repeated renders with the same parameters produce different scores and no seed or averaging strategy was declared, the renders are not comparable. Declare the strategy before scoring; do not compare incomparable renders.
  • Partial result: emit the best render and score obtained; never present a sub-threshold render as clearing the rubric.

Output

A terminal classification (success, capped, stalled, or blocked) plus the saved render, its per-dimension rubric scores, aggregate score, threshold, and the run receipt.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Use when explaining System V AMD64, ARM AAPCS, RISC-V psABI, stack frames, variadic calls, or FFI register rules. Not for the Rust FFI binding layer: use rust-ffi.

中文简介正在准备中。当前显示原文说明。

OutlineDriven/odin-claude-plugin382026年9月29日 更新

Use when configuring ADC sampling time, DMA-driven ADC, calibration, or DAC channel setup on bare-metal MCUs. Not for the DMA stream itself: use dma-baremetal.

中文简介正在准备中。当前显示原文说明。

OutlineDriven/odin-claude-plugin382026年9月29日 更新

af-xdp

免费

Use when creating AF_XDP sockets, configuring UMEM and XSK rings, writing an XDP redirect program, or choosing copy versus zero-copy mode. Not for full kernel bypass: use dpdk.

中文简介正在准备中。当前显示原文说明。

OutlineDriven/odin-claude-plugin382026年9月29日 更新

Use when a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.

中文简介正在准备中。当前显示原文说明。

OutlineDriven/odin-claude-plugin382026年9月29日 更新

Use when a redacted, trimmed agent transcript must be appended to a GitHub PR or issue body, with human approval and preview. Not for automated or model-initiated insertion.

中文简介正在准备中。当前显示原文说明。

OutlineDriven/odin-claude-plugin382026年9月29日 更新

agents-md

免费

Use when a repo needs agent setup, AGENTS.md added or made lean, CLAUDE.md audited, or agent instructions scored or pruned. Not for remote, credential, publish, deploy, or irreversible changes.

中文简介正在准备中。当前显示原文说明。

OutlineDriven/odin-claude-plugin382026年9月29日 更新

查看 OutlineDriven 的全部技能

报告此技能的问题