validate-the-users-proposed-mechanism SKILL.md skillA
validate-the-users-proposed-mechanism from iamakbarsha1/whetstone is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add iamakbarsha1/whetstone/validate-the-users-proposed-mechanism@git:20261024.08b5719Pins git:20261024.08b5719 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- iamakbarsha1/whetstone
- Path
skills/validate-the-users-proposed-mechanism/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261024.08b5719, committed Oct 24, 2026
- First version recorded
- Aug 15, 2026
- Size
- 6,632 bytes
- Repository stars
- 4
- License
- CC-BY-4.0
Use when a user specifies a platform, tool, library, or approach as part of a request — their choice is a proposed MECHANISM, not a spec. Grep the built artifact for disqualifying signals before agreeing, separate their intent from the mechanism, and satisfy the intent with a feasible mechanism when the chosen one conflicts. Triggers on "deploy on X", "use library Y", "run it on Z", "switch to", "let's use", and any user-named tech that the existing code may not fit.
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
# Validate the User's Proposed Mechanism **Type:** Open-source — client-agnostic methodology, no project-specific detail. **Created by akbarsha — https://github.com/iamakbarsha1** Distilled from a case where a user's stated deployment stack was infeasible for the built application, and implementing it verbatim would have discarded working, tested code. **Licence:** Released under CC BY 4.0 — share and adapt for any purpose with credit. Full text: `LICENSE` at the repository root. **Feedback & Support:** If a rule here proves wrong or needs sharpening, open an issue on the repository or contact the author at the profile link above. If the problem is the agent not following a rule below rather than the rule itself, that's an execution failure — acknowledge and correct it. ## The core rule When a user names a platform, tool, library, or approach, treat it as a PROPOSED MECHANISM for an underlying INTENT — not as a fixed requirement. Before implementing it, check the thing already built for signals that disqualify the chosen mechanism. If it conflicts, separate the intent from the mechanism, satisfy the intent with a feasible mechanism, and push back …
Read the whole file at its exact version.
How to install
mdr add iamakbarsha1/whetstone/validate-the-users-proposed-mechanism@sha256:253e1b2c4aac7787The line at the top of this page pins the label git:20261024.08b5719, 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_s746ov67ng4zrqds)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 15, 2026 and Oct 24, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.08b5719 latest | 2026-10-24 | 08b5719 | 6,632 B | A | view · diff |
| git:20261024.d153cce | 2026-10-24 | d153cce | 6,363 B | A | view · diff |
| git:20261019.b3a119b | 2026-10-19 | b3a119b | 6,080 B | A | view · diff |
| git:20260815.a481f85 | 2026-08-15 | a481f85 | 5,134 B | A | view · diff |
| git:20260815.0363531 | 2026-08-15 | 0363531 | 4,157 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 (6632 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
iamakbarsha1/whetstone · 4 stars · license CC-BY-4.0 · pushed 2026-10-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_s746ov67ng4zrqds GET https://markdownregistry.com/api/v1/resolve?ref=iamakbarsha1/whetstone/validate-the-users-proposed-mechanism GET https://markdownregistry.com/api/v1/blob/253e1b2c4aac7787327952df6c727d65822dc5a7a399af28f2b20a304d8bb25c
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.