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

62%

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 conceptual/advisory skill with clear workflows and safety boundaries. Its main strengths are the explicit validation checkpoints in both workflows and the concrete adoption checklist. Its weaknesses are moderate redundancy in safety constraints across sections and the inherently limited actionability due to the safety-redacted nature—though this is by design, it means the skill provides guidance rather than executable artifacts.

Suggestions

Consolidate the repeated safety constraints (Safety Scope, Q&A step 5, and implicit checks elsewhere) into a single authoritative section to reduce redundancy and improve conciseness.

Add a brief concrete example of a conceptual comparison output (e.g., a sample MCP-versus-Web-MCP comparison table) to increase actionability within the safety-redacted constraints.

DimensionReasoningScore

Conciseness

The content is mostly efficient but has some redundancy—the safety constraints are repeated across multiple sections (Safety Scope, Factual Q&A step 5, Safe Outputs), and some concept explanations restate what's already implied. The checklist and workflow sections are reasonably tight.

2 / 3

Actionability

The adoption workflow and checklist provide concrete, structured guidance, but the skill is intentionally non-executable (safety-redacted) and lacks any concrete code or commands. The guidance is specific enough to follow but remains at a conceptual/checklist level rather than providing copy-paste-ready artifacts.

2 / 3

Workflow Clarity

Both the Factual Q&A Workflow and Adoption Workflow are clearly sequenced with explicit validation checkpoints (step 5 in Q&A is a verification gate, step 5-6 in adoption cover privacy review and evaluation). The adoption checklist includes a release gate for human review before escalation to state-changing capabilities.

3 / 3

Progressive Disclosure

The skill references three bundle files (outline.md, transcript.md, quotes.md) with clear descriptions, but no bundle files were actually provided, making it impossible to verify the references work. The SKILL.md itself is well-structured with clear sections, but the inline content (concept explanations, safe outputs list) could potentially be offloaded to referenced files for better separation.

2 / 3

Total

9

/

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 what the skill does (conceptual explanation of a specific talk), when to use it (with an explicit and detailed 'Use when...' clause), and what it avoids (runnable implementation). The trigger terms are specific and varied, and the skill occupies a very distinct niche that minimizes conflict risk.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Explains, summarizes, compares, and applies' a specific talk on specific topics ('Web MCP', 'agentic web'). Also notes it is 'safety-redacted and avoids runnable implementation examples', which is a concrete constraint.

3 / 3

Completeness

Clearly answers both 'what' (explains, summarizes, compares, and applies the talk content at a conceptual level) and 'when' (explicit 'Use when...' clause listing multiple trigger scenarios). Both are well-articulated.

3 / 3

Trigger Term Quality

Includes a rich set of natural trigger terms users would say: 'Web MCP', 'agentic web patterns', 'web contracts for agents', 'frontend-declared capabilities versus backend MCP', 'safe read-only adoption', 'evaluation plans', 'privacy review', 'exposing page context'. These cover both broad and specific variations.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — scoped to a specific speaker's specific talk on a niche topic (Web MCP / agentic web). The mention of 'safety-redacted' and 'conceptual level' further narrows the niche. Very unlikely to conflict with other skills.

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