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 skill for answering questions about a specific talk, with strong actionability and workflow clarity across five distinct use cases. The grounding rules are excellent guardrails that prevent hallucination and enforce source fidelity. The main weaknesses are moderate verbosity (repeated 'verbatim quote' instructions across sections) and the inability to verify the referenced bundle files (outline.md, transcript.md, quotes.md) that the skill depends on.

Suggestions

Consolidate the repeated 'quote verbatim from transcript.md' instruction into the grounding rules section once, then reference it from each workflow (e.g., 'Follow grounding rule #2') to reduce redundancy.

Consider splitting the five detailed use-case workflows into a separate WORKFLOWS.md file, keeping SKILL.md as a concise overview with pointers to each workflow.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some verbose phrasing, especially in the opening summary paragraph and the detailed audit walkthrough. The grounding rules and workflow sections are well-structured but could be tightened — e.g., the seven-dimension audit procedure repeats 'verbatim quote' instructions multiple times across sections.

2 / 3

Actionability

The skill provides highly concrete, step-by-step procedures for five distinct use cases (apply framework, audit, factual Q&A, proactive surfacing, teach/explain). Each workflow has numbered steps with specific actions like 'read outline.md → locate section → read transcript.md → quote verbatim.' The grounding rules are precise constraints (e.g., never paraphrase inside quotation marks, cite line ranges).

3 / 3

Workflow Clarity

Each workflow is clearly sequenced with explicit validation checkpoints — e.g., 'If the framework doesn't fit, say so,' 'If the user hasn't described their state for a dimension, ask before scoring,' 'If the answer isn't in the transcript, say so explicitly.' The audit workflow enforces walking every dimension in order and asking before scoring gaps. Error/edge cases are addressed throughout.

3 / 3

Progressive Disclosure

The skill references external files (outline.md, transcript.md, quotes.md) with clear navigation instructions, which is good progressive disclosure. However, no bundle files were provided, so we cannot verify these references exist. The SKILL.md itself is somewhat long and could benefit from splitting the five use-case workflows into separate referenced files, keeping the main file as a concise overview with pointers.

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 defines its niche around a specific conference talk. It excels at providing explicit trigger guidance with a 'Use when...' clause and lists numerous specific, natural keywords that users would mention. The only minor concern is that it focuses entirely on 'when' triggers without a brief 'what it does' preamble (e.g., 'Provides detailed knowledge about...'), but the trigger list is so comprehensive that the purpose is self-evident.

DimensionReasoningScore

Specificity

The description lists numerous specific concrete topics and technologies: GPU-accelerated desktops, spec-driven development with plan/implement phases, ZFS-cloned Docker-in-Docker dev environments, forking Zed for remote control, mixing local models (Llama 3.1) with frontier models (Claude Opus), and more.

3 / 3

Completeness

The description explicitly starts with 'Use when the user asks about...' providing a clear trigger clause, and the extensive list of topics effectively answers 'what does this do' (provides knowledge about this specific talk and its topics) and 'when should Claude use it' (when the user asks about any of these specific topics).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms a user might say: 'HelixML', 'Luke Marsden', specific technology names like 'Llama 3.1', 'Claude Opus', 'Zed', 'ZFS', 'Docker-in-Docker', and conceptual phrases like 'dogfooding', 'self-improving companies', 'agent platform'. These are highly specific and natural keywords.

3 / 3

Distinctiveness Conflict Risk

This is extremely niche — it's about a specific person's specific talk with highly distinctive trigger terms like 'HelixML', 'Luke Marsden', 'snake eating its own tail dogfooding approach'. It is very unlikely to conflict with other skills unless there were multiple skills about the same talk.

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