ClawHub

Agent Desktop Ffi

v1.0.0

C-ABI bindings over agent-desktop's PlatformAdapter. Consumers (Python ctypes, Swift, Node ffi-napi, Go cgo, C++, Ruby fiddle) link libagent_desktop_ffi.{dyl...

⭐ 0· 16·0 current·0 all-time
by@lahfir
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description claim C-ABI bindings and the included docs explain building, linking, ownership, threading, and error handling. There are no unrelated env vars, binaries, or installs requested — everything asked for (cargo build, header, linking) fits the stated purpose.
✓
Instruction Scope
SKILL.md and reference files limit runtime instructions to local build/link steps and safe usage patterns (main-thread rule, allocation/free contracts, last-error semantics). No instructions to read unrelated files, send data externally, or access unrelated credentials. The docs explicitly call out a macOS permission inheritance concern (AXIsProcessTrusted) as a warning.
✓
Install Mechanism
No install spec or external downloads are present; the skill is instruction-only and expects consumers to build the cdylib locally via cargo. This is low risk and proportionate to the task.
✓
Credentials
No environment variables, credentials, or config paths are required. The references explain runtime constraints but do not request secrets or unrelated tokens.
✓
Persistence & Privilege
always is false and the skill does not request persistent system presence or modify other skills' configs. Autonomous invocation defaults are unchanged and no elevated privilege is requested.
Assessment
This skill is an on-disk FFI usage and build guide rather than executable code fetched at install time, and its requirements are reasonable for that purpose. Before integrating: build the cdylib locally with the documented --profile release-ffi to preserve panic/unwind guarantees; pin the library version you link against because the ABI is unstable before 1.0; follow the ownership/free rules exactly to avoid memory errors; and on macOS be aware that granting Accessibility (AXIsProcessTrusted) is granted to the hosting interpreter (python/node/etc.) — granting it to one process that dlopens this library effectively grants it to other code using the same interpreter. If you need higher assurance, inspect the built binary and the committed header in your own repo rather than relying on an external binary.

Like a lobster shell, security has layers — review code before you run it.

latestvk97aq920184ehahmsmey4egxj985196v

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments