openskills-bindings-maintainer

Verify TypeScript and Python bindings compatibility with the openskills-runtime.

68|14|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/Geeksfino/openskills --skill openskills-bindings-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openskills-bindings-maintainer
Source: https://github.com/Geeksfino/openskills/tree/main/.cursor/skills/openskills-bindings-maintainer
Command: npx skills add https://github.com/Geeksfino/openskills --skill openskills-bindings-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that the language bindings for OpenSkills (TypeScript and Python) remain compatible with the core runtime, preventing integration issues and maintaining feature parity.

Core Features & Use Cases

  • Compatibility Checks: Verifies that runtime API changes, feature flag updates, and dependency shifts are reflected correctly in the bindings.
  • Build & Test Verification: Executes build and smoke tests for both TypeScript and Python bindings to confirm their operational integrity.
  • Use Case: When a new feature is added to the OpenSkills runtime, this Skill can be used to automatically check if the TypeScript and Python bindings support it and if their build processes are still functional.

Quick Start

Use the openskills-bindings-maintainer skill to verify the compatibility of the TypeScript bindings with the latest runtime changes.

Frequently Asked Questions about openskills-bindings-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check TypeScript and Python bindings compatibility after a runtime API change?

To verify binding compatibility, execute checks against the `bindings/ts/**` and `bindings/python/**` directories to ensure runtime API changes and feature flag updates are correctly reflected in TypeScript and Python.

What is the best way to keep language bindings in sync with a core runtime?

Keeping language bindings in sync requires running build and smoke tests alongside feature flag management checks to verify that TypeScript and Python bindings maintain feature parity and operational integrity with the core runtime.

Do I need to manually update build configurations for TypeScript and Python bindings?

You do not need to manually update build configurations if you automate compatibility checks, as the process addresses build configurations and smoke verification automatically when runtime API or feature changes occur.

Can I verify feature flag updates across multiple language bindings simultaneously?

Yes, you can verify feature flag updates across multiple language bindings simultaneously by running targeted smoke tests that confirm both TypeScript and Python bindings support the new runtime features and maintain functional build processes.

Why does a runtime feature change break existing language bindings?

A runtime feature change breaks existing language bindings when API updates, dependency shifts, or feature flag modifications are not propagated to the TypeScript and Python integration layers, causing a loss of feature parity and build failures.

When should I run smoke tests for my TypeScript and Python bindings?

You should run smoke tests for TypeScript and Python bindings whenever runtime API or feature changes may impact binding stability, ensuring that build processes remain functional and seamless integration is maintained.