agentsclimarketplace

Cross binding feature extraction parity testing

Skill kjuhwa/skills-hub/skills/testing/cross-binding-feature-extraction-parity-testing

Generate reference feature vectors from one canonical implementation, store as JSONL, and assert byte-for-byte equality from every other binding (Rust↔Python↔JS↔Go).From its SKILL.md

Install
npx -y skills add kjuhwa/skills-hub --skill cross-binding-feature-extraction-parity-testing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 335 tokens by cl100k_base, as published. Nobody here has run it

Cross Binding Feature Extraction Parity Testing

Trigger: Feature extraction is non-trivial (multi-block sampling, padding, fixed-offset peeks) and MUST be identical across language bindings or the model output drifts.

Steps

  • Pick one binding as canonical (Rust here); add a script that extracts features from every test file and writes JSONL: {path, beg, mid, end, offset_8000, ...}.
  • Commit the reference JSONL into tests_data/features_extraction/.
  • In every other binding, write a test that loads the reference, re-extracts on the same files, and asserts equality.
  • Use tests_data/basic/ (small files spanning 30+ content types) as the input corpus.
  • On mismatch, dump a byte-level diff so the diverging binding is obvious.
  • Run the parity tests in CI for every binding on every commit.

Counter / Caveats

  • Reference is a frozen ground truth; regenerating requires consensus and a CHANGELOG entry.
  • Floating-point precision differences (numpy vs ndarray) can surface as false failures; use approximate equality where appropriate.
  • Test data must stay small (<100KB per file) or commit to git-lfs.
  • Block ordering is order-sensitive — drift in (beg, mid, end) sequence causes silent test pollution.

Source

Extracted from magika (https://github.com/google/magika.git @ main).

Files of interest:

  • python/tests/test_features_extraction_vs_reference.py
  • python/scripts/generate_reference.py:1-50
  • go/magika/features_test.go
  • tests_data/features_extraction/

What ships with it: 1 file

1.1 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,750. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.