audit-service-gaps SKILL.md skillA
audit-service-gaps from uzysjung/uzys-agent-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add uzysjung/uzys-agent-harness/audit-service-gaps@git:20260913.d34c425Pins git:20260913.d34c425 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- uzysjung/uzys-agent-harness
- Path
.claude/skills/audit-service-gaps/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260913.d34c425, committed Sep 13, 2026
- First version recorded
- Aug 2, 2026
- Size
- 14,641 bytes
- Repository stars
- 3
- License
- MIT
Audits the observable gaps between a service as it is today and an explicit target state, then researches how reference services actually solved each high-ranked gap before proposing a fix. DETECT scans through three independent lenses — north-star alignment, correctness (bugs), and user-perspective (UX) — and enumerates concrete, severity-ranked gaps; BENCHMARK verifies how a reference service closes each one and PROPOSES a differentiated close. VERIFY, CHANGE-IMPACT, DRIFT and FULL extend…
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
# Audit Service Gaps (reverse + competitive) A targeted loop, not a sweep by default. You take the service as it is today, find where it falls short of the ideal **and** where it is simply broken or awkward, then for each real shortfall you go look at how a benchmark service solved that exact problem before proposing a fix. The user's own framing: > "현재 서비스 개발 상태에서 북극성 기준으로 부족하거나, 버그가 있거나, 사용자 관점에서 부족한 점을 > 인지하면 다른 벤치마크 서비스는 이부분을 어떻게 해결했는지를 확인해 가는 거지." So the work fuses two moves that are usually done separately: **reverse-gap** (distance from the north-star / ideal) and **competitive benchmark resolution** (how others closed the same gap). DETECT finds gaps; BENCHMARK closes them. They chain: detect → for each gap, benchmark → propose fix. Two rules hold across every mode: **measure against a named baseline**, and **do not turn an opinion or an unverified benchmark claim into a fact.** ## When to use - You have a working-ish service and want to know, concretely, where it's behind its own north star, where it has bugs, and where the UX disappoints. - You've found a weak spot and want "다른 유사 깃허브 프로젝트 / 레퍼런스 SaaS 는 이걸 어떻게 했지?" before inventing a fix. …
Read the whole file at its exact version.
How to install
mdr add uzysjung/uzys-agent-harness/audit-service-gaps@sha256:81323cc7d4bda9f3The line at the top of this page pins the label git:20260913.d34c425, 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_2yxiogy5lv3pf5yu)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 2, 2026 and Sep 13, 2026, about one every 21 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260913.d34c425 latest | 2026-09-13 | d34c425 | 14,641 B | A | view · diff |
| git:20260830.f31c1d9 | 2026-08-30 | f31c1d9 | 14,796 B | A | view · diff |
| git:20260802.f93c659 | 2026-08-02 | f93c659 | 14,942 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 (14641 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
uzysjung/uzys-agent-harness · 3 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2yxiogy5lv3pf5yu GET https://markdownregistry.com/api/v1/resolve?ref=uzysjung/uzys-agent-harness/audit-service-gaps GET https://markdownregistry.com/api/v1/blob/81323cc7d4bda9f3739e8a72f566699d209f888aa216f77f106e77db975f231d
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 uzysjung/uzys-agent-harness
Every file in uzysjung/uzys-agent-harness