New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Scenario Report

by scenario-labs in scenario-labs/skills

A skill your agent uses 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…

MITAuto-check passedAgent Workflows

Install Scenario Report

skills CLI
$ npx skills add scenario-labs/skills --skill scenario-report -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install scenario-labs/skills scenario-report --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scenario-report .claude/skills/scenario-report && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
scenario-report
GitHub stars
946
Token cost
~1.5k tokens
SKILL.md length
744 words
Files
1
Skills in repo
146
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses 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…

  • Works in 4 steps: diagnostics_run in the failing session,… → Re-run the failing call once: arguments,… → Draft. Title: jobs_wait keeps returning… → …
  • A Scenario user wants to report a bug
  • SKILL.md covers Overview, Quick reference, Redact before drafting and Make it reproducible, plus 3 more sections
  • Calls npx

What it does

Scenario Report is an agent skill from scenario-labs/skills. 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 diagnosticsrun, 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.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering MCP servers. It works with GitHub. The repository describes itself as: Get production-ready images, video, audio, and 3D from any AI agent: skills that pick the right model, price before spending, and keep characters and brands consistent through… The licence is MIT.

When your agent uses it

  • A Scenario user wants to report a bug
  • Request a change
  • On the public tracker at github.com/scenario-labs/skills
  • By email to support@scenario.com: turning a failed generation

Example prompts

  • “/scenario-report”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. diagnostics_run in the failing session, keeping only the fields listed above and the trace ids.
  2. Re-run the failing call once: arguments, verbatim response, UTC time. Check with search whether the upscaler is public, so the reader can…
  3. Draft. Title: jobs_wait keeps returning the same texture upscale job in pending_job_ids for 20 minutes. Steps: the model_schema_get…
  4. Show the user the full text, and post only on a yes.

What it can do on your machine

Read from SKILL.md and the folder at commit f6f8ab7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Scenario Report loads about 1.5k tokens when it runs. Until then it costs about 124 tokens; SKILL.md has 744 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~124
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from scenario-labs/skills at commit f6f8ab7, republished under its MIT licence (© scenario-labs). 744 words, ~1,486 tokens.

Download SKILL.mdSave it as .claude/skills/scenario-report/SKILL.md (or your agent's skills folder).
name
scenario-report
description
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.
license
MIT

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, ask the user to install it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and flag the gap.

Account, billing, credit, quota, sign-in, and security problems never go in a public issue: send those to support@scenario.com or in-app support at app.scenario.com.

Quick reference

StepDo
Classifybug or change request, one problem each
Gatherfailing call, verbatim error, diagnostics_run from that session
Redactstrip identity and secrets; ask before any team or project id
Dedupesearch open and closed issues, comment on a match
Draftfill every field, label guesses as guesses
Approveshow the final text, post only on a yes
PostGitHub tool, prefilled URL, or email

Redact before drafting

Never include API keys or tokens, signed URLs from asset_download (the URL is a credential), account emails or names, local paths containing a username, or unreleased art, prompts, and model names the user has not agreed to publish.

Team and project ids identify the account, so strip them by default. Ask for one only when it changes the diagnosis (a Forbidden or scope error, a model only one team can see): quote the id you would post, and treat anything short of a yes as no. Email is the better home for it.

diagnostics_run is the best evidence and the biggest leak: self_test.detail can enumerate every team and project the user belongs to, and tenant can encode their account. Copy only version, endpoint, auth_type, self_test.layer, self_test.latencyMs, generated_at, and the ids under confirmed_trace_ids and candidate_trace_ids. Nothing else from that report.

Job, asset, and model ids match the report to a server-side request: include them with the user's agreement. Signed download URLs, never.

Make it reproducible

Name the model id and whether search finds it with public=true, the exact parameters sent to model_run, the verbatim error, the UTC timestamp, and at least one trace id. Substitute a short public prompt for a confidential one and say so. Say when a model is team-private: the reader reproduces against a public equivalent.

Show full SKILL.md (321 more words)Show less

Worked example: a texture upscale that never finishes

  1. diagnostics_run in the failing session, keeping only the fields listed above and the trace ids.
  2. Re-run the failing call once: arguments, verbatim response, UTC time. Check with search whether the upscaler is public, so the reader can run it too, then search the tracker, open and closed, for jobs_wait pending.
  3. Draft. Title: jobs_wait keeps returning the same texture upscale job in pending_job_ids for 20 minutes. Steps: the model_schema_get, model_run, and repeated jobs_wait calls with their arguments. Expected: the job completes or fails. Actual: status stays in_progress, pending_job_ids unchanged. Evidence: job id, trace ids, timestamp.
  4. Show the user the full text, and post only on a yes.

Posting

  • With GitHub tooling: search repo:scenario-labs/skills for duplicates, then create the issue with the label bug or enhancement, mirroring the form headings in the body.
  • Browser only: build https://github.com/scenario-labs/skills/issues/new?template=bug.yml&summary=...&repro=..., percent-encoding each value. Parameter names are the form field ids: summary, area, repro, expected, actual, evidence, env, frequency; change requests switch to template=change-request.yml and use problem, area, today, proposal, impact (a param matching no field id on the selected form is dropped silently). The user ticks the confirmation boxes and submits. Past about 8000 characters the URL returns 414: drop evidence.
  • By email: support@scenario.com, subject [bug] <title> or [change request] <title>, body carrying those same fields as labeled lines. Whatever was withheld from a public issue (team id, project id, account email) travels safely here.

Common mistakes

  • Pasting the whole diagnostics_run output, which leaks the team and project list.
  • Publishing a team or project id nobody asked for, or asking for one the diagnosis does not need.
  • A title like "generation is broken": name the surface, the symptom, and the condition.
  • Three problems in one issue: each needs its own reproduction and its own close.
  • Reporting the hypothesis ("the API is down") instead of the observation. Observation first, hypothesis last and marked as one.

© scenario-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/scenario-report of scenario-labs/skills.

Open the folder on GitHubat commit f6f8ab7

Compare with similar skills

Scenario Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Scenario Report compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scenario Report this skillscenario-labs/skills946—~1.5kAutomated safety check: PassMIT
Skill Seekers Builderyusufkaraaslan/Skill_Seekers15k—~760Automated safety check: PassMIT
MCP Apps Builderawslabs/cli-agent-orchestrator1.4k—~1.7kAutomated safety check: PassApache-2.0
Releasejgravelle/jcodemunch-mcp2.8k—~6.5kAutomated safety check: PassCustom licence
Open PRArcadeAI/arcade-mcp1k—~2.9kAutomated safety check: PassMIT
Triage Security Advisoriesactivepieces/activepieces25k—~3.9kAutomated safety check: PassCustom licence

Similar skills

  • Skill Seekers Builder

    yusufkaraaslan/Skill_Seekers

    Detects the type of a knowledge source and uses the Skill Seekers MCP tools to turn docs, repos, PDFs or videos into packaged AI skills.

    15k GitHub stars~760 tokensUpdated 10 days ago
    Agent WorkflowsAuto-check passed

  • MCP Apps Builder

    awslabs/cli-agent-orchestrator

    Official

    Load the official MCP Apps builder skills (create-mcp-app, migrate-oai-app, add-app-to-server, convert-web-app) from github.com/modelcontextprotocol/ext-apps.

    1.4k GitHub stars~1.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Release

    jgravelle/jcodemunch-mcp

    Publishing a jMunch release (jcodemunch-mcp, jdocmunch-mcp, jdatamunch-mcp, jragmunch-cli), reviewing/merging/closing PRs, and responding to the community.

    2.8k GitHub stars~6.5k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Open PR

    ArcadeAI/arcade-mcp

    Prepare arcade-mcp changes for review by verifying intended behavior, filling the repository PR template, and creating or updating the PR.

    1k GitHub stars~2.9k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Triage Security Advisories

    activepieces/activepieces

    Triage the GitHub privately-reported vulnerability backlog for Activepieces — pull repository security advisories from the Security tab, scope-check against SECURITY.md, deeply validate each…

    25k GitHub stars~3.9k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • MCP Client

    coleam00/second-brain-skills

    Universal MCP client for connecting to any MCP server with progressive disclosure.

    832 GitHub stars~1k tokensUpdated 8 mo ago
    Agent WorkflowsAuto-check passed

More from scenario-labs/skills

All 146 skills in this repo

  • Scenario Blender Grease Pencil

    scenario-labs/skills

    A skill your agent uses when drawing or animating with Grease Pencil in Blender 5.x from Python: 2D or 2.5D illustration, frame-by-frame animation, a cutout or part-based 2D character, strokes with…

    946 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed

  • Scenario Blender Hair

    scenario-labs/skills

    A skill your agent uses when grooming hair or fur in Blender with hair curves, such as a character hairstyle, animal fur, procedural fur in geometry nodes, or hair cards and mesh hair for games.

    946 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed

  • Scenario Blender Lighting Rendering

    scenario-labs/skills

    A skill your agent uses when lighting, rendering or compositing in Blender: light a character, product or hero shot, interior at dusk or night, three-point or motivated lighting, sun and sky, HDRI…

    946 GitHub stars~5k tokensUpdated yesterday
    Auto-check passed

  • Scenario Chatgpt Pet Create

    scenario-labs/skills

    A skill your agent uses when creating a ChatGPT pet or Codex pet with Scenario: hatching an animated companion from a text idea, a character, mascot or brand cue, or reference photos and art; making…

    946 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed

  • Scenario Godot Animation

    scenario-labs/skills

    A skill your agent uses when animating characters or scenes in Godot 4.7: AnimationPlayer clips and RESET, AnimationTree state machines and blend spaces built in code, Mixamo or glTF import, loop…

    946 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed

  • Scenario Godot Audio

    scenario-labs/skills

    A skill your agent uses when adding or fixing sound in Godot 4.7: audio buses and effects, volume sliders, 'too many sounds', combat audio with hundreds of enemies, sounds clipping or distorting, 3D…

    946 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Scenario Report

What does Scenario Report do?

A skill your agent uses 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…. Scenario Report is an agent skill from scenario-labs/skills.com: turning a failed generation, MCP tool error, or unclear skill into a reproducible report, collecting trace ids with diagnosticsrun, stripping keys, signed asset URLs, and personal data, asking before sharing a team or project id, or building a prefilled issue URL.

When should I use Scenario Report?

Scenario Report fits situations like: A Scenario user wants to report a bug; request a change; on the public tracker at github.com/scenario-labs/skills; by email to support@scenario.com: turning a failed generation.

How do I install Scenario Report in Claude Code?

Run `npx skills add scenario-labs/skills --skill scenario-report -a claude-code`. Or copy the skill folder (skills/scenario-report in scenario-labs/skills) into .claude/skills/scenario-report in your project. Claude Code loads it when a task matches its description.

How do I install Scenario Report in Codex?

Run `npx skills add scenario-labs/skills --skill scenario-report -a codex`. Or copy the skill folder (skills/scenario-report in scenario-labs/skills) into .agents/skills/scenario-report in your project. Codex loads it when a task matches its description.

Can I use Scenario Report in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add scenario-labs/skills --skill scenario-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scenario-report, .gemini/skills/scenario-report, .github/skills/scenario-report and .opencode/skills/scenario-report in your project.

What does Scenario Report need to run?

Going by SKILL.md and its folder, Scenario Report needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Scenario Report access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Scenario Report safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Scenario Report use?

Scenario Report is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Scenario Report use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Scenario Report?

Skills that share tags, products or a category with Scenario Report: Skill Seekers Builder (yusufkaraaslan/Skill_Seekers, 15k stars), MCP Apps Builder (awslabs/cli-agent-orchestrator, 1.4k stars), Release (jgravelle/jcodemunch-mcp, 2.8k stars) and Open PR (ArcadeAI/arcade-mcp, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scenario Report?

scenario-labs (a GitHub organization) maintains it in scenario-labs/skills, which has 946 GitHub stars. The repository holds 146 skills in this directory. The repository was last updated on October 10, 2026.

Source: scenario-labs/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.