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 with strong actionability and workflow clarity. Each use case has concrete, sequenced steps with appropriate validation and boundary handling. The main weaknesses are moderate verbosity (some redundancy across workflow sections and slightly wordy phrasing) and the inability to verify that referenced bundle files (outline.md, transcript.md, quotes.md) actually exist, though the references themselves are well-structured.

Suggestions

Reduce redundancy by consolidating the repeated 'follow the common pattern above' instructions — the common pattern section already establishes this, so subsequent sections could be more terse.

Ensure bundle files (outline.md, transcript.md, quotes.md) are included in the bundle so the skill's file references are verifiable and functional.

DimensionReasoningScore

Conciseness

The skill is reasonably well-structured but contains some redundancy — the 'common pattern' preamble is repeated conceptually across sections, and some instructions (like grounding rules) could be tighter. The opening summary paragraph is useful context but slightly verbose. However, it mostly avoids explaining things Claude already knows.

2 / 3

Actionability

The skill provides highly concrete, step-by-step workflows for each use case. Instructions are specific and executable — e.g., 'read outline.md to locate the relevant section, then read that section of transcript.md', clear verdict categories (covered/partial/missing), and explicit rules like 'never put quotation marks around paraphrased content'. Each workflow has clear, actionable steps.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced with numbered steps. The standard lookup procedure is defined once and referenced throughout. Each workflow variant has explicit validation checkpoints — e.g., 'If the framework genuinely doesn't fit, say so', 'If a claim isn't in transcript.md, say the talk doesn't address this', 'ask before scoring' when information is missing. Error handling and boundary conditions are well-addressed.

3 / 3

Progressive Disclosure

The skill references external files (outline.md, transcript.md, quotes.md) appropriately and with clear navigation instructions. However, no bundle files were provided, so we can't verify these references exist. The SKILL.md itself is somewhat long (~100 lines of instruction) with multiple workflow sections that could potentially be split, but the inline structure is reasonably organized with clear headers.

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 an excellent skill description that clearly defines its scope around a single, specific talk, lists concrete actions (summarize, explain, audit, answer questions), and provides an extensive 'Use when...' clause with highly specific trigger terms. The description is well-structured, uses third-person voice, and its narrow focus on a named speaker's specific talk makes it highly distinctive and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Summarizes, explains, audits, and answers questions about' a specific talk, and further specifies 'detailed explanations of key arguments, verbatim quotes, and step-by-step application of the talk's frameworks.'

3 / 3

Completeness

Clearly answers both 'what' (summarizes, explains, audits, answers questions about the specific talk with quotes and frameworks) and 'when' (explicit 'Use when...' clause with an extensive list of trigger scenarios and topics).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'vibe coding', 'agentic programming', 'AI-generated tests', 'BDD-style executable specifications', 'fifth-generation programming', 'AI as compiler', 'Farley's continuous-delivery-style approach', and many more specific concepts from the talk that a user would naturally reference.

3 / 3

Distinctiveness Conflict Risk

Extremely narrow niche — it's about one specific talk by a named speaker (Dave Farley). The combination of the speaker's name, the talk title, and the highly specific conceptual terms (e.g., 'three properties of programming languages', 'three problems AI programming creates') make it virtually impossible to conflict with other skills.

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