technical-unit-assessment SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
technical-unit-assessment from ulises-jeremias/agent-toolkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ulises-jeremias/agent-toolkit/technical-unit-assessment@git:20260831.856ee57Pins git:20260831.856ee57 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ulises-jeremias/agent-toolkit
- Path
plugins/agent-toolkit-complete/.opencode/skills/technical-unit-assessment/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260831.856ee57, committed Aug 31, 2026
- Size
- 2,228 bytes
- Repository stars
- 19
- License
- MIT
WHAT - Evidence-based technical unit assessment for repositories, platforms, frontend, backend,.
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
# 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@sha256:676a0fb1c91af414The line at the top of this page pins the label git:20260831.856ee57, 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_edkzlwpj2nqujws3)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 31, 2026.
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 · 19 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_edkzlwpj2nqujws3 GET https://markdownregistry.com/api/v1/resolve?ref=ulises-jeremias/agent-toolkit/technical-unit-assessment GET https://markdownregistry.com/api/v1/blob/676a0fb1c91af41494ca5cbc408465ffbf403846c039e2ca27418d7a9b2d8988
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 ulises-jeremias/agent-toolkit
Every file in ulises-jeremias/agent-toolkit