ワンクリックで
trace-mechanism-review
Review exact planner/scenario/seed/episode traces and videos without overgeneralizing from qualitative samples.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Review exact planner/scenario/seed/episode traces and videos without overgeneralizing from qualitative samples.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Open a conservative Robot SF PR with scope verification, freshness checks, and artifact discipline.
Use for an autonomous Robot SF issue-to-PR loop that selects eligible GitHub issues, implements one scoped issue at a time, validates, pushes, and opens PRs.
Guarded PR merger; merges merge-ready PRs after verifying label, CI status, branch protection, and preflight checks.
Use for an autonomous Robot SF PR review loop that fixes scoped review gaps, validates proof, resolves review threads, and applies merge-ready; not for merging.
Autonomous issue-to-PR workflow from next eligible issue to ready PR with consistent metadata handling.
Continuous goal autopilot; orchestrates implement, review, merge, and discover cycles with preflight validation and delegation failure recovery.
| name | trace-mechanism-review |
| description | Review exact planner/scenario/seed/episode traces and videos without overgeneralizing from qualitative samples. |
| category | campaign-analysis |
| kind | analysis |
| phase | analysis |
| requires_write | true |
| requires_slurm | false |
| requires_benchmark_artifacts | true |
| delegates_to | ["artifact-provenance","evidence-synthesis"] |
| output_schema | trace_mechanism_summary.v1 |
Use this skill for the campaign lane named by the title when you need canonical command surfaces, expected artifacts, row-status handling, and conservative claim boundaries.
Start with rendered trace/video artifacts, exact planner/scenario/seed/episode identifiers. Prefer config-first commands and existing validation launch-packet scripts when available.
supported | contradicted | unresolved and no population-level inference from tiny samples.mechanism_activation from observed telemetry: activation status, activation count,
command-source change, outcome change, and likely failure reason. Use unknown when the trace
or report does not preserve the needed signal.benchmark-row-status when benchmark rows exist.artifact-provenance.evidence-synthesis.Use the output_schema declared in frontmatter. The mechanism_activation block is:
mechanism_activation:
activated: true | false | unknown
activation_count: integer | unknown
changed_command_source: true | false | unknown
changed_outcome: true | false | unknown
likely_failure_reason: string