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 retrieval-augmented skill that provides clear, actionable instructions for grounding answers in transcript material. Its strongest aspects are the explicit workflow (navigate outline → read transcript → check quotes → redact → format) and the concrete output example. The main weaknesses are moderate redundancy in redaction/safety instructions across multiple sections and the inability to verify bundle file references since no bundle files were provided.

Suggestions

Consolidate the redaction/sensitive-value instructions into a single clearly-labeled rule rather than repeating them across grounding rules, edge case guidance, output format, and the quotes.md section.

Ensure the bundle actually includes outline.md, transcript.md, and quotes.md so the skill functions as designed — currently no bundle files are provided.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some redundancy — the grounding rules, edge case guidance, and output format sections repeat similar ideas (e.g., redaction is mentioned in multiple places). Some instructions like explaining what quotation marks are for could be tightened. However, it mostly avoids explaining concepts Claude already knows.

2 / 3

Actionability

The skill provides highly concrete, specific guidance: exact steps for answering questions (read outline.md first, then transcript.md), a worked example showing the expected response format with line ranges and italicized quotes, and explicit rules for handling edge cases. This is copy-paste-ready behavioral instruction.

3 / 3

Workflow Clarity

The workflow is clearly sequenced: (1) read outline.md to locate section, (2) read transcript.md for that section, (3) check quotes.md for pre-extracted highlights, (4) apply redaction rules, (5) format response with line ranges and separated paraphrase. Edge cases are explicitly handled with clear branching logic (multi-section, not covered, full synthesis). The validation step of checking for sensitive values before quoting serves as a checkpoint.

3 / 3

Progressive Disclosure

The skill references three bundle files (outline.md, transcript.md, quotes.md) with clear purposes, which is good structure. However, no bundle files were actually provided, making it impossible to verify the references work. The SKILL.md itself is somewhat long and could potentially split the output format example or edge case guidance into a separate reference file, though for this length it's borderline acceptable.

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 its narrow domain (a specific keynote talk), enumerates the concrete concepts it covers, and provides explicit 'Use when' guidance with multiple trigger verbs (understand, apply, audit, explore). The description is well-structured, uses third person voice, and would be highly distinguishable in a large skill library.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and concepts: five engineering disciplines (static analysis, evals, security testing, dependency management, observability), three challenge buckets, agentic development stack, skill authoring, context engineering, agent harnesses, and skill quality scoring.

3 / 3

Completeness

Clearly answers both what ('Assists with questions about Guy Podjarny's talk') and when ('Use when the user wants to understand, apply, audit, or explore frameworks from this keynote') with explicit trigger conditions and detailed enumeration of covered topics.

3 / 3

Trigger Term Quality

Includes highly specific natural keywords a user would say: 'Guy Podjarny', 'Skills are the new Code', 'engineering disciplines', 'static analysis', 'evals', 'security testing', 'dependency management', 'observability', 'agentic development stack', 'context engineering', 'skill authoring'. These are terms someone familiar with the talk would naturally use.

3 / 3

Distinctiveness Conflict Risk

Extremely distinctive — scoped to a specific person's specific talk with named concepts unique to that keynote. Very unlikely to conflict with other skills given the narrow, well-defined niche.

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