CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

talk-azriel-executable-specs

Use when the user asks about Shachar Azriel's AI Native DevCon talk on executable specs, verification layers for agentic coding, planner/verifier separation, requirement mapping, product-gap detection, and safe review architecture.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./Plugins/aidevcon/skills/talk-azriel-executable-specs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

The body is a lean, well-structured instruction set for a reference skill: grounding rules sequence the sources, safety rules treat source material as inert, and each help mode has a concrete procedure. The main weaknesses are the absence of worked examples for citation/answer formats and the fact that the three referenced bundle files do not exist in the bundle as shipped.

Suggestions

Ship the referenced bundle files (outline.md, quote.md, transcript.md) or path-qualify them (e.g., references/outline.md) so the grounding rules resolve to real files.

Add one short worked example of a cited factual answer showing the transcript line-ID citation format and attribution style.

Specify what to do when quote.md and transcript.md disagree (e.g., treat transcript.md as authoritative and note the discrepancy).

DimensionReasoningScore

Conciseness

The ~40-line body is lean with no concept padding: the one-line thesis ("requirements are made testable, evidence is mapped explicitly, and product gaps are surfaced") is talk-specific information rather than explanation Claude already has, and the grounding/safety rules are all actionable directives. Matches anchor 5 ("Lean and efficient; assumes Claude's competence; every token earns its place"); the Core Concepts list is a useful index, not filler, so it does not drop to 4.

5 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: "Read `outline.md` first", "Use `quote.md` for short supporting excerpts, then verify against `transcript.md`", "cite the transcript line IDs when available", and "Mark anything beyond the talk as your own recommendation". Minor gaps remain — no worked example of a cited answer or of the apply/compare output formats — so it fits anchor 4 rather than the fully-covered common cases of anchor 5.

4 / 5

Workflow Clarity

Grounding rules give a clear source sequence (outline → quote → transcript) with an explicit validation checkpoint ("If the transcript does not support a claim, say that the talk does not address it") and an attribution check. It falls short of anchor 5 because verification is conditional ("when precision matters") and there is no guidance for conflicts between quote.md and transcript.md; it is above anchor 3 because a real checkpoint and fallback are explicitly stated.

4 / 5

Progressive Disclosure

References are clearly signaled, purpose-scoped, and one level deep (outline for locating, quotes for excerpts, transcript for verification), matching anchor 4's "references mostly clear". However, the bundle contains no references/ directory — `outline.md`, `quote.md`, and `transcript.md` are unqualified filenames that are not present in the skill bundle, so the structure cannot be verified and paths are unqualified, keeping it below anchor 5.

4 / 5

Total

17

/

20

Passed

Description

51%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.

The description has excellent trigger terms and distinctiveness thanks to the named speaker and talk, but it is only a 'when' clause — it never tells Claude what the skill does (grounded Q&A, applying concepts, comparing talks using bundled transcript/outline/quote files). Adding a one-sentence 'what' clause would raise completeness and specificity substantially.

Suggestions

Add a 'what' clause before the 'Use when' clause, e.g., "Answers questions about, applies concepts from, and compares Shachar Azriel's AI Native DevCon talk using bundled transcript, outline, and quote files."

Include a couple of natural synonyms such as "spec review" or "spec-driven development" alongside "executable specs" to broaden trigger coverage.

State the concrete action modes (factual Q&A with line-ID citations, applying the talk to the user's context, comparing with other sessions) so the description covers the skill's full scope.

DimensionReasoningScore

Specificity

The description names the domain concretely ("Shachar Azriel's AI Native DevCon talk on executable specs, verification layers for agentic coding, planner/verifier separation...") but lists no actions the skill performs — there is no verb describing what it does (answer, summarize, apply, compare). This matches anchor 2 ("Names the domain but actions are minimal or generic"); it is not 3 because no concrete actions are listed at all, and not 1 because the language is specific rather than vague.

2 / 5

Completeness

The 'when' is explicit and detailed ("Use when the user asks about..."), but the 'what' is entirely absent — the description never states what the skill does with such questions. This matches anchor 2 ("only 'when' is present without 'what'"); it is not 3 because that anchor requires a clear 'what', and not 1 because the 'when' clause is strong rather than extremely vague.

2 / 5

Trigger Term Quality

Strong natural keywords a user would actually say: "Shachar Azriel", "AI Native DevCon", "executable specs", "planner/verifier separation", "requirement mapping", "product-gap detection". A few natural variations are missing (e.g., "spec review", "spec-driven development", "agentic verification"), which fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Naming a specific speaker, conference, and talk creates a clear niche with distinct triggers; no other skill would plausibly fire on "Shachar Azriel's AI Native DevCon talk on executable specs". Minimal conflict risk, matching anchor 5.

5 / 5

Total

13

/

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-azriel-executable-specs/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.