CtrlK
BlogDocsLog inGet started
Tessl Logo

deepnote

Use when a task mentions Deepnote, the connected Deepnote app, Deepnote OAuth connection, Deepnote docs, projects, workspaces, notebooks, blocks, integrations, or notebook runs.

61

Quality

72%

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 ./plugins/deepnote/skills/deepnote/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-3

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

A well-organized, concise router with clean progressive disclosure and a real bundled reference. It is held back by delegated execution detail and the absence of explicit validation checkpoints for its stateful actions.

Suggestions

Add an explicit pre-flight validation step for stateful actions (e.g. 'Read with get_notebook before editing; confirm the target ID before create_run') to give workflow clarity a checkpoint loop.

Briefly inline the key invocation detail or signature for the most common tools so the router is executable without the unbundled specialist skills, or confirm where the specialist skills live.

DimensionReasoningScore

Conciseness

The body is lean — a capability map, route-by-intent table, routing defaults, and guardrails — with no padding or explanation of concepts Claude already knows, matching the 'every token earns its place' anchor.

3 / 3

Actionability

It names concrete tools ('get_me', 'search', 'list_projects', 'get_notebook', 'create_run') and maps intents to them, but detailed execution is delegated to unbundled specialist skills ('deepnote-notebooks', 'deepnote-notebook-editing'), leaving incomplete executable guidance.

2 / 3

Workflow Clarity

Routing Defaults gives a clear 6-step sequence and guardrails add safety notes, but for persistent actions (runs, creates) there is no explicit validation/verification checkpoint, which caps workflow clarity at 2 per the destructive-operations guideline.

2 / 3

Progressive Disclosure

SKILL.md is a clean overview/router; the one bundled reference (references/workspace-summary.md) exists, is one level deep, and is clearly signaled via a markdown link in the route-by-intent table, matching the well-organized overview anchor.

3 / 3

Total

10

/

12

Passed

Description

72%Weight 40%Scale 1-3

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, distinct trigger description with excellent natural keyword coverage, weakened only by omitting any statement of what the skill actually does. Adding a short capability clause would lift completeness and specificity.

Suggestions

Prepend a one-clause statement of capability, e.g. 'Routes Deepnote tasks to the connected Deepnote app tools and specialist skills.' so the description answers 'what' as well as 'when'.

Add a few concrete verbs (inspect, run, edit, map integrations) alongside the enumerated objects to raise specificity from domain-naming to action-naming.

DimensionReasoningScore

Specificity

The description enumerates concrete domain objects ('Deepnote app, Deepnote OAuth connection, Deepnote docs, projects, workspaces, notebooks, blocks, integrations, or notebook runs') but states no actions or capabilities, landing between the vague anchor 1 and the action-naming anchor 2.

2 / 3

Completeness

It explicitly answers 'when' via the 'Use when a task mentions...' clause but never states 'what' the skill does, so it cannot reach the both-what-and-when anchor 3 yet stays above the both-weak anchor 1.

2 / 3

Trigger Term Quality

It covers natural terms a user would say — 'Deepnote', 'projects', 'workspaces', 'notebooks', 'blocks', 'integrations', 'notebook runs', 'Deepnote docs', 'OAuth connection' — with good breadth of variations, matching the high-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

The Deepnote-specific triggers ('Deepnote OAuth connection', 'Deepnote docs', 'notebook runs') carve a clear niche that is unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.