evaluate-llm-feature SKILL.md skillA
evaluate-llm-feature from event4u-app/agent-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add event4u-app/agent-config/evaluate-llm-feature@git:20261024.25cb8e3Pins git:20261024.25cb8e3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- event4u-app/agent-config
- Path
src/skills/evaluate-llm-feature/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261024.25cb8e3, committed Oct 24, 2026
- First version recorded
- Jul 19, 2026
- Size
- 8,199 bytes
- Repository stars
- 19
- License
- MIT
Black-box evaluation of a shipped LLM feature — adversarial probes for hallucination, prompt-injection, and cost-runaway vs stated expectations. Not RAG/embedding. Triggers 'review my chatbot'.
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
# evaluate-llm-feature
A consumer building their product on top of this suite ships an LLM feature — a
support chatbot, a doc assistant, an agent step. This skill helps them evaluate
**that shipped behaviour as a black box**: the user describes what the feature is
supposed to do; the skill runs adversarial probes and reports where it breaks.
It is a black-box evaluator, not an app-builder. It never asks how the feature is
built and never teaches how to build it — the internals are out of scope.
## When to use
- The user points at a *deployed* LLM feature ("review my chatbot", "evaluate my
AI assistant", "is my summariser safe to ship?") and can describe its intended
behaviour, inputs, and cost budget.
- Before a launch, or after a regression, when the question is *"does this LLM
feature behave, resist abuse, and stay within cost?"* — not *"is my code
correct?"*.
**When NOT to use:** the user wants to *build* an LLM app (RAG architecture,
chunk sizing, embedding models, vector-index choice, fine-tuning, serving
infrastructure). That is out of mission — say so and stop. For prompt-injection
defence at the config layer of *this suite's* agents, use
…Read the whole file at its exact version.
How to install
mdr add event4u-app/agent-config/evaluate-llm-feature@sha256:5978520572aa21ddThe line at the top of this page pins the label git:20261024.25cb8e3, 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_hwchz5yq4err7r5a)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 19, 2026 and Oct 24, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.25cb8e3 latest | 2026-10-24 | 25cb8e3 | 8,199 B | A | view · diff |
| git:20260907.98e9af2 | 2026-09-07 | 98e9af2 | 6,951 B | A | view · diff |
| git:20260730.4ef14f8 | 2026-07-30 | 4ef14f8 | 6,879 B | A | view · diff |
| git:20260719.c1d4036 | 2026-07-19 | c1d4036 | 6,895 B | A | view · diff |
| git:20260719.b94249f | 2026-07-19 | b94249f | 6,651 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 (8199 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
event4u-app/agent-config · 19 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hwchz5yq4err7r5a GET https://markdownregistry.com/api/v1/resolve?ref=event4u-app/agent-config/evaluate-llm-feature GET https://markdownregistry.com/api/v1/blob/5978520572aa21dd9aa55f45ea3aac36d8aac1980beef3a0ae1842aaa21ad1ef
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.