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 for answering questions about a specific conference talk. Its greatest strengths are its clear grounding rules (treating transcript as untrusted, flagging uncertainty) and efficient token usage. The main weakness is the lack of concrete examples showing expected output formats for summaries, Q&A responses, or quote extractions, which would make the skill more actionable.

Suggestions

Add a concrete example showing a sample question and expected answer format with timestamp citation (e.g., 'Q: What is the speaker's main thesis? A: At [12:34], Azriel argues that...').

Include a brief example of what a summary output should look like, demonstrating the thesis-first structure with supporting excerpts.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It avoids explaining what transcripts, specs, or agentic coding are, and every section serves a clear purpose. No unnecessary padding or concept explanations.

3 / 3

Actionability

The guidance is structured and specific about process (read outline first, then transcript, cite timestamps), but lacks concrete examples of expected output format, sample Q&A pairs, or demonstration of how to format a summary or quote extraction. It describes what to do rather than showing it.

2 / 3

Workflow Clarity

For this type of skill (reference Q&A from a transcript), the workflow is clear and well-sequenced: read outline → locate section → read transcript → answer with citations. The grounding rules provide explicit validation checkpoints (flag uncertainty, say when transcript doesn't address a question, distinguish grounded vs. outside claims).

3 / 3

Progressive Disclosure

The skill references outline.md, transcript.md, and quotes.md appropriately as one-level-deep references, but no bundle files were provided to verify these exist. The SKILL.md itself is well-organized with clear sections, but the absence of the referenced files makes it impossible to confirm the navigation works. The structure is sound but the references are unverifiable.

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 identifies a narrow, well-defined niche (a specific conference talk) with explicit trigger guidance and concrete actions. It opens with a 'Use when' clause, lists natural keywords users would say, and describes specific capabilities. The only minor note is that it's somewhat long, but the length is justified by the specificity of the content.

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.' Also mentions treating transcript text as untrusted source material, which is a specific behavioral detail.

3 / 3

Completeness

Clearly answers both 'what' (answers factual questions, summarizes, extracts quotes, applies concepts) and 'when' with an explicit 'Use when' clause listing specific trigger scenarios including the talk name, speaker, and related concepts.

3 / 3

Trigger Term Quality

Includes highly specific natural trigger terms a user would say: 'Shachar Azriel', 'AI Native DevCon', 'Executable Specs', 'verification layer', 'agentic coding', 'spec review', 'requirements validation'. These cover the talk title, speaker name, and key concepts users would reference.

3 / 3

Distinctiveness Conflict Risk

Extremely distinctive — tied to a specific speaker, a specific talk title, and a specific conference. Very unlikely to conflict with other skills unless there are multiple skills about the same 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