· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Beike Yan v0.2.0
Write submission materials
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Turn these approved Skills-only product facts and test results into a submission pack.
Developer declarations; not independently tested. Listing last checked Nov 20, 2026. Package observed Nov 20, 2026.
From the marketplace listing
Turn approved Skills-only product facts and current-version test evidence into listing copy, capabilities, starter prompts, five positive and three negative review cases, and release notes. Missing or conflicting evidence remains explicit. The plugin does not judge product quality, operate the OpenAI portal, submit, publish, or guarantee approval.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- 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. --- # Skill Submission Pack Writer Turn approved Skills-only product facts and test evidence into submission-ready copy without changing the product verdict or filling gaps by guesswork. ## Start from the packaged rules Read [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. Use [assets/submission-pack-template.md](assets/submission-pack-template.md) for a complete pack. Omit optional sections only when the template explicitly permits it. ## Keep the boundary - 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. - Use supplied facts and evidence only. Never turn a proposed capability, author claim, planned test, or missing field into a confirmed fact. - 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. - Do not upload, scan, submit, publish, sign attestations, or act in an external portal. - Treat YouTube title and description as optional Skills-only material unless the user supplies a current portal requirement that makes them mandatory. ## Build the evidence ledger first Classify every supplied item as one of: 1. `CONFIRMED_PRODUCT_FACT`: frozen name, user goal, behavior, boundary, version, or publisher fact. 2. `PASSED_TEST_EVIDENCE`: executed case tied to the current package version and evidence reference. 3. `PROPOSED_OR_UNVERIFIED`: draft, plan, author assertion, or evidence from another version. 4. `MISSING`: required information not supplied. 5. `CONTRADICTION`: two supplied sources disagree. Retain the source label or evidence reference beside every material claim. Do not assign a reference to material that was not received. Preserve 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`. ## Decide whether to draft - Ask one bundled question and stop when the product identity, Skills-only route, current version, or core user goal is unknown. - 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. - 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`. - Use `BLOCKED_INPUT_CONFLICT` when supplied sources disagree about the current identity, ver
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 4 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 20, 2026.
plugins_6a7ab7ab6a84819196a8505377547eed
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.