docs: prepare OpenAI plugin submission artifacts - #5
Merged
Merged
Conversation
The PR appears safe to merge; no outstanding correctness, security, or repository-rule failures remain.
|
ravern
dismissed stale reviews from greptile-apps-staging[bot] and greptile-apps[bot]
via
September 10, 2026 01:24
94e7ba1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepare the reusable OpenAI directory submission materials: app copy, explicit annotation justifications for all 21 MCP tools, five positive cases, and three negative cases. Expected outputs are acceptance criteria, not claims that the cases have already run.
Document the upload and verification steps, and correct the README's missing account tools and stale claims about comment resolution, comment fields, and evidence bodies. Extend the existing MCP check to validate the submission's tool names, annotations, justifications, and case counts.
Validation: README and submission names match live
tools/list; all submission hint values match the proposed server metadata; the existing workflow's Python validation passes; the plugin archive contains its manifest, both skills, and bundled CLI. No credentials or internal deployment details are included.Before submitting, the production server must advertise these annotations and pass a fresh scan and domain verification. Skill ingestion, isolated-account test execution, demo recording, and remaining listing fields still need portal verification; see SUBMISSION.md.