CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cline-sdk

Comprehensive Cline SDK skill for building AI agents. Covers the Agent runtime, ClineCore sessions, custom tools, plugins, events, LLM providers, scheduling, multi-agent teams, and production deployment. Use for any task involving @cline/sdk or its sub-packages.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured router skill: critical rules front-load high-value API specifics, decision trees and indexes make navigation unambiguous, and progressive disclosure is textbook — a lean overview pointing one level deep to real, verified reference files. The main improvement opportunities are deduplicating the overlapping navigation sections and adding one minimal quick-start code snippet.

Suggestions

Consolidate the overlapping navigation (Reading Order, Example Paths, Product Index, and Troubleshooting Index all restate the same file targets) into one routing table plus one troubleshooting list to reduce tokens.

Add a minimal quick-start snippet (e.g. 5-8 lines instantiating an Agent with a provider and one custom tool) so the body has copy-paste executable guidance before deferring to references/agent/api.md.

DimensionReasoningScore

Conciseness

The body is a lean navigation index with no concept explanations and no padding — 'Install with `npm install @cline/sdk`', 'Requires Node.js 22 or later', terse decision trees. It could be tightened: the same file targets appear redundantly across the Reading Order, Example Paths, Decision Trees, Product Index, and Troubleshooting Index sections.

4 / 5

Actionability

Critical Rules give concrete, executable guidance — exact package names, `createTool()` with `snake_case` naming, `lifecycle: { completesRun: true }`, `dispose()`, and precise event-type corrections ('text streaming is "chunk" with payload.type === "text"'). Falls short of 5 because the body contains no complete copy-paste code example (e.g. a minimal `new Agent({...})` snippet), though as an index-only skill the actionable routing to specific files is solid.

4 / 5

Workflow Clarity

The navigation workflow is clearly sequenced: a numbered Reading Order ('1. Start with REFERENCE.md... 2. Then read additional files relevant to your task'), decision trees that resolve API-surface choice by need, and a troubleshooting index for failure modes. No validation checkpoints are needed since the skill routes reads rather than performing destructive or batch operations; the gap to 5 is the absence of any 'verify you loaded the right reference before coding' checkpoint.

4 / 5

Progressive Disclosure

Exemplary one-level-deep structure: the body is a pure index, every referenced path exists on disk (agent/ and clinecore/ each contain REFERENCE.md, api.md, patterns.md, gotchas.md; all concept directories have REFERENCE.md), references are clearly signaled in tables with 'When to Read' guidance, and there is no nested-reference indirection.

5 / 5

Total

17

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit 'Use for...' clause, broad and specific coverage enumeration, and a package-pinned trigger that makes conflict risk minimal. To reach top marks it would need multiple concrete trigger phrases (user-mention variants) and action-oriented phrasing instead of topic enumeration.

Suggestions

Add natural trigger variations to the 'when' clause, e.g. 'Use when the user mentions Cline, the Cline SDK, @cline/sdk, building agents with ClineCore, or any of its sub-packages.'

Lead with one or two concrete actions (e.g. 'Build and deploy AI agents with the Cline SDK: define custom tools, subscribe to streaming events, configure LLM providers') instead of the buzzword-adjacent 'Comprehensive Cline SDK skill'.

DimensionReasoningScore

Specificity

Lists many specific concrete coverage areas — 'the Agent runtime, ClineCore sessions, custom tools, plugins, events, LLM providers, scheduling, multi-agent teams, and production deployment' — which is comprehensive, but these are domain components rather than executable actions, and 'Comprehensive... skill for building AI agents' pads slightly, leaving minor gaps versus the anchor-5 fully action-based example.

4 / 5

Completeness

Both are present: a clear 'what' ('Covers the Agent runtime, ClineCore sessions, custom tools...') and an explicit 'when' ('Use for any task involving @cline/sdk or its sub-packages'). Not a 5 because the 'when' is a single condition rather than multiple concrete trigger phrases like 'or when the user mentions Cline, building agents, or custom tools'.

4 / 5

Trigger Term Quality

Good natural-term coverage: 'Cline SDK', '@cline/sdk', 'Agent runtime', 'ClineCore', plus topic words like tools, plugins, scheduling. A few natural user phrasings are missing (e.g., 'Cline extension', 'Cline bots', file/extension variants), so it sits between anchors 4 and 5, closer to 4.

4 / 5

Distinctiveness Conflict Risk

Clear niche: the trigger is pinned to the '@cline/sdk' package and its sub-packages, which is unambiguous and unlikely to fire for unrelated skills; only the generic opening 'building AI agents' has any overlap risk, and it is immediately qualified by 'Cline SDK'.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

cline/cline

Path

.agents/skills/cline-sdk/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.