CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

talk-obstbaum-willoughby-vibes-to-metrics

Use when the user asks about Simon Obstbaum and Rob Willoughby's AI Native DevCon talk on measuring AI agents, output evals versus trajectory evals, instrumentation, compliance, and skill activation metrics.

Quality

80%

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-obstbaum-willoughby-vibes-to-metrics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 concise, well-organized reference-skill body with genuinely actionable grounding rules and sensible verification checkpoints. Its one material defect is bundle integrity: the entire workflow routes through outline.md, quote.md, and transcript.md, and none of those files ship with the skill.

Suggestions

Ship the referenced bundle files (e.g., in references/outline.md, references/quote.md, references/transcript.md) and update the grounding-rule paths to match, so the navigation the skill depends on actually resolves.

Add one short worked example in 'Factual Q&A' showing an answer with a transcript line-ID citation and speaker attribution, to make the expected answer format concrete.

Clarify the quote-vs-transcript verification trigger — replace the conditional "when precision matters" with an explicit rule for when verification is required (e.g., any direct quotation, any contested claim).

DimensionReasoningScore

Conciseness

The ~50-line body is lean with no padding: every section carries instructions Claude does not already know (grounding and attribution policy, source-material safety rules, three task modes, a concept index). It assumes Claude's competence — it never explains what evals or instrumentation are — and re-reading anchors 4 and 3, nothing here rises to the level of trimmable over-explanation.

5 / 5

Actionability

The guidance is concrete and directive for an instruction-only skill: "Read `outline.md` first to locate the relevant section," "Use `quote.md` for short supporting excerpts, then verify against `transcript.md` when precision matters," "cite the transcript line IDs when available," and explicit fallback behavior ("If the transcript does not support a claim, say that the talk does not address it"). It stops short of anchor 5 because no worked example of an expected answer (e.g., a cited excerpt with attribution) is given to anchor the format.

4 / 5

Workflow Clarity

Grounding Rules give a clear lookup sequence (outline → quote → transcript verification) with real checkpoints: verification against the transcript, attribution discipline, and a defined refusal path for unsupported claims. It is not anchor 5 because verification is conditional ("when precision matters") and there are no explicit error-recovery loops or checklists; it is well above anchor 3, where checkpoints are missing or implicit.

4 / 5

Progressive Disclosure

Structurally the body is excellent — three well-signaled, one-level-deep references (outline.md, quote.md, transcript.md) each with a stated purpose, plus a clean section layout. But the bundle check shows none of these files exist: there is no references/ directory and outline.md, quote.md, and transcript.md appear nowhere in the skill bundle, so the overview-to-detail navigation the skill depends on is broken at runtime. That is more than anchor 4's 'minor organization gaps' — the disclosure targets are simply absent.

3 / 5

Total

16

/

20

Passed

Description

73%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 well-scoped, trigger-rich description for a reference skill: the 'when' is explicit and highly specific, and proper nouns make it very distinct from other skills. Its main weakness is that it describes content rather than capabilities — no action verb ever states what the skill does with that content.

Suggestions

State the capability explicitly in third person, e.g. "Answers questions, summarizes, and applies the concepts from Simon Obstbaum and Rob Willoughby's AI Native DevCon talk 'From Vibes to Metrics' on measuring AI agents…" so the 'what' is as explicit as the 'when'.

Add the talk's title phrase ("From Vibes to Metrics") and a synonym like "agent evaluation" / "evals" to the trigger terms, since users may reference the talk by title rather than by the speakers.

Keep the topic enumeration but trim it to the terms users actually search on; the current list already borders on topic padding without adding capability information.

DimensionReasoningScore

Specificity

The description precisely names the domain — "Simon Obstbaum and Rob Willoughby's AI Native DevCon talk" — and enumerates concrete topical scope ("output evals versus trajectory evals, instrumentation, compliance, and skill activation metrics"), which is far richer than the generic domain-only anchor at 2. However, it states no capability actions at all (the only verb is the trigger phrase "the user asks about"), so it does not reach anchor 4's 'several specific actions.'

3 / 5

Completeness

The 'when' is explicit and specific ("Use when the user asks about…" with concrete triggers), exceeding anchor 4's example. The 'what' is present but implicit — the topic list implies a reference/Q&A role for the talk's content, yet no capability verb (answers, summarizes, applies) is ever stated, so it does not clearly and explicitly answer 'what' at anchor 5.

4 / 5

Trigger Term Quality

Strong natural trigger coverage: speaker names, "AI Native DevCon," "measuring AI agents," "output evals versus trajectory evals," "instrumentation," "compliance," and "skill activation metrics" are exactly what a user would say when seeking this talk. It falls short of anchor 5 because common variations are missing — notably the talk's own title phrase "vibes to metrics" and looser synonyms like "agent evaluation."

4 / 5

Distinctiveness Conflict Risk

The speaker proper nouns, conference name, and talk-specific topics create a clear niche with distinct triggers and minimal conflict risk — only a sibling talk in the same series could compete, and the speaker names disambiguate that. It clearly matches anchor 5 rather than anchor 4's 'minor overlap risk.'

5 / 5

Total

16

/

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-obstbaum-willoughby-vibes-to-metrics/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.