← SkillsProof case studyInteractive example

SkillsProof · Interactive demo

Every step. Every fault. One glance.

Select a stage to inspect its evidence without changing the next required check.

Example data · No commands are executed

About this example data

This browser demo uses fixed example data. It does not read your skills, run SDK commands or contact Tessl. All security findings are synthetic. The nine stages describe the intended lifecycle; several still need implementation or live integration proof.

SKILLS SDK

improve-agent-native

Local Needs attention

Demo scenario

2 passed · 1 needs review · 6 awaiting proof

Gate 03 / 09Next required

Security

Review required · 1 critical · 2 high (synthetic)

Full security receipt missing or malformed. Inspect findings before continuing.

Visual reference · no executable command

Tessl Registry Unavailable

No cached registry evidence in this fixture.

Registry evidence stays separate from local checks. A registry score cannot pass a local gate.

What each gate should prove

These are target evidence requirements, not a claim that every route is executable end to end.

  1. Identity

    The exact source package is known and bound to its package ID, source revision and content digest, with provenance and ownership recorded.

  2. Validation

    The plugin and its skills meet the applicable structural, metadata, resource, reference and presentation requirements.

  3. Security

    Applicable security and permission checks have acceptable evidence, with no unresolved risk blocking evaluation or release.

  4. Eval prep

    Scenarios, assertions, scoring criteria and scorer calibration are ready; comparison settings and budgets are frozen.

  5. Local eval

    Baseline and candidate have been compared under matched local conditions, and any accepted winner is selected and frozen.

  6. Cloud eval

    Cloud refinement has been compared against the accepted local winner under matched cloud conditions, with a recorded selection decision.

  7. Staging

    The selected release archive, required resources, presentation, recovery plan and registry preparation are verified, including the final scoped security check.

  8. Publication

    The authorised, exact checked version has been published to the selected registry and verified by readback.

  9. Runtime

    That version has been installed and its discovery, activation and behaviour verified, with rollback evidence where applicable.

Security remains active throughout, including a final scoped check at Staging. A changed candidate invalidates affected evidence and dependent stages; independently valid upstream evidence can remain. Publication and Runtime require readback and behaviour evidence from the registry and host adapters.