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 instruction-only skill for handling questions about a specific conference talk. Its greatest strengths are the highly actionable, clearly sequenced workflows for each use case and the rigorous grounding rules that prevent hallucination and misattribution. The main weaknesses are moderate verbosity (the quoting mandate is repeated across nearly every section) and the inability to verify the referenced bundle files (outline.md, transcript.md, quotes.md) that the entire skill depends on.

Suggestions

Consolidate the repeated 'quote verbatim from transcript.md' instruction into the grounding rules section and reference it once from each workflow, rather than restating it in every procedure.

Consider splitting the five detailed use-case workflows into a separate WORKFLOWS.md file, keeping SKILL.md as a concise overview with the grounding rules and a navigation table.

DimensionReasoningScore

Conciseness

The skill is reasonably well-structured but includes some verbose sections, particularly the detailed audit walkthrough and the repeated emphasis on verbatim quoting rules. Some instructions could be tightened — e.g., the 'Surface this talk proactively' section repeats the quoting mandate yet again. However, it mostly avoids explaining things Claude already knows and stays focused on domain-specific guidance.

2 / 3

Actionability

The skill provides highly concrete, step-by-step procedures for each use case (apply framework, audit against maturity model, teach concepts, factual Q&A, proactive surfacing). Each workflow has numbered steps with specific actions like 'read outline.md → locate section → read transcript.md → quote verbatim.' The grounding rules are precise and actionable constraints. This is an instruction-only skill that doesn't need code examples, and the guidance is specific enough to be directly executable.

3 / 3

Workflow Clarity

Each of the five use-case workflows is clearly sequenced with explicit steps. The audit workflow is particularly strong with its dimension-by-dimension walkthrough, explicit handling of missing user info ('ask before scoring'), gap acknowledgment ('Thomas only gives the full level-by-level rubric for the workflow integration dimension'), and summary/next-steps phase. Validation is built in through the grounding rules (verify against transcript, cite line numbers, say 'the talk doesn't address this' when appropriate).

3 / 3

Progressive Disclosure

The skill references external files (outline.md, transcript.md, quotes.md) appropriately and signals when to use each. However, no bundle files were provided, making it impossible to verify these references resolve correctly. The SKILL.md itself is somewhat long and could potentially split the five use-case workflows into a separate reference file, keeping the main skill leaner with just the grounding rules and a quick-reference table pointing to detailed procedures.

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 niche — answering questions about a specific conference talk by Ian Thomas. It provides extensive trigger terms covering the talk's key concepts and tools, and opens with an explicit 'Use when' clause. The only minor note is that it doesn't describe what the skill *does* (e.g., 'Answers questions about...', 'Summarizes and explains...') — it's entirely trigger-focused — but the 'Use when the user asks about' framing implicitly covers this.

DimensionReasoningScore

Specificity

The description lists numerous specific concrete topics and tools: AI4P programme, 6-dimension/5-level AI maturity model, self-assessment workshop, autonomous code mods, DRS risk-scoring tool, Horizon MCP server, anti-test-slop, vanity metrics vs real productivity, and the ground-up-plus-top-down adoption playbook.

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 thoroughly covers what the skill addresses. Both 'what' and 'when' are clearly answered.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms a user would say: 'Ian Thomas', 'AI Native Engineering', 'Meta', 'Reality Labs', 'Horizon', 'AI4P', 'AI maturity model', 'DRS risk-scoring tool', 'Horizon MCP server', 'anti-test-slop', 'autonomous code mods'. These are highly specific and match what someone familiar with the talk would naturally reference.

3 / 3

Distinctiveness Conflict Risk

This is extremely distinctive — it targets a specific person's specific talk at a specific company with highly unique terminology (AI4P, DRS risk-scoring tool, Horizon MCP server, anti-test-slop). It is very 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