CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

talk-kerr-bipolar-disorder-dysregulation-ai

Use when the user asks about Dave Kerr's AI Native DevCon talk on bipolar disorder, dysregulation, and AI, including responsible interpretation of personal and clinical themes from the transcript.

Quality

77%

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-kerr-bipolar-disorder-dysregulation-ai/SKILL.md
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 tight, well-sequenced instruction-only reference skill with genuinely non-obvious grounding, attribution, and safety rules and no padding. Its main weakness is the reference layer: the three bundled files it depends on are absent from the bundle and are referenced by bare filename with no directory location, leaving the progressive-disclosure structure unverified.

Suggestions

Ensure `outline.md`, `quote.md`, and `transcript.md` actually ship in the skill bundle, and reference them with explicit paths (e.g., `references/outline.md`) so the pointers resolve.

Add a brief rule for handling conflicts between the outline and the transcript (e.g., transcript is authoritative) to make the verification checkpoint explicit.

Consider trimming or integrating the 'Core Concepts' list, which mostly duplicates the title and description, into the outline-lookup workflow.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what bipolar disorder or dysregulation is, and the Grounding and Safety rules are all non-obvious, skill-specific instructions. The only trim candidate is the 'Core Concepts' bullet list, which largely restates topics already in the title and description, keeping it just below anchor 5's 'every token earns its place'.

4 / 5

Actionability

The guidance is concrete and executable for an instruction-only skill: 'Read `outline.md` first', 'Use `quote.md` for short supporting excerpts, then verify against `transcript.md` when precision matters', 'cite the transcript line IDs when available', and 'Mark anything beyond the talk as your own recommendation'. It misses anchor 5 only because there is no worked example (e.g., a sample grounded answer with a line-ID citation) covering the most common case.

4 / 5

Workflow Clarity

The grounding rules form a clear ordered workflow (locate in outline → excerpt from quote.md → verify against transcript.md → attribute or disclaim) with an honesty checkpoint ('If the transcript does not support a claim, say that the talk does not address it'), and the three How-To-Help modes are cleanly separated. It sits at anchor 4 rather than 5 because some checkpoints are implicit — e.g., what to do when the outline and transcript disagree, or when a quote cannot be verified.

4 / 5

Progressive Disclosure

The design intent is good — a tiered, one-level-deep structure (outline.md for location, quote.md for excerpts, transcript.md for precision) clearly signaled in the Grounding Rules. However, scoring against the actual bundle structure, none of the referenced files (outline.md, quote.md, transcript.md) exist in any bundle directory, and the body gives no path context for where they live, so the navigation pointers do not resolve. That unverifiable reference layer fits anchor 3 (references present but with real organization gaps) better than anchor 4.

3 / 5

Total

15

/

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-targeted description with excellent trigger terms, a clear explicit 'when' clause, and near-zero conflict risk. Its main weakness is that the 'what' is thin: only one concrete action (responsible interpretation of themes) is stated, leaving the skill's actual capabilities implied.

Suggestions

State the concrete actions the skill performs, e.g. 'Answers questions, locates concepts, and applies insights from the transcript of Dave Kerr's talk' — currently only 'responsible interpretation of personal and clinical themes' is explicit.

Add one or two natural trigger variations users might say, such as 'session' or 'presentation', to round out keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain precisely ("Dave Kerr's AI Native DevCon talk on bipolar disorder, dysregulation, and AI") and states one concrete action — "responsible interpretation of personal and clinical themes from the transcript" — but does not explicitly list what the skill does with that material (e.g., answering questions, summarizing, applying concepts). It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) better than anchor 4, which expects several specific actions.

3 / 5

Completeness

The 'when' is explicit and specific ("Use when the user asks about Dave Kerr's AI Native DevCon talk..."), but the 'what' is only partially stated — "responsible interpretation of personal and clinical themes from the transcript" implies answering/interpreting without naming the actual capability (grounded Q&A, summarizing, applying the talk). This lands between anchors 4 and 5; the weakly explicit 'what' keeps it at 4, above anchor 3 because both elements are present.

4 / 5

Trigger Term Quality

Natural user phrasing is well covered: "Dave Kerr", "AI Native DevCon", "bipolar disorder", "dysregulation", "AI", and "talk" are exactly what a user would say. A few natural variations ("session", "presentation", "mental health") are missing, so it fits anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Naming a specific speaker, event, and topic set ("Dave Kerr's AI Native DevCon talk on bipolar disorder, dysregulation, and AI") creates a clear niche with distinct triggers and virtually no overlap risk with other skills — a direct match for anchor 5.

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-kerr-bipolar-disorder-dysregulation-ai/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.