Individual skill

scenario-report

Use when a Scenario user wants to report a bug or request a change, on the public tracker at github.com/scenario-labs/skills or by email to support@scenario.com: turning a failed generation, MCP tool error, or unclear skill into a reproducible report, collecting trace ids with diagnostics_run, stripping keys, signed asset URLs, and personal data, asking before sharing a team or project id, or building a prefilled issue URL. Keywords: file an issue, feature request, feedback.

skills/scenario-report/SKILL.md

Read pinned source

Source commit f29bf06ab89088695ed3431ac99d20a090441a2f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,594
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Reporting Scenario bugs and change requests

## Overview

Public tracker: `https://github.com/scenario-labs/skills/issues`, forms `bug.yml` and
`change-request.yml`. Offer `support@scenario.com` as the private alternative, and let the user
pick.

Two constraints. A public issue is permanent, so redact first and post only after the user approves
the exact text. The reader has no access to the user's account, so the report must carry everything
needed to reproduce from outside.

Connection and the core generation loop: see the `scenario` skill in this repo. If a sibling skill
named here is missing from your available skills, load it with `skill_get` (Scenario MCP) or ask the
Back to top