CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

talk-baker-sadogursky-context-engineering-skills

Use when the user asks about Macey Baker and Baruch Sadogursky's workshop-style AI Native DevCon session on turning repeated agent work into skills, rules, scripts, hooks, and evals.

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-baker-sadogursky-context-engineering-skills/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 well-organized, token-efficient overview for a reference skill: concrete grounding rules, sensible safety guidance, and clearly sequenced task modes with one-level-deep file references. The main improvements are minor — an example citation format and a brief map of the bundled files would close the remaining gaps.

DimensionReasoningScore

Conciseness

The body is lean (~50 lines) with every section earning its place: a one-sentence framing of the talk's taxonomy, numbered grounding rules, a short safety list, and terse task modes. It assumes Claude's competence and explains nothing Claude already knows; this matches anchor 5 ('lean and efficient; every token earns its place').

5 / 5

Actionability

For an instruction-only skill the guidance is concrete and executable: exact files in a defined order ('Read outline.md first', 'use quote.md… verify against transcript.md'), attribution rules, and 'cite the transcript line IDs when available'. It falls short of anchor 5 only through minor gaps — no example of the citation/attribution format, and subjective thresholds like 'when precision matters' and 'short excerpts only when they clarify'.

4 / 5

Workflow Clarity

The grounding rules give a numbered, ordered workflow (outline → quote → transcript verification) with an explicit unsupported-claim checkpoint ('If the transcript does not support a claim, say that the talk does not address it'), and each How-To-Help mode has a clear linear sequence. It sits at anchor 4 rather than 5 because the quote→transcript verification is stated as a rule rather than an explicit validate-and-retry loop within the task workflows.

4 / 5

Progressive Disclosure

The short overview appropriately defers detail to clearly signaled, one-level-deep references (outline.md, quote.md, transcript.md) named in the grounding rules, matching anchor 4's 'good structure; references mostly clear'. It does not reach anchor 5 because navigation is embedded inside the rules rather than presented as a reference map, and the referenced bundle files could not be verified as present in the skill's directory.

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 is highly distinctive and carries good natural trigger terms, but it is a 'when'-only description: it never states what the skill does (answer questions, summarize, or apply the session's material), leaving its capabilities implicit. Adding a capability clause would lift both completeness and specificity.

Suggestions

Add a 'what' clause before the 'Use when' clause stating concrete capabilities, e.g. 'Answers questions, summarizes, and applies the concepts from <session title>, using a bundled transcript, outline, and quote excerpts.'

Include the session title 'Don't Write Prompts, Write Software' and natural variants like 'talk' or 'workshop' as trigger terms to improve keyword coverage.

Name the concrete actions per task mode (factual Q&A, applying the talk, comparing with other DevCon talks) so the described capabilities match the skill's actual coverage.

DimensionReasoningScore

Specificity

The description names a concrete domain ("Macey Baker and Baruch Sadogursky's workshop-style AI Native DevCon session on turning repeated agent work into skills, rules, scripts, hooks, and evals") but states no capability of the skill itself — there is not a single action verb describing what it does. This matches anchor 2 ('names the domain but actions are minimal or generic'), not 3, which requires 1-2 concrete actions, and not 1, because the domain is specific rather than abstract.

2 / 5

Completeness

The 'when' is explicit ('Use when the user asks about…') but the 'what' is entirely absent — scoring only what is explicitly stated, no capability is described anywhere. This matches anchor 2 ('only when is present without what'); it does not reach anchor 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

Strong natural keyword coverage: both full speaker names, 'AI Native DevCon session', 'workshop-style', and the topic terms 'skills, rules, scripts, hooks, and evals' — phrases a user asking about this talk would plausibly say. It falls short of anchor 5 because it omits the session title ('Don't Write Prompts, Write Software') and common variants like 'talk' or 'presentation'.

4 / 5

Distinctiveness Conflict Risk

Two named individuals plus a named event ('AI Native DevCon') create a clear niche with distinct, highly specific triggers and minimal conflict risk with any other skill. This matches anchor 5 ('clear niche with distinct triggers; minimal conflict risk').

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-baker-sadogursky-context-engineering-skills/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.