Test the version you intend to publish and record its steps and results before submitting for review.
The report shows that the submitted version has been run and its main behavior matches the listing. Environment details, input, and steps let reviewers reproduce results and identify account, dependency, or usage issues. Describe limitations and special permissions in advance.
Record actual results. Re-test fixes and update the evidence; keep unresolved issues visible.
For a meeting-action skill, record the installed version and test notes; request actions, owners, deadlines, and evidence; inspect the output table. The expected result is that every action has source evidence and unknown owners or deadlines remain unconfirmed. Fill in actual omissions or errors, not just Pass. Attach a result screenshot and redacted input where needed. This is a recording example, not a tested result.
Match the report to the uploaded version, check attachments, and retain known issues. Do not include passwords, API Keys, or full tokens; use the dedicated review access fields.
Plugins and connectors may explain why a report cannot be provided when the form offers that option. For skills, provide the self-test report required by the publishing form.
Why a report is required
The report shows that the submitted version has been run and its main behavior matches the listing. Environment details, input, and steps let reviewers reproduce results and identify account, dependency, or usage issues. Describe limitations and special permissions in advance.
What to include
| Item | Include |
|---|---|
| Extension | Name, type, and version matching the submission |
| Environment | Client, version, operating system, and runtime |
| Prerequisites | Account permissions, external services, dependencies, and test data |
| Steps | Input and actions in order |
| Results | Expected result, actual result, and pass, fail, or not-tested status |
| Evidence | Screenshots, demonstrations, or redacted logs |
| Known issues | Failures, untested scenarios, limits, and workarounds |
Focus by extension type
- Skills: activation, resource loading, required output, and at least one complete task. Include script runtime and results if applicable.
- Plugins: loading, included skills and tools, and a complete workflow. Record first-time service configuration and authorization.
- Connectors: connection, authorization, a representative tool call, and feedback for missing input, missing permissions, or service failure.
- App plugins: UI loading, interaction, and agreement between visible results and tool responses. Include a clear demonstration.