CtrlK
BlogDocsLog inGet started
Tessl Logo

setup-python-tools

Pyodide Python tools for an already-approved in-app useAtlasChat UI. EOS sidebar Python tools run from agent CDF config — do not vendor Pyodide. Triggers: Pyodide, pythonRuntime, usePyodideRuntime, runPythonCode.

58

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/setup-python-tools/SKILL.md
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 skill body is a tight, highly actionable integration guide with complete executable code and a clear five-step workflow. Its main gaps are the absence of an explicit verification/test checkpoint and a few explanatory sentences that could be trimmed.

DimensionReasoningScore

Conciseness

The body is largely lean — code blocks, a compact API table, and short step prose — with only minor justifying sentences ('The user shouldn't send messages before the runtime is ready.') that explain rather than instruct; not quite the every-token-earns-its-place of a 5.

4 / 5

Actionability

It provides copy-paste-ready, executable guidance throughout: exact per-package-manager install commands, complete TSX for the hook, a full return-field API table, loading/error UI code, useAtlasChat wiring, and input-disable code covering the common cases.

5 / 5

Workflow Clarity

Five steps are clearly sequenced (understand → install → set up hook → wire into useAtlasChat → disable input) with a Step 1 prerequisite checkpoint; there is no explicit 'verify the runtime loads / test a Python tool call' validation step, but this is additive integration (not destructive or batch), so the cap does not apply.

4 / 5

Progressive Disclosure

Content is well-organized into clearly signaled sections with a compact inline API table; there are no external bundle files or references (none exist), and while the ~145-line body is over the 50-line simple-skill threshold, the inline material is appropriately placed with only minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

55%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 specific and niche-focused with explicit trigger terms, but those triggers are technical identifiers rather than natural user phrases, and it flags overlap with a sibling skill. It clearly answers both what and when, though the 'what' is dense with project-internal jargon.

Suggestions

Rewrite the trigger list as natural user phrasing (e.g., 'Use when adding Python tool execution to an Atlas/EOS chat, or when the user mentions Pyodide or running Python in the browser') alongside the identifier terms.

Lead with a plain-language capability statement ('Runs agent-defined Python tools client-side via Pyodide in the Atlas chat UI') before the CDF/EOS jargon.

Clarify the boundary with integrate-fusion-agent up front so the skill is less likely to trigger for the non-Pyodide sidebar path.

DimensionReasoningScore

Specificity

Names the domain ('Pyodide Python tools for...useAtlasChat UI') and one concrete behavior ('Python tools run from agent CDF config'), but lists only a single action rather than a comprehensive set; 'do not vendor Pyodide' is a constraint, not a capability.

3 / 5

Completeness

It answers 'what' (Pyodide Python tools running from agent CDF config for useAtlasChat) and provides explicit trigger guidance ('Triggers: ...'), so it clears the missing-trigger cap; the 'when' is a bare identifier list rather than a 'Use when...' clause and the 'what' is jargon-heavy, so not a 5.

4 / 5

Trigger Term Quality

The listed triggers ('Pyodide, pythonRuntime, usePyodideRuntime, runPythonCode') are identifier-style technical jargon a user would only say inside this specific codebase, missing the natural phrases users say; this is below the midpoint toward score 1's 'only technical jargon' anchor.

2 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (client-side Pyodide for the Atlas/EOS chat) with distinct identifiers, but explicitly notes overlap with the sibling 'integrate-fusion-agent' skill, indicating minor conflict risk with closely related skills rather than minimal risk.

4 / 5

Total

13

/

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.