scenario-moderation
Use when a Scenario generation is blocked, refused, or returns a moderation or sensitive-content error, when a video is rejected after rendering or its audio track is flagged, when an output is flagged for likeness to a real person or for IP and copyright detection, when the same prompt passes on on…
Install / Use
npx skills add scenario-labs/skills --skill scenario-moderationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of scenario-moderation
scenario-moderation scores 86/100 on our quality scale, 2443rd of 4,698 Development & Engineering skills we index.
Its SKILL.md is 14 KB long, well organised into 10 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 29 days ago, so scenario-moderation is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-10. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
scenario-moderation compared with similar skills
All 4 of these similar skills score higher than scenario-moderation; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-moderation (this skill)by scenario-labs | 86 | 1.0k | 29d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install scenario-moderation?
- Run
npx skills add scenario-labs/skills --skill scenario-moderation. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-moderation work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is scenario-moderation safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is scenario-moderation still maintained?
- The repository was last updated 29 days ago, so scenario-moderation is actively maintained.
Skill content
View source on GitHubname: scenario-moderation description: "Use when a Scenario generation is blocked, refused, or returns a moderation or sensitive-content error, when a video is rejected after rendering or its audio track is flagged, when an output is flagged for likeness to a real person or for IP and copyright detection, when the same prompt passes on one model and fails on another, or when a team's own characters, weapons, or props get flagged. Keywords: blocked prompt, content moderation, refused generation, provider filter, false positive." license: MIT
Scenario Blocked Generations
Overview
Three gates can stop a generation, and only two of them read the prompt. Content filters run on the
model provider's side, not on Scenario, so a provider block is a property of the model that was
picked and the same prompt usually passes elsewhere in the catalog. IP Detection is the team's own
gate: it screens the prompt and the input images before the run, an organization admin switches it
on, and no model switch clears it. Plan and blocklist restrictions remove models before any prompt
is judged. Treat a block as a routing problem first and a wording problem second. This skill is
about false positives on content a team is entitled to make; it is not a way to produce content a
provider prohibits. Core loop: see the scenario skill. If a sibling skill named here is missing
from your available skills, load it with skill_get (Scenario MCP) or ask the user to install it
(https://github.com/scenario-labs/skills#install); unattended, proceed from tool schemas and flag
the gap.
Quick reference
| Step | Call |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Read the actual error | job_get with job_id: the row carries error and hint, plus modelId (the model to exclude) and cuCost (what the failed run charged); verbose=true adds metadata.input with the exact prompt the job ran. Or read error and hint off the jobs_wait row |
| Confirm the charge | job_get's cuCost first; a policy block is typically refunded and failed jobs are reimbursed except xAI generations stopped by moderation (see scenario), but the reservation is not always released at once, so confirm later with usage bounded by start_date and end_date to the job's day and include=["usages"], reading the per-type totals (the headline is project-lifetime; a team-gate screen shows as its own IP Detection line), and file the job_id with support if a charge stands |
| Read the team's gate | teams_list: the team row carries ipDetectionEnforcement; anything but disabled means a refusal naming intellectual-property risk is the team's own policy, screened before the run |
| Find alternative models | recommend with the failed job's capability (txt2img for a text-to-image block, img2img with a reference in play, img2video for a clip animated from a still) plus the user's own words; set max_cost_cu a little above the failed row's cuCost per asset to stay in the cost band, and drop the failed modelId from the ranking yourself, since recommend has no exclusion argument |
| Price an alternative | model_run with dry_run=true |
| Re-test the same intent | One model_run per candidate, prompt unchanged, so the model stays the only variable |
Four failures look alike and only the first is about wording: a provider moderation block, an IP Detection block from the team's own settings, a 403 Forbidden error (the plan does not include that model), and a model a team has put on its own blocklist. Read the error before rewriting anything.
Why legitimate prompts get blocked
Three triggers stack, and each alone often sits under the threshold:
- Recognizable characters. Automated filters react to character names and signature traits they recognize. They cannot know who owns the IP, so a team's own characters are flagged like anyone else's.
- Intensity-coded language. Words chosen to convey scale or drama ("oversized", "huge", "massive") read as violence in aggregate, even when the subject is a prop.
- Real-person likeness. Filters watch for resemblance to public figures in the output as well as names in the prompt, so a character sheet the platform itself generated can be refused as a reference on the next run, and a celebrity comparison in the prompt ("built like a heavyweight champion") is a name by another route.
With two present the prompt sits near the threshold, which is why the same intent passes one run and fails the next: a small rewording tips it over. An upstream LLM step that rewrites prompts is a frequent cause, because it leans harder on intensifiers to solve an unrelated problem and re-introduces the block on every run.
Filters differ by provider, not by price
Scenario's public content policy guide ranks the providers: Google's models (Gemini, Veo) block the
most brand and character references, ByteDance, OpenAI, Ideogram and Hunyuan sit in the middle, and
FLUX and Recraft are the most permissive. recommend ranks by measured performance, not by filter
strictness, so an alternative from the same provider inherits the same filter: take the next
candidate from a different provider, and read modelId on the failed row to know which one that
was: the provider is usually legible in the id, and when it is not, model_get (catalog-only, read
lane) returns the record with complianceMetadata.modelProvider.
Video and audio blocks
Video changes the economics of a block. Several providers moderate the finished render, so a
rejected clip has already been rendered in full, and a retry of the identical payload renders it
again. Read cuCost on the failed row before anything else and confirm the charge per the quick
reference, then switch provider as above, prompt unchanged.
The audio track is judged on its own. OutputAudioSensitiveContentDetected on an audio-enabled
video run means the soundtrack tripped the filter, and the usual cause is a named instrument or
genre, even inside an exclusion: "no music" and "a distant guitar" have both failed where "room
tone, footsteps, a single voice" passed. Describe diegetic sound positively and name nothing to
exclude; when the clip needs no sound, turn the audio field off where the schema exposes one
(generateAudio on many families) rather than prompting silence.
IP Detection is the team's own gate
Teams on the Enterprise plan can switch on IP Detection, Scenario's own gate, independent of any
provider's filter: it reads the prompt and the input images before the run against the filters an
organization admin enabled (fictional characters, brands and trademarks, celebrity likeness, artist
styles, and custom filters), and a match fails the job at once with a message naming
intellectual-property risk, nothing generated and no generation cost charged. The screen itself
bills 1 CU per screened generation plus 1 CU per input image, charged even when the result is a
block and reported as its own IP Detection line in usage; video, audio and 3D inputs are neither
analyzed nor charged. The setting rides the teams_list row as ipDetectionEnforcement: while it
reads disabled, every IP or copyright refusal is a provider's; the active levels differ in one
thing only, whether a job is let through or blocked when the check itself cannot run, so report the
literal value and that distinction. When it is active, read which gate the error names: the team's
gate names intellectual-property risk, a provider's names a content policy violation, and when the
text says neither, run the unchanged prompt once on one alternative provider: a provider filter
clears with the switch, the team's gate repeats on any model. A team-gate block earns one retry with
the design described visually and no protected mark in the prompt or in any input image (the brands
filter reads a logo shown in a reference like a name, while generic product descriptions are not
flagged). If that repeats, it is a conversation, not a call: tell the user which gate fired; an
organization admin owns the filters and can opt a single project out of screening for licensed work,
and verified IP holders who keep hitting false positives on their own licensed property have an
escalation path through their Scenario account manager. A copyright warning attached to a completed
output is the provider's flag and informational: the asset was delivered, and reviewing it before
commercial use is the team's call.
Recovery, cheapest first
- Switch provider. Usually needs no prompt edit at all. Run the unchanged prompt against two or three alternatives from other providers at comparable cost; if they pass, the filter was that provider's, not the content's.
- Describe scale by proportion, not intensity. "The staff reaches shoulder height" or "the blade is about as long as the forearm" carries the same art direction as "oversized" without the violence coding.
- Soften recognizable names in the direct model input. Describe the design in the prompt and
carry identity with a reference image instead, which holds the look better anyway (see
scenario-consistency). Drop real-person comparisons the same way. - Constrain any upstream rewriter. When an LLM node writes the final prompt, put steps 2 and 3 in its instructions, or the block returns on the next run.
Then stop. If every provider refuses and one honest rewrite has not cleared it, the filter
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
