Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
ffi - Skill - OpenSmartRoute
Skillv1.0.0
ffi
Imageflow offers a very stable ABI, focused on sending/recieving JSON and byte buffers in conjuction with an endpoint string. There are wrappers in C# (the main one), go, node, elixr, and more. Keepin
Instruction file imported from imazen/imageflow (.cursor/rules/ffi.mdc). Copyright stays with the author.
Imageflow offers a very stable ABI, focused on sending/recieving JSON and byte buffers in conjuction with an endpoint string. There are wrappers in C# (the main one), go, node, elixr, and more. Keeping these wrappers up-to-date with the latest JSON features is difficult, and the nature of the JSON graph structure makes it require simpler API wrappers.
For the HTTP-like endpoint names, see @/imageflow_core/src/context_method.rs
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/imazen-imageflow-ffi-rule/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
imazen-imageflow-ffi-rule.ocm.jsonjson
{
"ocm": "1",
"id": "imazen-imageflow-ffi-rule",
"kind": "skill",
"name": "ffi",
"description": "Imageflow offers a very stable ABI, focused on sending/recieving JSON and byte buffers in conjuction with an endpoint string. There are wrappers in C# (the main one), go, node, elixr, and more. Keeping these wrappers up-to-date with the latest JSON features is difficult, and the nature of the JSON graph structure makes it require simpler API wrappers.",
"publisher": "imazen",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"github-cursor-rules"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Imageflow offers a very stable ABI, focused on sending/recieving JSON and byte buffers in conjuction with an endpoint string. There are wrappers in C# (the main one), go, node, elixr, and more. Keeping these wrappers up-to-date with the latest JSON features is difficult, and the nature of the JSON graph structure makes it require simpler API wrappers."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-cursor-rules",
"repository": "https://github.com/imazen/imageflow",
"path": ".cursor/rules/ffi.mdc",
"ref": "f49ec638d60d06911c7232309bba85578a0812ea",
"url": "https://github.com/imazen/imageflow/blob/f49ec638d60d06911c7232309bba85578a0812ea/.cursor/rules/ffi.mdc",
"key": "imazen/imageflow/.cursor/rules/ffi.mdc"
}
},
"instructions": "Imageflow offers a very stable ABI, focused on sending/recieving JSON and byte buffers in conjuction with an endpoint string. There are wrappers in C# (the main one), go, node, elixr, and more. Keeping these wrappers up-to-date with the latest JSON features is difficult, and the nature of the JSON graph structure makes it require simpler API wrappers. \n\nFor the HTTP-like endpoint names, see @/imageflow_core/src/context_method.rs \n\nFor the FFI ABI, read @/imageflow_abi/src/lib.rs and [imageflow_default.h](mdc:bindings/headers/imageflow_default.h)",
"cost": {
"context_tokens": 137
}
}
Fetch it by URL: GET /api/v1/registry/imazen-imageflow-ffi-rule/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.