Scenario Skills

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 Scenario MCP, plus expert teams that drive Blender, Maya, ZBrush, Unreal, and Unity.

Agent Skills Python Listed MIT

Is Scenario Skills safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 7.7 / 10
Provenance None
Signed commits 100%
Last push yesterday
Compare Scenario Skills
Suggest a correction

In detail: Scenario Skills scores 70.6/100 (Grade B), ranked #36 of 396 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 7.7/10; 100% of recent commits are signed; last pushed 2026-11-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Scenario Skills could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Chain of custody

Scanners check what the code says. This traces who ships Scenario Skills and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Signed

    github.com/scenario-labs/skills, MIT, last pushed 2026-11-16. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 7.7/10 (scanned Nov 16, 2026). The checks that decide who can get a change released:

    • Code Review2
    • Branch Protection8
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies10
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 8
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 2
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 10
    SAST -1
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 5
  3. Published packages None

    No registry package. Scenario Skills is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Scenario Skills.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Scenario Skills’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Scenario Skills compares in Agent Skills

  1. #34 Tlive 72.9 +2.3
  2. #35 Computer Use Linux 72.1 +1.5
  3. #36 Scenario Skills 70.6 this agent
  4. #37 RuView 70.2 −0.4
  5. #38 ClawBio 70.1 −0.5

Bars show each HVTrust score; the tick marks Scenario Skills’s 70.6.

Where the 70.6 comes from

HVTrust dimensions vs the Agent Skills average

70.6 / 100 · 100.0% confidence

Scenario Skills Agent Skills average (396 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.6 / 25
6.4 above avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.7 below avg 11.5
Transparency50% declared license · 50% OSSF Scorecard
15.0 / 17
2.8 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
5.9 above avg 14.0
AdoptionLog-scaled stars · package downloads
8.6 / 20
0.6 below avg 9.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-10
Newly Listed
First tracked at rank #41
Maintainer Checklist
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
83.3
Activity sub-score · out of 100
#36

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-17 12:07 UTC · Repo last pushed yesterday

Rank Trend

2026-11-10 2026-11-17

Activity & Reach

Stars
3.9k
Forks
336
Last Push
2026-11-16
yesterday
Commits (4 wk)
120
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
10
Rank Change
▼1
was #35

Analysis

Activity Inputs

83.3 / 100
StarsRepository reach
21.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
11.8 / 20

Common questions about Scenario Skills

Scenario Skills has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Scenario Skills publish package provenance?
No published build provenance is currently detected for Scenario Skills. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Scenario Skills have an OpenSSF Scorecard?
Scenario Skills has an OpenSSF Scorecard score of 7.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Scenario Skills actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Scenario Skills use?
Scenario Skills ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Scenario Skills's commits signed?
100% of the last 100 commits to Scenario Skills are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
medium confidence
Implemented
Scenario Skills appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Scenario Skills?

For maintainers

HVTrust scores Scenario Skills from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Listed 1
2026-11-10
Newly Listed
First tracked at rank #41

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 70.6 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/scenario-skills.svg)](https://hvtracker.net/agents/scenario-skills)
HTML:
<a href="https://hvtracker.net/agents/scenario-skills"><img src="https://hvtracker.net/badge/scenario-skills.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON