菜单
Validates JSON or tool-call model outputs without repair, separating parse, schema, supplied-identifier, semantic, replay, and safety failures. Use for first-attempt benchmarks, teacher-label pipelines, and bounded model tool selection.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/bastos/skills --skill validate-structured-model-output命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | validate-structured-model-output |
| description | Validates JSON or tool-call model outputs without repair, separating parse, schema, supplied-identifier, semantic, replay, and safety failures. Use for first-attempt benchmarks, teacher-label pipelines, and bounded model tool selection. |
Treat model output as untrusted input. Preserve raw bytes and validate a normalized copy through ordered gates.
Keep failure categories separate. A parse failure is not an abstention, and a legal identifier is not proof of a safe or useful result.
Use the bundled validator when each row contains supplied, ranked, and optional alternative IDs:
python scripts/validate_jsonl_outputs.py results.jsonl \
--supplied-field request.planIDs \
--ranked-field response.rankedPlanIDs \
--alternative-field response.alternativePlanIDs \
--max-ranked 3 --output validation-report.json
It checks duplicate IDs within arrays, overlap between ranked and alternatives, unknown IDs, rank length, and alternatives without a ranked selection. Add project validators after this generic layer.
For first-attempt acceptance, generate once and validate without repair, remediation, or deterministic fallback. Test production remediation separately. Persist raw output, normalized output, every gate result, timing, prompt/config revision, and validator revision so failures remain auditable.
Writes and revises clear, precise, accessible technical content for any medium. Use for manuals, wikis, README files, developer and user documentation, tutorials, references, specifications, RFCs, feature requests, issues, commit messages, code comments, review comments, pull request messages, release notes, runbooks, decision records, status updates, email, Slack, and other workplace or agent-facing communication.
Audits and designs lean, coherent context across system prompts, persistent instructions, repository guidance, skills, tool descriptions, memory, and references. Use for context engineering; creating, reviewing, simplifying, or reorganizing agent context; resolving conflicting, duplicated, bloated, stale, or misplaced guidance; designing progressive disclosure; or deciding where shared information should live.
Orchestrates and ships a milestone, release, issue set, or multi-workstream engineering goal through one manager and bounded parallel workers. Use when the user asks to manage a milestone, build a dependency graph, execute independent issues in parallel, coordinate threads, sessions, subagents, or worktrees, recover a stopped delivery, or invokes /gogopowermanager.