Skills Library

A skill is a generated, named workflow definition that wraps a compute call for a specific problem. You describe your industry and your use case in plain language; the generator picks the matching physics domain, selects the operators (with KO42 mandatory), suggests the input variables, and hands you a complete skill definition — description, operator list, zeqConfig, generated client code, and a Markdown write-up — all pointed at POST /api/zeq/compute.

The point is that you don't have to know the physics. The operators encode the domain knowledge; you supply variable names and values, and the framework composes the equation.

Where it fits

Layer	What	This page
The language	Operators — the verbs	—
The compute surface	Hosted API — POST /api/zeq/compute	—
Skill generator	Skill	here

A skill is the highest-level reusable artefact the generator produces: one call to /api/skills/generate returns a self-contained definition you can save, share, and run against the compute API.

Skill shape

The generator returns a definition like this (fields abbreviated):

{
  "skillId":   "zeq-aerospace-9c41f2ab",
  "name":      "orbital-transfer-planner",
  "industry":  "Aerospace",
  "domain":    "Classical Mechanics",
  "operators": ["KO42", "NM21", "NM23"],
  "description": "…what the skill computes and which operators carry it…",
  "zeqConfig": {
    "endpoint":         "/api/zeq/compute",
    "domain":           "classical-mechanics",
    "suggestedInputs":  { "mass": 5.972e24, "r": 6.78e6 },
    "mandatoryOperator": "KO42"
  },
  "code":      "…generated client snippet that calls /api/zeq/compute…",
  "markdown":  "…human-readable write-up of the skill…"
}

The skill's zeqConfig.endpoint is /api/zeq/compute — that is how a skill runs: the generated code calls the same compute surface every SDK wraps, with KO42 always in the operator list.

Generating a skill

curl -X POST https://zeqsdk.com/api/skills/generate \
  -H "Content-Type: application/json" \
  -d '{ "industry": "aerospace", "useCase": "plan a Hohmann transfer burn" }'

Supply an industry (one of healthcare, aerospace, quantum, ai_ml, finance, biotech, energy, manufacturing, environmental, defense, education, custom) and a useCase (free text, min 5 characters). The response is the full skill definition above, including the generated code and Markdown.

Generating a skill definition is free — no subscription required. A subscription is required to call the compute API the generated skill targets.

Browsing existing skills

• GET /api/skills — list the skill catalogue (filterable), plus the generator endpoint.
• GET /api/skills/:id — fetch a single catalogued skill.

Composes with

• Operators — the verbs a skill selects from.
• The 7-step Wizard protocol — the lifecycle every compute call runs.
• Compute API — the surface a generated skill calls.

File map

• apps/zeq-dev/public/apps/skills/ — the live UI
• shared/api-core/src/routes/skills.ts — POST /api/skills/generate, GET /api/skills, GET /api/skills/:id