geeksfino/openskills · Archived

openskills-bindings-maintainer

Maintain compatibility between openskills-runtime and language bindings (TypeScript, Python), including feature flags, build configuration, and smoke verification.

First seen Mar 4, 2026

Installation

$ npx skills add geeksfino/openskills --skill openskills-bindings-maintainer

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from geeksfino/openskills · top by installs.

npx skills add geeksfino/openskills

Browse all from geeksfino/openskills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 60
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,227 B
  • docs SUMMARY.md 201 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

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

  1. Identify runtime change surface (API, features, dependencies).
  2. Check both bindings for feature/compile assumptions.
  3. Verify build and smoke tests for each binding.
  4. 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