Skip to content
Zester
All products

Operational Knowledge

SkillsClaw

Turn recorded workflows and standard operating procedures into production-ready AI skill definitions that agents can actually run.

Domain
Knowledge Operations
Status
In active development
Stack
ReactClaudeVideo AnalysisDocument Parsing

The problem

Operational knowledge is trapped in formats machines cannot use.

The way an organisation actually works lives in SOP documents, training recordings, and the heads of the people who have done the job longest. None of that is executable. Every attempt to automate the work starts by re-deriving knowledge that already exists, which is why automation projects stall before they reach the floor.

How it works

  1. 01

    Take the material that already exists

    Recorded workflows, screen captures, and SOP documents go in as they are. No rewriting the procedure first.

  2. 02

    Analyse the actual procedure

    The system extracts the steps, decision points, inputs, and tools that the recording or document describes.

  3. 03

    Generate a structured skill

    Output is a structured SKILL.md definition: named, scoped, and specific enough for an agent to execute.

  4. 04

    Review and deploy

    A human who knows the process confirms the definition before it goes into production.

Architecture

  1. 01

    Input

    Screen recordings, video walkthroughs, SOP documents, procedure exports

  2. 02

    Extraction

    Transcription, action detection, document parsing, step segmentation

  3. 03

    Structuring

    Decision points, inputs, tool calls, preconditions, success criteria

  4. 04

    Generation

    Structured SKILL.md definition with scope and invocation triggers

  5. 05

    Deployment

    Human review, versioning, publication to the agent runtime

What changes

  • Existing SOP libraries become the starting point for automation rather than an obstacle.

    Verifiable directly: the input is the organisation's own SOP corpus.

  • The written procedure and the executable procedure stop diverging.

    Versioned skill definitions are diffable against their source document.

  • Automation work starts at review rather than at discovery.

    PILOT MEASUREMENT REQUIRED: time from SOP to first deployed skill.

Capabilities

  • Video and screen-recording workflow analysis
  • SOP and procedure document parsing
  • Step, decision point, and tool extraction
  • Structured SKILL.md generation
  • Human review and approval gate
  • Skill versioning and deployment

Who uses it

Operations leads

Encoding a process once instead of retraining it every quarter.

Training and enablement teams

Turning existing SOP libraries into something operational.

Automation engineers

Starting from real procedure rather than a blank definition.

Quality and compliance

Keeping the executable version and the written version in step.

Evidence pending

This page does not fabricate product imagery. The slots below are reserved at their final dimensions and name exactly what is needed.

Product screenshot required

Upload and input screen with a recording queued.

Product screenshot required

Workflow analysis screen showing extracted steps.

Sample output required

A real generated SKILL.md, rendered as it appears in product.

Demo video required

Recording in, deployable skill out.

Have an operation this should be pointed at?