CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

talk-scheire-artificial-intelligence

Use when the user asks about Lieven Scheire's talk "Artificial Intelligence" (a Belgian physicist/comedian's keynote on AI for a developer audience) — including questions about his one-sentence definition of AI as "a new kind of software good at pattern recognition", the history of AI from the 1956 Dartmouth workshop, how neural networks mimic the brain, training-data bias (the "snow in the background" wolves-vs-huskies example, the dermatology ruler example), the black-box nature of neural nets, hobbyist AI tools (Teachable Machine, Custom Vision, HeyGen, PhotoMath, Merlin), Ben Hamm's cat flap, his skeptical stance on LLMs as "language imitation" vs AGI, safe excerpts from the talk, or applying his framing to current AI work.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured reference-skill body: the lookup workflow is concrete and clearly sequenced, attribution and untrusted-source safety rules handle real failure modes, and bulk content is correctly pushed to one-level-deep bundle files. The main weaknesses are redundancy — the 'Grounding rules' and 'General lookup procedure' sections restate the same workflow — and small grammar slips that slightly undermine an otherwise tight document.

Suggestions

Merge the 'Grounding rules' and 'General lookup procedure' sections into a single canonical procedure (read outline.md → read the transcript range → quote safe excerpts → cite line numbers → explicit not-in-transcript fallback), and have the rules reference it instead of restating it, cutting ~10 lines of duplication.

Fix the recurring grammar slips: 'a **safe excerpts**' (appears twice, should be 'a safe excerpt' or 'safe excerpts'), and define the 'safe excerpts' quoting convention once instead of bolding it in nearly every section.

Add one short worked example of a grounded answer (question → outline.md section located → quoted excerpt with a line-range citation) so the citation and quoting conventions are unambiguous in practice, which would also raise actionability.

DimensionReasoningScore

Conciseness

The body is entirely procedural, talk-specific guidance with no re-teaching of concepts Claude already knows, but the six 'Grounding rules' and the five-step 'General lookup procedure' restate the same outline→transcript→quote→cite→fallback workflow, which is a real tightening opportunity beyond 'minor instances'. Recurring bolded 'safe excerpts' and grammar slips ('a **safe excerpts**' twice) add padding, placing it at anchor 3 ('mostly efficient but... could be tightened') rather than anchor 4, and far above anchor 2's padded verbosity.

3 / 5

Actionability

Concrete, executable instruction-only guidance: exact files and lookup order ("read `outline.md` to locate the relevant section, then read that section of `transcript.md`"), exact fallback phrasing ("say 'the talk doesn't address this'"), attribution phrasing ("Scheire said..." / "the host said..."), and four specific proactive-surfacing triggers. It stops short of anchor 5 because there is no worked example of a cited answer and some steps remain directional ('walk through applying it step-by-step'), so it fits anchor 4's 'mostly executable guidance... with minor gaps'.

4 / 5

Workflow Clarity

The lookup workflow is clearly sequenced (outline.md → transcript range → answer with safe excerpts → cite line numbers → explicit not-in-transcript fallback), and the unreliable-speaker attribution rules act as error handling for a known failure mode. There are no destructive or batch operations, so no validation cap applies, but there is no explicit validate/verify checkpoint on its own outputs, so it fits anchor 4 ('clear sequence with most checkpoints present; minor validation gaps') rather than anchor 5's feedback loops.

4 / 5

Progressive Disclosure

SKILL.md is a lean overview that appropriately delegates all bulk material to three one-level-deep, clearly signaled files (`outline.md` as index, `transcript.md` as source, `quote.md` as pre-extracted highlights), with navigation guidance for each ("check `quote.md` first for strong citable evidence", outline section names like "Terminology glossary" and "Named frameworks / concepts"). This matches anchor 5's 'clear overview with well-signaled one-level-deep references; easy navigation'. Note: no bundle files were provided alongside SKILL.md in this review copy, so the existence of the three referenced files could not be directly verified.

5 / 5

Total

16

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong reference-skill description: it names a highly specific niche (Lieven Scheire's 'Artificial Intelligence' talk), provides an explicit 'Use when...' trigger clause with concrete trigger phrases, and enumerates the talk's coverage areas with specific, quotable terms and synonyms. Its only weakness is that it describes coverage as 'questions about <topic>' rather than explicit action verbs, which slightly blurs what the skill does versus what it covers.

DimensionReasoningScore

Specificity

The description enumerates many concrete, verifiable topics ("his one-sentence definition of AI as 'a new kind of software good at pattern recognition'", "the 1956 Dartmouth workshop", "the 'snow in the background' wolves-vs-huskies example", "Teachable Machine, Custom Vision, HeyGen, PhotoMath, Merlin", "his skeptical stance on LLMs as 'language imitation' vs AGI") plus two skill actions ("safe excerpts from the talk", "applying his framing to current AI work"). It falls just short of anchor 5 because it lists topics as 'questions about X' rather than multiple explicit concrete actions (compare anchor 5's 'Extract... fill... merge... convert...'), and well above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Both 'what' and 'when' are explicit: it opens with "Use when the user asks about Lieven Scheire's talk 'Artificial Intelligence'..." (explicit when, with concrete trigger phrases) and defines the what via the enumerated coverage areas and actions ("safe excerpts from the talk, or applying his framing to current AI work"). This clearly satisfies anchor 5 and exceeds anchor 4, whose 'when' 'could be more explicit or specific' — here the when clause is maximally explicit.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and specific names a user would actually say: "Lieven Scheire", "Artificial Intelligence" talk, "neural networks", "pattern recognition", "training-data bias", "black box", "LLMs", "AGI", "language imitation", and tool names like "Teachable Machine" and "PhotoMath". This matches anchor 5's 'comprehensive coverage of natural terms including synonyms'; nothing a user would naturally type about this talk is missing.

5 / 5

Distinctiveness Conflict Risk

A clear niche — one specific keynote by a named speaker — with distinct triggers (the speaker's and talk's names). The generic AI terms (neural networks, AGI, LLMs) are all scoped by "questions about" the talk, so overlap with general-AI skills is minimal, matching anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/aidevcon/skills/talk-scheire-artificial-intelligence/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.