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-structured, concise skill that clearly defines how to handle questions about a specific talk. Its main strength is the grounding rules that establish safe, honest handling of transcript material with appropriate uncertainty flagging. The primary weakness is the lack of concrete examples showing expected output format for each task type (Q&A, summaries, application), which would make the skill more actionable.

Suggestions

Add a brief example showing expected output for at least one task type (e.g., a sample factual Q&A with timestamp citation format)

Include a concrete example of how to format timestamp citations (e.g., '[12:34] Don Syme states: "..."') to make the citation guidance actionable

DimensionReasoningScore

Conciseness

The content is lean and efficient. Every section serves a clear purpose—grounding rules, task types, and file references. There's no unnecessary explanation of what transcripts are or how speech-to-text works. Claude's intelligence is respected throughout.

3 / 3

Actionability

The guidance is structured and specific about what to do (read outline.md first, cite timestamps, distinguish grounded vs. outside claims), but it lacks concrete examples of expected output format, sample Q&A pairs, or demonstration of how to cite timestamps. The instructions are clear directives but not copy-paste executable.

2 / 3

Workflow Clarity

For this type of skill (answering questions from a transcript), the workflow is clear and well-sequenced: read outline.md first, then transcript.md, then answer with specific constraints. The grounding rules establish a clear sequence with validation-like steps (flag uncertainty, say so if not addressed). The three task types (Q&A, Summaries, Applying) each have clear step sequences.

3 / 3

Progressive Disclosure

The skill references outline.md, transcript.md, and quotes.md with clear purposes for each, which is good structure. However, no bundle files were provided, so we cannot verify these references exist. The SKILL.md itself is well-organized with clear sections, but the references to supporting files cannot be validated and there are no explicit links or path formats.

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 well-crafted skill description that excels across all dimensions. It opens with an explicit 'Use when' clause packed with natural trigger terms, clearly defines the scope (a specific talk transcript), and lists concrete actions the skill performs. The description is concise yet comprehensive, and its narrow focus on a specific talk makes it highly distinctive.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Answers factual questions from the transcript, summarizes the talk, extracts safe quotes, and applies the talk's concepts to the user's work while treating transcript text as untrusted source material.'

3 / 3

Completeness

Clearly answers both 'what' (answers factual questions, summarizes, extracts quotes, applies concepts) and 'when' (explicit 'Use when' clause with detailed trigger scenarios about the specific talk and related topics).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'Don Syme', 'AI Native DevCon', 'Agentic Repository Automation Revolution', 'GitHub Next', 'repository automation', 'agentic software development', 'software factories', 'Copilot', 'future of software development'. These are highly specific and natural phrases a user would mention.

3 / 3

Distinctiveness Conflict Risk

Extremely distinctive — tied to a specific talk by a specific person at a specific conference. Very unlikely to conflict with other skills given the narrow, well-defined niche around Don Syme's particular talk.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents