CtrlK
BlogDocsLog inGet started
Tessl Logo

create-client-tool

Scaffolds an AtlasTool for an already-approved in-app useAtlasChat UI. For EOS sidebar tools, use integrate-fusion-agent (createAgentAction) instead. Triggers: AtlasTool, useAtlasChat tool, in-app atlas client tool.

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

The body is a tight, actionable 4-step guide with executable code at each step and a useful TypeBox reference table. It loses points only on the lack of an explicit verification checkpoint and a small amount of conceptual framing in the Background section.

Suggestions

Add a short "Verify" checkpoint after Step 3 (e.g., typecheck or confirm the tool appears in the agent's tool list) to push workflow_clarity toward 5.

Tighten or move the Background paragraph into a one-line lead-in so the body opens directly with the workflow, improving conciseness.

DimensionReasoningScore

Conciseness

Mostly lean with copy-paste-ready code and a compact TypeBox table; the Background section adds some conceptual framing that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready TypeScript/TSX for defining an AtlasTool, wiring it into useAtlasChat, and rendering toolCalls, covering the common case.

5 / 5

Workflow Clarity

Four clearly sequenced, labeled steps with a conditional final step and path-adjustment guidance; lacks an explicit compile/verify checkpoint, though the operation is additive and non-destructive.

4 / 5

Progressive Disclosure

Well-organized into headered sections with a compact reference table; no bundle files exist so all content is inline, which is appropriate but slightly exceeds the simple-skill threshold.

4 / 5

Total

17

/

20

Passed

Description

82%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.

The description is concise, third-person, and clearly answers both what the skill does and when to trigger it, with strong disambiguation against a sibling skill. Its main limitation is specificity — it names a single scaffolding action rather than enumerating several concrete capabilities.

Suggestions

List 2-3 concrete actions beyond "Scaffolds" (e.g., defines the TypeBox parameter schema, wires the tool into useAtlasChat, renders tool-call results) to lift specificity from 3 toward 5.

Add a couple of natural synonyms or a file/path cue (e.g., "atlas tool", "client tool") to round out the trigger-term coverage.

DimensionReasoningScore

Specificity

Names the AtlasTool domain with one concrete action ("Scaffolds an AtlasTool") plus a sibling-skill redirect, but does not enumerate several specific actions.

3 / 5

Completeness

Explicitly states what ("Scaffolds an AtlasTool for an already-approved in-app useAtlasChat UI") and when (concrete "Triggers:" enumeration), satisfying both halves with concrete trigger phrases.

5 / 5

Trigger Term Quality

Explicit "Triggers:" list (AtlasTool, useAtlasChat tool, in-app atlas client tool) plus inline API names gives good keyword coverage, missing a few synonyms/extensions.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (approved in-app useAtlasChat AtlasTool) and an explicit cross-skill redirect ("For EOS sidebar tools, use integrate-fusion-agent... instead"), minimizing conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository
cognitedata/builder-skills
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.