scenario-asset-analysis SKILL.md skillA
scenario-asset-analysis from scenario-labs/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add scenario-labs/skills/scenario-asset-analysis@git:20261013.0b5fa62Pins git:20261013.0b5fa62 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- scenario-labs/skills
- Path
skills/scenario-asset-analysis/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261013.0b5fa62, committed Oct 13, 2026
- First version recorded
- Aug 16, 2026
- Size
- 7,343 bytes
- Repository stars
- 1,094
- License
- MIT
Use when finished Scenario assets have to give something back: a caption for a dataset or alt text, a reusable style description, a verdict against a brief, a canny, depth, pose, or segmentation control map for the next model, or the asset itself found again by text, tags, or visual similarity and filed into a collection. Keywords: caption, describe, analyze, QA, control map, find similar, reverse image search, semantic search, tag, collection.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Scenario Asset Analysis ## Overview Four tools extract captions, style descriptions, analysis, or control maps from existing assets: three fixed-purpose, one open-ended. With `search` (default toolset) they answer the questions that come after a batch lands, which is where most of the work actually is: is this on brief, what look is this, what does this show, what can the next model condition on, where did last week's approved version go. None of them are in the default toolset. Get schemas with `scenario_tools_search`, then run each through the executor matching the returned `permission`: `read` uses `scenario_tool_execute_read`, `write` uses `scenario_tool_execute_write`. Use that live result for both estimates and runs; do not infer the lane from an unchanged input asset. Put the tool name in `name` and its inputs under `parameters`. Or reconnect with `?toolsets=full`. Connection and scope: 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. ## Quick reference …
Read the whole file at its exact version.
How to install
mdr add scenario-labs/skills/scenario-asset-analysis@sha256:17cd5124463e3317The line at the top of this page pins the label git:20261013.0b5fa62, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_hxsxmr6egxhukzuq)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Aug 16, 2026 and Oct 13, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261013.0b5fa62 latest | 2026-10-13 | 0b5fa62 | 7,343 B | A | view · diff |
| git:20261013.d64e363 | 2026-10-13 | d64e363 | 7,448 B | A | view · diff |
| git:20261004.f28b840 | 2026-10-04 | f28b840 | 7,072 B | A | view · diff |
| git:20260901.32b9e2b | 2026-09-01 | 32b9e2b | 7,054 B | A | view · diff |
| git:20260823.3cf5952 | 2026-08-23 | 3cf5952 | 6,729 B | A | view · diff |
| git:20260820.1c618f1 | 2026-08-20 | 1c618f1 | 6,413 B | A | view · diff |
| git:20260816.cc146d8 | 2026-08-16 | cc146d8 | 5,134 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7343 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
scenario-labs/skills · 1,094 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hxsxmr6egxhukzuq GET https://markdownregistry.com/api/v1/resolve?ref=scenario-labs/skills/scenario-asset-analysis GET https://markdownregistry.com/api/v1/blob/17cd5124463e3317923c4b779b098b2a2263cbc4659a64d7d375a3839c6d0a85
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.