CtrlK
BlogDocsLog inGet started
Tessl Logo

ainativedev/aidevcon-2026-ldn

AI Native DevCon 2026 London — all conference sessions as interactive skills

71

Quality

89%

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

Overview
Quality
Evals
Security
Files

Quality

Content

77%

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

This is a well-crafted reference skill for answering questions about a specific talk. Its greatest strength is actionability — each use case has clear, numbered steps with explicit guardrails around attribution, verbatim quoting, and honesty about gaps. The main weakness is moderate redundancy: the 'read outline → read transcript → quote verbatim → cite lines' pattern is repeated across nearly every section and could be factored into a shared preamble to save tokens.

Suggestions

Factor the repeated 'read outline.md → read transcript.md → quote verbatim → cite line numbers' pattern into a single shared preamble referenced by each task section, reducing token count by ~30%.

Provide the bundle files (outline.md, transcript.md, quotes.md) or at minimum a file listing so progressive disclosure can be fully validated.

DimensionReasoningScore

Conciseness

The skill is reasonably well-structured but contains some redundancy — the grounding rules and the per-task instructions repeat the same 'read outline.md, read transcript.md, quote verbatim' pattern multiple times. Several sections could be consolidated. However, it doesn't explain concepts Claude already knows and most content is task-specific guidance.

2 / 3

Actionability

Each task type (factual Q&A, apply framework, audit, draft artifact, proactive surfacing, teach concepts) has concrete, numbered step-by-step instructions with specific actions (e.g., 'read outline.md first', 'quote verbatim', 'mark clearly as not from talk'). The guidance is specific enough to be directly executable without ambiguity.

3 / 3

Workflow Clarity

Every workflow is clearly sequenced with explicit steps. The audit workflow includes a completeness check ('walk through every dimension — don't skip'), the draft workflow includes a validation step (quote the speaker's prescription before producing output), and multiple workflows include explicit fallback/error handling ('if the answer isn't in the transcript, say so').

3 / 3

Progressive Disclosure

The skill references supporting files (outline.md, transcript.md, quotes.md) appropriately and with clear navigation signals. However, no bundle files were provided, making it impossible to verify these references resolve correctly. The SKILL.md itself is somewhat long and the repeated patterns across sections could benefit from consolidation or a shared preamble, but the section structure is clear.

2 / 3

Total

10

/

12

Passed

Description

100%

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

This is a strong, well-crafted skill description that clearly identifies its narrow domain (a specific conference talk), provides comprehensive trigger terms covering the talk's key topics, and includes an explicit 'Use when' clause. The only minor note is that it doesn't describe what the skill *does* (e.g., 'Answers questions about...') — it only specifies when to use it — but the 'Use when the user asks about' framing implicitly covers the 'what' as well.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete topics: AI slop in open source, drive-by PRs, the new maintainer playbook (with sub-items: issue-first, rate limits, context files, agent skills), the Vouch trust system, OSS vacation, specific project responses (Ghostty/curl/Tldraw), and the Gemini CLI maintainer experience.

3 / 3

Completeness

The description explicitly answers both 'what' (knowledge about Wotherspoon's talk covering AI slop, maintainer strategies, trust systems, specific project responses) and 'when' with a clear 'Use when the user asks about...' clause listing comprehensive trigger scenarios.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms a user would say: 'Jack Wotherspoon', 'AI slop', 'open source', 'drive-by PRs', 'maintainer playbook', 'Vouch trust system', 'Ghostty', 'curl', 'Tldraw', 'Gemini CLI', 'guardrails', 'context files', 'agent skills'. These are highly specific and natural keywords someone familiar with this talk would use.

3 / 3

Distinctiveness Conflict Risk

This is extremely niche — it's about a specific person's specific talk with named concepts (Vouch trust system, OSS vacation) and named projects. It is highly unlikely to conflict with any other skill.

3 / 3

Total

12

/

12

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

9

/

11

Passed

Reviewed

Table of Contents