What this is not
What is the difference between an agent skill and an enforcement runtime?
This is not a claim that installing a skill can stop an unauthorized action. A skill can describe permit, deny, escalate, and error outcomes, but an agent or process that ignores those outcomes can still act.
This is not a released runtime, package, or daemon. The runtime boundary described here is a separate product layer and is not available through this page.
This is not a registration claim, a security certification, or a promise that an agent becomes safe after installation. HANRIA is a coined name with no expansion published here.
The distinction
An agent skill is an instruction and checking layer. It can define vocabulary, inspect a structured mandate, apply ordered clauses, identify an expiry or required human decision, and record a local result. Those checks help an agent decide what it should attempt; they do not control every path by which software can perform the action.
An enforcement runtime is an execution layer. For a protected operation, the runtime would sit on the path to the enrolled tool, credential, transaction, or other action, evaluate the applicable authority, and allow, deny, or escalate before the operation proceeds. Its value depends on the protected surface actually being reachable only through that boundary.
The difference is therefore about where the decision takes effect. A skill influences an agent's behavior. A runtime mediates execution. A successful skill check is evidence of a local decision, not evidence that an external system could not be reached another way.
A practical test
Ask what happens when the caller ignores the result. If the caller can continue by choosing another tool, credential, process, or path, you are looking at advisory guidance. If the protected operation cannot proceed except through the checked boundary, you are looking at an enforcement design.
Keep the two layers separate in documentation and review. The skill can make a mandate explicit and flag authority drift. It cannot turn a convention into a control boundary by itself.
Entry action
npx skills add HANRIA-AI/hanria-skillAfter installation, read the mandate examples and limitations before treating any local decision as meaningful evidence. The skill's checks are useful for structured reasoning and fail-closed guidance; they do not replace an execution boundary.
Honest verdict
Use the skill when you need explicit instruction vocabulary and local checks around delegated authority. If your requirement is to make an unauthorized operation technically unable to proceed, a skill alone is the wrong layer; wait for a separately verified enforcement runtime and its protected-surface evidence.