jev-opportunities skillA
jev-opportunities is agent-read markdown (skill) from jpcaparas/skills: Finds and spikes Jev optimisation opportunities in an existing application without Jev. Use only when explicitly invoked as jev-opportunities. Scrapes live docs, maps costs, fast paths and adjudication, and measures approved experiments..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Jev opportunities Find where Jev could improve an existing application, then test the promising decisions against what the application does today. A useful result may be **do not add Jev**. Optimise the whole workflow, not the number of Jev calls. ## Invocation and scope Run only when the user explicitly invokes `jev-opportunities`. A mention of Jev, a slow endpoint, an expensive LLM bill, or an API key in the environment is not an invocation. One invocation covers this application's audit and its follow-up spikes, not unrelated projects or a standing background monitor. This skill owns discovery and disposable experiments for an app without Jev. First inspect manifests, configuration names, adapters, and call sites to confirm that premise without reading secret values. If Jev is already integrated, report the existing boundary and ask whether to scope an incremental opportunity audit. Existing-integration debugging or production implementation belongs to the project's normal workflow; `integrating-typesafe`, if installed, is optional implementation guidance, not a dependency or permission to change the app. | Activity | Authority needed | | --- | --- | …
Read the whole file at its exact version.
How to install
mdr add jpcaparas/skills/jev-opportunities@git:20260920.4431d3fmdr add jpcaparas/skills/jev-opportunities@sha256:ce82452a4baa6cb5Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_6qfxaxu5rbzyfkdm)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260920.4431d3f latest | 2026-09-20 | 4431d3f | 14,544 B | A | view · diff |
| git:20260919.d06ad09 | 2026-09-19 | d06ad09 | 12,658 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 (14544 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
jpcaparas/skills · 51 stars · license none · pushed 2026-09-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6qfxaxu5rbzyfkdm GET https://markdownregistry.com/api/v1/resolve?ref=jpcaparas/skills/jev-opportunities GET https://markdownregistry.com/api/v1/blob/ce82452a4baa6cb5952a18630788466d6a8e4dff4dd0250524f3cd348dd0b080
Your agent 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.