technical-unit-assessment skillA
technical-unit-assessment is agent-read markdown (skill) from ulises-jeremias/agent-toolkit: WHAT - Evidence-based technical unit assessment for repositories, platforms, frontend, backend,.
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
# Technical Unit Assessment (WHAT) Assess a technical unit: frontend app, backend API, data platform, infrastructure/IaC scope, mobile app, AI/ML pipeline, or another technical workload. Run **`project-assessment-evidence`** first. Use **`project-assessment`** as the router for multi-unit assessments. ## Out of scope - Does NOT score indicators without evidence — mark as **Not assessed** - Does NOT make technical decisions — scores inform, humans decide - Does NOT produce final report without **`output-handshake`** ## Unit intake Ask before scoring: - Unit name and type (frontend / backend / infra / data / mobile / AI) - Repositories, services, infrastructure scopes, or pipelines included - Technical decision ownership (team, client, shared, unknown) - Assessment period - Authoritative systems for code, docs, CI/CD, incidents, observability, security ## Workflow 1. Run **`project-assessment-evidence`** to build evidence map 2. Select indicator groups matching the unit type (see `references/indicator-groups.md`) 3. Score only indicators with evidence; mark rest as **Not assessed** 4. Note confidence and missing evidence per score …
Read the whole file at its exact version.
How to install
mdr add ulises-jeremias/agent-toolkit/technical-unit-assessment@git:20260831.856ee57mdr add ulises-jeremias/agent-toolkit/technical-unit-assessment@sha256:676a0fb1c91af414Pin 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_e7cqqvivbfity2df)
1 badge views in 30 days
Versions
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 (2228 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
ulises-jeremias/agent-toolkit · 18 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_e7cqqvivbfity2df GET https://markdownregistry.com/api/v1/resolve?ref=ulises-jeremias/agent-toolkit/technical-unit-assessment GET https://markdownregistry.com/api/v1/blob/676a0fb1c91af41494ca5cbc408465ffbf403846c039e2ca27418d7a9b2d8988
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.