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 with strong actionability and workflow clarity — each user intent has a clear, sequenced procedure with appropriate validation steps and guardrails. The main weaknesses are moderate verbosity from heavily repeated instructions (especially the verbatim-quoting mandate appearing in nearly every section) and the inability to verify the referenced bundle files (outline.md, transcript.md, quotes.md). The grounding rules and safety constraints are excellent.

Suggestions

Consolidate the repeated 'quote verbatim from transcript.md' instruction into the grounding rules section once, then reference it briefly in each workflow (e.g., 'Follow grounding rules for quoting') to reduce redundancy and save tokens.

Ensure bundle files (outline.md, transcript.md, quotes.md) are included in the bundle so the progressive disclosure references are verifiable and functional.

DimensionReasoningScore

Conciseness

The skill is reasonably well-structured but contains some repetitive instructions — the 'verbatim quote' mandate is restated in nearly every section (at least 6 times), and the grounding rules overlap significantly with the per-section instructions. Some tightening would reduce token cost without losing clarity.

2 / 3

Actionability

Each section provides concrete, step-by-step procedures for different user intents (audit, draft artifact, factual Q&A, proactive surfacing, teaching). The instructions are specific about which files to consult, what to quote, how to handle gaps, and how to mark additions beyond the talk's content. This is highly actionable guidance for an instruction-only skill.

3 / 3

Workflow Clarity

Every workflow is clearly sequenced with numbered steps, explicit validation checkpoints (e.g., 'ask before scoring' if user hasn't described their state, 'say so explicitly' if a dimension doesn't apply, 'mark clearly' for content beyond the talk). The audit workflow in particular has a thorough feedback loop: check each dimension, ask if info is missing, give verdicts, summarize gaps.

3 / 3

Progressive Disclosure

The skill references supporting files (outline.md, transcript.md, quotes.md) with clear navigation instructions, which is good. However, no bundle files were provided, so we cannot verify these references exist. Additionally, the SKILL.md itself is fairly long and some of the repetitive quoting/grounding instructions could be factored into a shared reference section rather than repeated in every workflow, improving organization.

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 description that clearly identifies a very specific knowledge domain (a particular conference talk) and provides extensive trigger terms covering all major topics from that talk. The explicit 'Use when' clause and comprehensive topic enumeration make it easy for Claude to select this skill precisely when needed. The only minor concern is that it's a single long sentence which could be slightly more readable, but this doesn't materially impact functionality.

DimensionReasoningScore

Specificity

The description lists numerous specific concrete concepts and actions: Agent Experience (AX), AX paradox, redesigning CLIs/build logs/deploy previews, event-driven agent architectures, blueprints (skills/recipes/context/ADRs), software factories, autonomous development loops, sandbox + human-in-loop + audit/rollback trust principles, and applying Netlify's AX approach.

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 handles. Both 'what' and 'when' are clearly addressed.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms a user would say: 'Dana Lawson', 'Built for Humans', 'Agent Experience', 'AX', 'Netlify', 'CTO', 'blueprints', 'software factories', 'human-in-loop', 'deploy previews', 'ADRs'. These are highly specific and match what someone familiar with this talk would naturally reference.

3 / 3

Distinctiveness Conflict Risk

This is extremely niche — it's about a specific person's specific talk at a specific company. The combination of 'Dana Lawson', 'Built for Humans. Now Agents Are Here.', and 'Netlify CTO' makes 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