What counts as a runtime change surface?

Any API surface modification, feature flag introduction/removal, or dependency topology change that bindings rely on and could alter behavior or compilation.

How should I verify compatibility between runtime and bindings?

Run the TS and Python binding build/test pipelines, perform smoke verification, and ensure lockfiles and manifests are consistent; document results in a compatibility matrix.

What qualifies as a breaking change and what migration steps are expected?

Changes that require code updates in bindings or consumer code to function correctly. Provide explicit migration steps, update guides, and communicate impact to downstream teams.

openskills-bindings-maintainer

npx machina-cli add skill Geeksfino/openskills/openskills-bindings-maintainer --openclaw

Files (1)

SKILL.md

1.2 KB

OpenSkills Bindings Maintainer

Use this skill when runtime APIs, features, or dependency topology changes may affect bindings.

Scope

bindings/ts/**
bindings/python/**
runtime crate feature interactions affecting bindings

Workflow

Identify runtime change surface (API, features, dependencies).
Check both bindings for feature/compile assumptions.
Verify build and smoke tests for each binding.
Confirm lockfile and manifest consistency where applicable.

TS Binding Checks

cd bindings/ts
npm install
npm run build

Python Binding Checks

Use project-standard build/test commands for Python bindings and confirm import/runtime behavior.

Guardrails

Avoid introducing plugin/build-tool dependencies into default binding paths unless intentional.
Keep generated files and lockfiles aligned with project policy.

Output Format

Compatibility matrix (runtime vs TS/Python)
Breaking changes
Required migration steps
Verification evidence

Source

git clone https://github.com/Geeksfino/openskills/blob/main/.cursor/skills/openskills-bindings-maintainer/SKILL.mdView on GitHub

Overview

OpenSkills Bindings Maintainer ensures compatibility between openskills-runtime and language bindings for TypeScript and Python. It manages feature flags, build configurations, and smoke verification to prevent breaking changes when the runtime evolves. The scope includes bindings/ts/**, bindings/python/**, and runtime feature interactions that affect bindings.

How This Skill Works

When runtime changes surface (API, features, or dependencies), identify the impacted bindings and feature/compile assumptions. Review TS and Python bindings for compatibility, run the appropriate build and smoke tests, and address any mismatches. Update lockfiles and manifests as needed, and produce a compatibility matrix, note breaking changes, migration steps, and verification evidence.

When to Use It

Runtime API, feature, or dependency changes that could affect bindings (TS or Python)
New feature flags or topology changes impacting binding behavior
Build or CI failures in TS or Python bindings after runtime updates
Introductions of new runtime dependencies that bindings share
Post-change verification to confirm lockfile/manifest consistency

Quick Start

Step 1: Identify the runtime change surface (API, features, dependencies) that could affect bindings
Step 2: Inspect TS and Python bindings for feature/compile assumptions and update if needed
Step 3: Run builds and smoke tests for both bindings; align lockfiles/manifests and record verification evidence

Best Practices

Avoid introducing plugin or non-default build-tool dependencies into the default binding paths unless intentional
Keep generated files and lockfiles aligned with project policy
Run both TS and Python bindings builds and smoke tests after any runtime change
Document any breaking changes and provide clear migration steps for downstream users
Produce a compatibility matrix mapping runtime changes to TS/Python bindings

Example Use Cases

In bindings/ts, run npm install and npm run build after a runtime API change to surface type/ABI mismatches
For Python bindings, execute the project-standard build/test commands and validate import/runtime behavior
Update and synchronize lockfiles (package-lock.json/yarn.lock, pyproject.toml/poetry.lock) across bindings
Generate a compatibility matrix comparing runtime vs TS/Python bindings and flag breaking changes
Publish migration steps and examples to guide downstream teams on updating bindings

Frequently Asked Questions

Add this skill to your agents