agentleFS
Sign inStart free
feichai0017feichai0017/QuillSQL/.agents/skills/python-binding/SKILL.md

python-binding

Skill337 starsChanged 18 days agoApache-2.0View on GitHub

Modify OrbitKV PyO3 APIs, native client ownership, Python type stubs or wheel packaging. Use for native binding and installed-artifact changes in this repository.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read AGENTS.md from the Git root.

    line 8
  2. Distinctive:

    Use the gate table in AGENTS.md: default Python tests must remain source-only.

    line 31
  3. Very specific:

    Use scripts/build-wheel.sh for a complete installed artifact.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OrbitKV Python bindings and adapters

Read AGENTS.md from the Git root. Keep Python responsible for framework callbacks, layout inspection, GPU allocations and ownership handoff; shared cache state machines, batching, waiting and execution belong to the existing Rust owners.

  • Public bindings: python/src/lib.rs, python/src/client.rs and python/orbitkv/orbitkv.pyi. Update stubs when an exposed API changes. Verify actual call sites rather than restoring removed aliases or client facades.
  • Common client ownership: crates/orbitkv-channel/src/cache_client.rs.
  • Engine callback changes: use .agents/skills/engine-integration/SKILL.md and docs/adapters.md; release targets and current qualification are distinct.
  • Model/layout identity and hybrid recovery are shared contracts. Do not equate compatible API shapes with cross-engine byte compatibility.
  • register_context_batch returns an opaque native GpuRegistration and takes client-local CUDA ordinals and retained tensors. Publish calls save(registration, saves); adapters capture that object at producer handoff, not when a delayed queue worker executes. Retired or foreign-client authority is rejected. The object retains exporters but is neither a page-slot generation nor a device completion receipt. Resolve their full physical GPU UUIDs; the native owner retains the Manager's resolved ordinal for Publish/Restore. Do not reuse the client's ordinal on the Manager or convert a UUID into an ordinal with physical nvidia-smi ordering. Lifecycle protocol 8 requires matching installed client and Manager artifacts.

Use the gate table in AGENTS.md: default Python tests must remain source-only; native lifecycle changes need process integration, and consumed adapter changes need the relevant engine correctness/restart gate. Run benches/tests when changing benchmark helpers. Put runtime outputs outside the checkout.

Use scripts/build-wheel.sh for a complete installed artifact; maturin develop is a development build. See docs/releases.md for CUDA variants, bundled native dependencies and installed-package checks. Freeze native artifacts before GPU tests: Cargo can restage shared libraries used by live Managers.

Download now (ZIP)

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. novitalabs/pegaflow★ 214same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free