Skip to content
Back to skills

Technical Unit Assessment

ASecurity

WHAT - Evidence-based technical unit assessment for repositories, platforms, frontend, backend,

  • 19 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 2, 2026
ai-agentsapifrontendbackendci/cdsecurity

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 2, 2026

npx -y skills add ulises-jeremias/agent-toolkit --skill technical-unit-assessment --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Technical Unit Assessment?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Technical Unit Assessment
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ulises-jeremias-technical-unit-assessment/badge)](https://www.skillsdirectory.com/skills/ulises-jeremias-technical-unit-assessment)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: technical-unit-assessment
description: WHAT - Evidence-based technical unit assessment for repositories, platforms, frontend, backend,
  infrastructure, data, UI/UX, and AI-native structural readiness.
origin:
  type: first-party
---
# 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
5. Apply **`output-handshake`** before final scorecard

## Scoring rules

Use the 1–5 scale from `references/indicator-groups.md`. Do not average unrelated indicators
without explaining weighting. Request validator for subjective scores.

## References

- `references/indicator-groups.md` — all indicator groups + scoring scale + AI-native readiness
- `references/default-template.md` — technical unit scorecard template
- `references/example-frontend-assessment.md` — example assessment for a frontend team

## Delegates to

| Need | Skill |
|------|-------|
| Evidence intake | **`project-assessment-evidence`** |
| Multi-unit routing | **`project-assessment`** |
| Deep UI/UX review | **`figma`** / **`figma-implement-design`** |
| Repo discovery | **`assistant`** |
| Final output gate | **`output-handshake`** |

Files in this skill

  • SKILL.md2.2 KB
  • references/default-template.md482 B
  • references/example-frontend-assessment.md5.5 KB
  • references/indicator-groups.md2.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.