Update to Skill Submission Pack Writer

{
  "name": "write-skill-submission-pack",
  "description": "Create evidence-bound submission materials for OpenAI Skills-only plugins from approved product facts and completed test evidence. Use when the user asks to write or prepare a Skills-only plugin listing, capabilities, starter prompts, five positive and three negative review cases, release notes, optional demo-video metadata, or a complete submission pack. Do not use for general marketing copy, product QA, invented evidence, MCP-backed submissions, portal operations, submission, or publication.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 256
    },
    {
      "relative_path": "assets/submission-pack-template.md",
      "size_in_bytes": 1942
    },
    {
      "relative_path": "references/submission-fields.md",
      "size_in_bytes": 6458
    },
    {
      "relative_path": "scripts/validate_submission_pack.py",
      "size_in_bytes": 6958
    }
  ],
  "skill_md_contents": "---\nname: write-skill-submission-pack\ndescription: Create evidence-bound submission materials for OpenAI Skills-only plugins from approved product facts and completed test evidence. Use when the user asks to write or prepare a Skills-only plugin listing, capabilities, starter prompts, five positive and three negative review cases, release notes, optional demo-video metadata, or a complete submission pack. Do not use for general marketing copy, product QA, invented evidence, MCP-backed submissions, portal operations, submission, or publication.\n---\n\n# Skill Submission Pack Writer\n\nTurn approved Skills-only product facts and test evidence into submission-ready copy without changing the product verdict or filling gaps by guesswork.\n\n## Start from the packaged rules\n\nRead [references/submission-fields.md](references/submission-fields.md) completely before drafting. Treat its date as the rule snapshot date, not a promise that OpenAI has not changed the portal. If the user supplies newer official requirements, preserve the conflict and ask for a rule update rather than silently mixing versions.\n\nUse [assets/submission-pack-template.md](assets/submission-pack-template.md) for a complete pack. Omit optional sections only when the template explicitly permits it.\n\n## Keep the boundary\n\n- Accept only a Skills-only submission. If the supplied product contains MCP, `.app.json`, `.mcp.json`, tool calls, authentication, live data, or controlled external actions, stop and route it to an MCP-backed production workflow.\n- Use supplied facts and evidence only. Never turn a proposed capability, author claim, planned test, or missing field into a confirmed fact.\n- Do not decide whether the product passed QA, will pass OpenAI review, or should be published. Preserve the supplied independent verdict and report only whether the writing pack is complete.\n- Do not upload, scan, submit, publish, sign attestations, or act in an external portal.\n- Treat YouTube title and description as optional Skills-only material unless the user supplies a current portal requirement that makes them mandatory.\n\n## Build the evidence ledger first\n\nClassify every supplied item as one of:\n\n1. `CONFIRMED_PRODUCT_FACT`: frozen name, user goal, behavior, boundary, version, or publisher fact.\n2. `PASSED_TEST_EVIDENCE`: executed case tied to the current package version and evidence reference.\n3. `PROPOSED_OR_UNVERIFIED`: draft, plan, author assertion, or evidence from another version.\n4. `MISSING`: required information not supplied.\n5. `CONTRADICTION`: two supplied sources disagree.\n\nRetain the source label or evidence reference beside every material claim. Do not assign a reference to material that was not received.\n\nPreserve any supplied usage marker such as `fixture`, `test only`, `draft only`, or `not for submission`. When any source is explicitly a test fixture or not for submission, set `artifact_use: TEST_ONLY_NOT_FOR_SUBMISSION`, put that warning in the first sentence and control block, and label every draft section as a test-only format preview. Do not call it portal-ready, submission-ready, paste-ready, or `可粘贴`. Otherwise use `artifact_use: SUBMISSION_DRAFT`.\n\n## Decide whether to draft\n\n- Ask one bundled question and stop when the product identity, Skills-only route, current version, or core user goal is unknown.\n- Ask for confirmed product facts, capabilities, boundaries, publisher facts, and executed evidence—not for final copy that this Skill is supposed to write. Do not require the user to prewrite a short description, long description, Skill description, starter prompts, case wording, or release-notes copy. Ask for confirmed release-change facts instead.\n- Produce `PARTIAL_MISSING_INPUT` with explicit blanks when required inputs or executed evidence are absent and the user is only asking for a draft. Missing evidence alone does not justify `BLOCKED_UNVERIFIED_EVIDENCE`.\n- Use `BLOCKED_INPUT_CONFLICT` when supplied sources disagree about the current identity, version, behavior, or evidence.\n- Use `BLOCKED_UNVERIFIED_EVIDENCE` only when the user asks you to state or imply that unexecuted tests, QA, scan, review, or publication results are real or passed.\n- Use `DECLINED_UNAUTHORIZED_ACTION` for upload, attestation, submission, publication, or other external execution requests.\n- Use `OUT_OF_SCOPE` for MCP-backed submission work, general marketing copy, product QA, or another adjacent workflow.\n- Never create a positive or negative review case from an unexecuted scenario. A proposed scenario may appear only in the gaps section.\n\n## Draft in this order\n\n1. State pack status: `DRAFT_COMPLETE_FROM_SUPPLIED_EVIDENCE`, `PARTIAL_MISSING_INPUT`, `BLOCKED_INPUT_CONFLICT`, `BLOCKED_UNVERIFIED_EVIDENCE`, `DECLINED_UNAUTHORIZED_ACTION`, or `OUT_OF_SCOPE`.\n2. Show the evidence ledger and rule-snapshot date.\n3. Draft the public listing from confirmed product facts.\n4. Draft up to 20 concise capabilities without adding features.\n5. Draft one to three distinct starter prompts. Keep each self-contained, realistic, and free of plugin `@mentions`.\n6. Populate exactly five positive and three negative review cases from executed current-version evidence. Include prompt, supplied fixture, expected behavior, expected result shape, actual-result summary, and evidence reference.\n7. Write release notes that describe only the current submitted version and supported change facts.\n8. Add optional YouTube title and description only when requested or explicitly required by supplied current rules.\n9. List missing inputs, contradictions, version drift, and owner or portal actions separately.\n10. Validate field lengths and case counts before presenting a complete pack.\n\nWhen the user requests a bounded follow-up edit to an existing pack, freeze every unrequested field. Return only the requested before/after blocks plus `unchanged_fields_preserved: YES` and the unchanged pack status. Do not silently rewrite evidence, cases, release notes, identity, version, or portal state.\n\n## Validate deterministically\n\nWhen producing a complete pack as files, also create `submission-pack.json` with the keys used by the template and run:\n\n```bash\npython3 scripts/validate_submission_pack.py submission-pack.json\n```\n\nUse the script from this Skill directory. Fix writing errors that are supported by evidence. If a failure requires invented facts, return `PARTIAL_MISSING_INPUT`, `BLOCKED_INPUT_CONFLICT`, or `BLOCKED_UNVERIFIED_EVIDENCE` as appropriate. Never edit the validator to make a failing pack pass.\n\n## Present the result\n\nLead with one sentence: what is ready and what remains blocked. Keep platform-ready copy separate from evidence notes so the user can paste fields without carrying internal commentary into the portal.\n\nFor every complete pack, include:\n\n- the Skills-only submission type and package version;\n- the embedded-rule snapshot date;\n- the deterministic validation result;\n- the independent product verdict exactly as supplied, without upgrading it;\n- a clear statement that portal scan, review, submission, and publication were not performed.\n\nWithin blocked sections, repeat the applicable defined pack status. Do not introduce a looser status such as `BLOCKED_INPUT`.\n"
}