Cline SDK Skill

Why it's ranked here

The skill is useful because it captures distinctions that commonly break integrations: runtime selection, incompatible event shapes, separate plugin models, tool policy timing, and different result formats. Its value comes from precise operational guidance, not executable features.

What's good

The documentation pairs quick decisions with deeper API, pattern, and troubleshooting material. It clearly separates lightweight in-memory agents from persistent sessions, explains approval behavior, identifies cleanup requirements, and warns that custom tool timeout and retry metadata are not automatically enforced.

Tradeoffs

This is reference material, not the SDK runtime, so users must install the SDK separately. The full runtime requires Node.js 22 or later. Browser use needs a lower-level package, and developers must navigate two event systems, two plugin shapes, and distinct result formats.

How to use it well

Use it when an AI coding assistant is implementing or debugging a Cline-based TypeScript agent, especially around tools, streaming, persistence, plugins, or production controls. Start with the runtime decision tree, then load only relevant references. It does not replace the SDK package, provider credentials, application tests, or full hosted documentation.

Observed

License

Apache License 2.0

Artifact type

Markdown reference skill with TypeScript API examples

Skill install surface

Install through npx skills, or clone and symlink into an assistant skill directory

SDK install surface

npm package @cline/sdk

Runtime interfaces

Lightweight in-memory Agent library and persistent ClineCore session library

Runtime requirement

ClineCore and @cline/core require Node.js 22 or later

Browser support

Browser-compatible Agent usage is available through @cline/agents

Assistant support

Cline CLI, Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Goose, OpenCode, and Windsurf