options-analysis SKILL.md skillA
options-analysis from federbenjamin/feder-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add federbenjamin/feder-skills/options-analysis@git:20261007.87f312aPins git:20261007.87f312a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- federbenjamin/feder-skills
- Path
skills/options-analysis/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261007.87f312a, committed Oct 7, 2026
- Size
- 1,556 bytes
- Repository stars
- 3
- License
- MIT
Answer an open design or tooling question with N mechanistically distinct options — each with its own pros and cons block — then one recommendation argued from mechanism, naming which options to skip and why.
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
# options-analysis
The user wants to *choose*, not to read a survey. Deliver N real alternatives and a verdict that
eliminates.
Options must differ in **mechanism**, not in degree — a hook that blocks, a config default, and a
runtime escalation ladder are three options; three phrasings of "add a rule" are one. Give the
number asked for, and when only two are real, say so rather than padding with a variant.
The cons are where the answer gets made. Lead each option's cons with its disqualifying property —
the reason it fails, not its rough edges. Ground that failure in how the thing works, and look up
the real contract (tool schema, API precedence, config resolution order) when the con depends on
it; a con asserted from vibes is the expensive kind of wrong. When an option has no serious con,
say so instead of manufacturing balance.
The verdict names a winner and names what to skip, reasoned from mechanism. Layering is a
legitimate answer ("2 as the floor, 1 as the enforcement") — say which does which job. "Depends on
your priorities" is a non-answer.
If the framing itself is broken — the constraint can't be enforced where they're asking, the
…Read the whole file at its exact version.
How to install
mdr add federbenjamin/feder-skills/options-analysis@sha256:b587654f1eecd729The line at the top of this page pins the label git:20261007.87f312a, 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_ygxlelm7sbh5yaps)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 7, 2026.
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 (1556 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
federbenjamin/feder-skills · 3 stars · license MIT · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ygxlelm7sbh5yaps GET https://markdownregistry.com/api/v1/resolve?ref=federbenjamin/feder-skills/options-analysis GET https://markdownregistry.com/api/v1/blob/b587654f1eecd7290091e05ac9aa473535551c7094b0b1b21aeb52cfdff6601d
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.
More from federbenjamin/feder-skills
Every file in federbenjamin/feder-skills