Assess one bounded Proto UI Adapter question without changing repository or external state. Use for new-Adapter research, target compatibility, catalog readiness, reviewed Module support or omission evidence, Host Capability fidelity, lifecycle translation, dependency risk, or implementation readiness. Do not catalog, implement, repair, or approve the Adapter slice.
Installs into .claude/skills of the current project.
Are you the author of Pui Adapter Assess?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/proto-ui-pui-adapter-assess)
---
name: pui-adapter-assess
description: Assess one bounded Proto UI Adapter question without changing repository or external state. Use for new-Adapter research, target compatibility, catalog readiness, reviewed Module support or omission evidence, Host Capability fidelity, lifecycle translation, dependency risk, or implementation readiness. Do not catalog, implement, repair, or approve the Adapter slice.
---
# Assess one Adapter question
1. Require current `pui-orient` and `pui-trace` artifacts for the bounded question.
2. Read the Adapter decision, cataloging guide, target profile when present, related Module and Host Capability entities, tests, current translation code, issue boundary, and exact exclusions.
3. Classify the question as new-Adapter research, catalog readiness, compatibility assessment, support or omission evidence, capability-fidelity assessment, or implementation readiness. Do not move between classes silently.
4. Inspect real translation behavior and executable evidence. Distinguish observed support, explicit omission, uncataloged scope, implementation attachment, and faithful realization.
5. Identify target and runtime range, lifecycle ownership, failure behavior, dependency implications, portable-semantic gaps, incompatible host behavior, and evidence still needed.
6. Return a read-only assessment packet containing facts, unknowns, recommendation, exclusions, residual risks, and one eligible next registered leaf. Use the schema's gate field only for an unresolved Adapter identity/semantics/compatibility choice or a privileged operation; otherwise route governed parity, evidence, and implementation work forward immediately. Do not load that next leaf.
Remain read-only. Do not create a support matrix from packages or dependencies, infer conformance from source attachment, edit catalog entities, or authorize implementation.
## Explicit handoff
Do not load or execute another skill. Return exactly one handoff conforming to `internal/agent-operations/schemas/skill-handoff.schema.json`. Carry required prior artifacts by reference, include every artifact this leaf produces according to `skills.yaml`, and set `nextSkillId` to one eligible registered leaf or `null`.
Communicate with the user in the user's current language. Keep target, entity, and API identifiers canonical.
