cef-client-sdk

Bridge external applications to CEF agent services using the @cef-ai/client-sdk.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/CEF-AI/skills --skill cef-client-sdk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cef-client-sdk
Source: https://github.com/CEF-AI/skills/tree/main/skills/clientsdk
Command: npx skills add https://github.com/CEF-AI/skills --skill cef-client-sdk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External applications such as GitHub Actions, demos, and test harnesses need to securely connect to CEF agent services. The @cef-ai/client-sdk provides a standardized, inline-runtime bridge to push events, query cubbies, subscribe to streams, and manage wallets without embedding runtime logic inside the V8 isolate.

Core Features & Use Cases

  • Connect external code to CEF agent services using a ClientContext, wallet signer, and a ClientSdk instance to orchestrate events, cubby queries, and stream publishing.
  • Create and manage agreements, publish events, query cubbies, and subscribe to streams across workflows, tests, and demos.
  • Use in GitHub Actions, backend scripts, or demos to quickly prototype and integrate CEF capabilities with external codebases.

Quick Start

Install the @cef-ai/client-sdk, assemble a ClientContext with agentService, workspace, and stream, configure a wallet and ClientSdk, and begin sending events.

Frequently Asked Questions about cef-client-sdk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect external code to CEF agent services?

To connect external code to CEF agent services, use the @cef-ai/client-sdk to assemble a ClientContext with agentService, workspace, and stream, then configure a wallet signer and ClientSdk instance to orchestrate events, cubby queries, and stream publishing.

What is the best way to push events and query cubbies from a GitHub Actions workflow?

The best way to push events and query cubbies from GitHub Actions is using the @cef-ai/client-sdk, which provides a standardized, fully inline-runtime bridge to securely connect external applications to CEF agent services without embedding runtime logic inside the V8 isolate.

Does the CEF client SDK require a wallet signer to manage agreements?

Yes, the CEF client SDK requires a wallet signer to manage agreements. You must configure the wallet alongside a ClientSdk instance and a ClientContext to successfully create agreements, publish events, and subscribe to streams across your workflows.

Why does the client SDK require an eventRuntimeUrl and garUrl?

The client SDK requires an eventRuntimeUrl and garUrl because it enforces a fully inline runtime to bridge external applications to CEF agent services. These endpoints are mandatory to securely push events, query cubbies, and subscribe to streams.

Can I use the client SDK to subscribe to streams in backend scripts and demos?

Yes, you can use the client SDK to subscribe to streams in backend scripts and demos. It supports patterns for stream data, event publishing, and cubby queries across GitHub Actions, test harnesses, backends, and rapid prototypes.

What are the limitations of using an inline runtime bridge for CEF integration?

A limitation of using this inline runtime bridge is that it requires mandatory eventRuntimeUrl and garUrl configurations, and it explicitly prevents embedding runtime logic directly inside the V8 isolate, restricting certain inline execution patterns.