objective-brief SKILL.md skillA
objective-brief 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/objective-brief@git:20261014.0ec0829Pins git:20261014.0ec0829 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/objective-brief/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261014.0ec0829, committed Oct 14, 2026
- First version recorded
- Sep 13, 2026
- Size
- 13,598 bytes
- Repository stars
- 3
- License
- MIT
Rewrite work about to be delegated, designed, or run over several steps into the canonical XML brief — objective, inputs, invariants, success_criteria, boundaries, autonomy, verification, communication, output_format — so the worker receives one judgeable definition of done instead of prose. Runs in two directions: INBOUND reshapes a sprawling or half-formed request into that shape, filling each field from context already on screen and dropping sections that do not apply; OUTBOUND writes the…
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
# Objective Brief A single shape for "here is the task". The point is not tidiness — it is that every field is a place where an unstated assumption would otherwise stay unstated. A worker that receives prose guesses what done means; a worker that receives this brief can be judged against it. Use it in both directions. **Inbound**, an arriving request gets normalized into the shape before you act on it. **Outbound**, a delegation prompt *is* this shape — you do not write a different prompt format per worker. ## The template Copy this shape. Fill what applies, delete what does not — an empty section left in place reads as a field that was considered and found empty, which is a claim you did not make. ```xml <objective> [최종적으로 만들어야 할 의사결정 가능 상태 — 무엇을, 왜] [가능하면 한 문장 판정 기준. 예: "이 화면을 보고 실제 주문을 낼 수 있는가"] </objective> <inputs> [파일은 @경로로 직접 지정, 에러/로그는 요약 없이 원문] [기존 자산을 승계할 경우: 무엇을 참고하고, 어떤 개념·인터페이스를 재정의하지 않고 그대로 쓰는지 명시] </inputs> <invariants> [정답의 기준. 구현 방법이 아니라 결과값의 정의이므로 autonomy가 침범 불가. 계산 규칙·법규·도메인 제약 등. 바뀔 수 있는 값(세율 등)은 파라미터로 다루라고 명시. 해당 없으면 섹션 삭제 — 빈 섹션을 남기지 않는다] </invariants> <success_criteria> [명령어·외부 관찰로 검증 가능한 완료 조건. 체크리스트 형태 권장. …
Read the whole file at its exact version.
How to install
mdr add uzysjung/uzys-agent-harness/objective-brief@sha256:46cd19cd092ebdf9The line at the top of this page pins the label git:20261014.0ec0829, 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_3ykzautth5yjvjf7)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 13, 2026 and Oct 14, 2026, about one every 16 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.0ec0829 latest | 2026-10-14 | 0ec0829 | 13,598 B | A | view · diff |
| git:20260920.639753f | 2026-09-20 | 639753f | 13,462 B | A | view · diff |
| git:20260913.a125453 | 2026-09-13 | a125453 | 13,391 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 (13598 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_3ykzautth5yjvjf7 GET https://markdownregistry.com/api/v1/resolve?ref=uzysjung/uzys-agent-harness/objective-brief GET https://markdownregistry.com/api/v1/blob/46cd19cd092ebdf9b725961b6fb3b5153604199f503ea9e7ec1cfefd78a16615
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