feature-risk-analysis SKILL.md skillA
feature-risk-analysis from robsonkades/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add robsonkades/agent-skills/feature-risk-analysis@git:20261016.c769bd8Pins git:20261016.c769bd8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- robsonkades/agent-skills
- Path
skills/feature-risk-analysis/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261016.c769bd8, committed Oct 16, 2026
- First version recorded
- Sep 6, 2026
- Size
- 12,107 bytes
- Repository stars
- 3
- License
- Apache-2.0
Naming what could go wrong with a specific feature in a form that can be acted on: the failure stated as an event rather than a worry, how anyone would find out it happened, what reduces its probability or its cost, and what is done if it happens anyway. Use before implementation on anything touching data, integrations, concurrency or a released contract, when a plan has a risk section containing only adjectives, when a HIGH risk has no detection signal, when a migration or a breaking change…
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
# Feature Risk Analysis ## Purpose Turn a feature's possible failures into decisions about controls, exposure and follow-up. Category names such as "performance" or "data integrity" do not establish an event or its rating. **Detection** explains how anyone discovers the event; **fallback** states what can be done afterward. Missing detection or recovery is itself important risk evidence. Keep the row and its unresolved controls visible instead of discarding it as a worry. ## Workflow 1. **Bound the assessment and follow the affected paths.** Identify the change, revision and rollout/operation window. Use the impact map, assumptions, unresolved decisions and resource list to derive candidates, then inspect the actual caller or producer through the changed operation to affected state or consumers. An upstream map is a starting point, not proof of coverage. Check where a claimed control acts before crediting it to another entry path. Read `references/risk-register.md` when deriving a register, resolving uncertain ratings, or revisiting one; it covers path tracing, evidence, controls and outcome review. …
Read the whole file at its exact version.
How to install
mdr add robsonkades/agent-skills/feature-risk-analysis@sha256:b5c5c22686442b0dThe line at the top of this page pins the label git:20261016.c769bd8, 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_wgtzroms6uhjjiok)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 6, 2026 and Oct 16, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.c769bd8 latest | 2026-10-16 | c769bd8 | 12,107 B | A | view · diff |
| git:20260927.9ecadfd | 2026-09-27 | 9ecadfd | 9,647 B | A | view · diff |
| git:20260923.832673e | 2026-09-23 | 832673e | 9,417 B | A | view · diff |
| git:20260911.37b054b | 2026-09-11 | 37b054b | 9,193 B | A | view · diff |
| git:20260906.e6ad4bd | 2026-09-06 | e6ad4bd | 9,046 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 (12107 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
robsonkades/agent-skills · 3 stars · license Apache-2.0 · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wgtzroms6uhjjiok GET https://markdownregistry.com/api/v1/resolve?ref=robsonkades/agent-skills/feature-risk-analysis GET https://markdownregistry.com/api/v1/blob/b5c5c22686442b0d25cd7c59c0c9316c46fc8893f314c522fda6a52b85f57d80
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.