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 skill with excellent actionability and workflow clarity — each workflow has clear triggers, numbered steps, validation checkpoints, and explicit handling of edge cases. The main weaknesses are moderate verbosity (the verbatim-quote instruction is repeated in nearly every section, and some detailed content could be offloaded to bundle files) and the inability to verify progressive disclosure since no bundle files were provided. Overall it's a strong skill that would guide Claude effectively through complex knowledge-retrieval and artifact-generation tasks.

Suggestions

Reduce repetition of the 'quote verbatim / cite line range' instruction — state it once in SLP and reference SLP in each workflow without restating it.

Consider moving the seven audit dimensions and the CLAUDE.md constraint checklist into separate bundle reference files to slim down the main skill body.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient for its complexity, but some sections are verbose — e.g., the audit workflow enumerates seven dimensions inline that could be referenced from a separate file, and the grounding rules repeat the 'verbatim quote' instruction multiple times across sections. Some redundancy between SLP and individual workflow steps.

2 / 3

Actionability

Each workflow has clear, numbered steps with specific triggers, explicit file-lookup procedures, and concrete instructions (e.g., 'read outline.md → locate section → read transcript.md → quote verbatim with line range'). The audit workflow specifies exact dimensions and verdict categories. The draft workflow lists specific constraints to capture. Guidance is precise and directly executable.

3 / 3

Workflow Clarity

Workflows are clearly sequenced with numbered steps, a shared base procedure (SLP), and explicit validation checkpoints (e.g., 'if the answer isn't in the transcript, say so explicitly', 'ask before scoring any the user hasn't described', 'mark anything you add beyond what Paul prescribed'). The trigger table provides clear routing. Error/edge cases are addressed (e.g., framework doesn't fit, claim not in transcript).

3 / 3

Progressive Disclosure

The skill references three bundle files (outline.md, transcript.md, quotes.md) with clear navigation signals, and uses anchor links for internal workflow sections — good structure. However, no bundle files were provided, making it impossible to verify the references work. The audit section's seven dimensions and the draft section's constraint list are inlined when they could be in separate reference files, making the main skill longer than necessary.

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 is highly specific, comprehensive, and distinctive. It clearly articulates what the skill does (explains concepts, audits workflows, drafts artifacts) and when to use it (with an extensive list of natural trigger terms tied to a specific talk). The only minor concern is that the description is quite long, but the length is justified by the breadth of specific trigger terms and capabilities listed.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: answers questions, explains key concepts, surfaces relevant quotes, audits workflows against a framework, drafts specific artifacts (CLAUDE.md files, adversarial-reviewer prompts, UAT test structures). Very detailed and actionable.

3 / 3

Completeness

Clearly answers both 'what' (answers questions, explains concepts, surfaces quotes, audits workflows, drafts artifacts) and 'when' with an explicit 'Use when...' clause listing numerous specific trigger scenarios.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'stopped writing code', 'no-PR open-source policy', 'CLAUDE.md', 'planner/adversarial-reviewer loop', 'swamp', 'vibes don't scale', 'intent is the new architecture', 'supply-chain integrity', 'Paul Stack'. These are highly specific phrases a user familiar with this talk would naturally use.

3 / 3

Distinctiveness Conflict Risk

Extremely distinctive — tied to a specific person (Paul Stack), a specific talk title, and highly unique concepts like 'vibes don't scale', 'swamp the AI-native ops CLI', and the no-PR open-source policy. Virtually no risk of conflicting 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