CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

talk-ruiz-agents-on-canvas-tldraw

Use when the user asks about Steve Ruiz's AI Native DevCon talk on tldraw, Make Real, annotations as prompt input, canvas workflows, tldraw computer, and agents collaborating on an infinite canvas.

Quality

74%

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/aidevcon/skills/talk-ruiz-agents-on-canvas-tldraw/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 lean, well-structured instruction skill with a clear grounding workflow and explicit verification checkpoints, appropriate for a reference-type skill. Its one material weakness is that the entire workflow depends on three files that are absent from the bundle, undermining both navigation and executability.

Suggestions

Include the referenced files (outline.md, quote.md, transcript.md) — or place them in a references/ directory — so the grounding workflow ('Read outline.md first... verify against transcript.md') is actually executable.

Trim the 'Core Concepts' list, which duplicates the topic enumeration already in the description, or merge it into the grounding rules.

Add one short worked example (e.g., a Q&A with a cited transcript line ID) to make the citation and attribution rules concrete.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and assumes Claude's competence — no concept explanations, and rules like 'Preserve transcription artifacts in direct quotations and explain likely corrections separately' add genuinely non-obvious value. Not 5: the 'Core Concepts' list ('Make Real, Drawings and annotations as prompt input, ...') duplicates the description's topic enumeration and could be trimmed.

4 / 5

Actionability

Concrete, instruction-only guidance throughout: 'Read `outline.md` first to locate the relevant section', 'verify against `transcript.md` when precision matters', 'cite the transcript line IDs when available', plus three distinct usage modes (Factual Q&A, Apply, Compare). Not 5: there are no worked examples of an answer or comparison, and the workflow presumes source files the bundle does not contain.

4 / 5

Workflow Clarity

A clear sequence is present (outline.md to locate → quote.md for excerpts → transcript.md for verification) with explicit checkpoints such as 'If the transcript does not support a claim, say that the talk does not address it' and speaker-attribution correction rules. Not 5: verification is conditional ('when precision matters') rather than a mandatory validate-fix-retry feedback loop. No destructive/batch cap applies to this Q&A-style skill.

4 / 5

Progressive Disclosure

The body's references to `outline.md`, `quote.md`, and `transcript.md` are clearly signaled and one level deep, but scoring against the actual bundle structure shows none of these files exist (no references/, scripts/, or assets/ directories), so the well-signaled split cannot actually be navigated. This lands between anchor 2 (broken/inaccessible reference structure) and anchor 4 (well-signaled, verifiable references).

3 / 5

Total

15

/

20

Passed

Description

67%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 has excellent trigger terms and distinctiveness — a user asking about this specific talk would reliably match it — but it states only the 'when' and never says what the skill does (answer questions, apply concepts, compare talks), leaving the 'what' implicit and its action surface unstated.

Suggestions

Add an explicit 'what' statement before the 'Use when' clause, e.g., 'Answers questions about, applies concepts from, and compares Steve Ruiz's AI Native DevCon talk on tldraw...' so both what and when are stated.

Name the skill's concrete capabilities (factual Q&A grounded in the transcript, applying talk concepts to the user's context, comparing with other DevCon sessions) instead of only enumerating topics.

Optionally add a broader catch phrase such as 'agents on the canvas' or 'canvas + AI demos' to widen the natural trigger surface without harming distinctiveness.

DimensionReasoningScore

Specificity

The domain is richly named ('tldraw, Make Real, annotations as prompt input, canvas workflows, tldraw computer, and agents collaborating on an infinite canvas') but no concrete skill actions are stated — the only action verb is the user's 'asks about', leaving the skill's actions minimal and generic. Anchor 3 does not fit because it requires 1-2 concrete actions the skill performs, which are absent.

2 / 5

Completeness

Only the 'when' is present ('Use when the user asks about...'); the 'what' is implied by the enumerated topics but never explicitly stated, so the description sits between anchor 2 ('only when present without what' — here the topic list is far richer than that anchor's vague example) and anchor 4 (both what and when explicit, which the missing 'what' statement precludes).

3 / 5

Trigger Term Quality

'Steve Ruiz', 'AI Native DevCon talk', 'tldraw', 'Make Real', 'canvas workflows', and 'agents collaborating on an infinite canvas' are exactly the natural phrases a user would say when needing this skill, covering speaker, event, product, and concept variations. Not 4: no meaningful natural term for this niche is missing.

5 / 5

Distinctiveness Conflict Risk

Naming the specific speaker and event ('Steve Ruiz's AI Native DevCon talk on tldraw') establishes a clear niche with distinct triggers and minimal conflict risk with other skills. The only conceivable overlap is a bare reference to 'the DevCon canvas talk', which the speaker name disambiguates.

5 / 5

Total

15

/

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

jscraik/Agent-Skills

Path

Plugins/aidevcon/skills/talk-ruiz-agents-on-canvas-tldraw/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.