CtrlK
BlogDocsLog inGet started
Tessl Logo

deepgram-python-text-intelligence

Use when writing or reviewing Python code in this repo that calls Deepgram Text Intelligence / Read (`/v1/read`) for sentiment, summarization, topic detection, and intent recognition on text input. Covers `client.read.v1.text.analyze(...)` with body `text` or `url`. Use `deepgram-python-audio-intelligence` when the source is audio instead of text. Triggers include "read API", "text intelligence", "analyze text", "sentiment", "summarize text", "topics", "intents", "read.v1".

75

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A tight, actionable skill body with executable quick-start and async examples, a clear parameter table, and well-signaled one-level-deep references. The only weakness is verbosity: the 'summarize is boolean-only' caveat is explained at length in three separate places.

Suggestions

Consolidate the 'summarize is boolean-only on /v1/read' guidance into a single, concise gotcha entry and shorten the parameter-table cell to a one-line cross-reference instead of repeating the full Union/Literal/Fern-artifact explanation.

Drop the 'Fern artifact / generated wire test' detail from the body or move it to reference.md — it is debugging context, not guidance Claude needs to call the API correctly.

Reduce the inline code comment '# /v1/read is boolean-only (see gotchas)' since the dedicated gotcha already covers it, avoiding a third repetition of the same caveat.

DimensionReasoningScore

Conciseness

The body is mostly lean code and tables with no beginner-concept padding, but the 'summarize is boolean only' caveat is repeated verbosely three times (table cell note, inline comment, and the long gotcha #3 covering the Fern artifact and 'Union[Literal["v2"], Any]'), which could be tightened — placing it at anchor 2 rather than the fully lean anchor 3.

2 / 3

Actionability

Quick-start and async code blocks are fully executable and copy-paste ready, the parameter table gives concrete types, and the response shape is spelled out, matching the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

This is a single one-shot analysis call made unambiguous by 'When to use', a quick start, and a gotchas list; per the simple_skills note a single-action skill can score 3 when clear, and no destructive/batch operation requires a validation checkpoint.

3 / 3

Progressive Disclosure

SKILL.md acts as a clear overview with a layered 'API reference' section pointing one level deep to reference.md, OpenAPI, Context7, and product docs, with content appropriately split and easy to navigate; no bundle directories exist, so the conditional bundle-structure guideline does not apply.

3 / 3

Total

11

/

12

Passed

Description

100%

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 precise, well-scoped description that states concrete capabilities, gives a natural-language trigger list, and explicitly disambiguates from the sibling audio skill. It uses imperative 'Use when...' voice with no first/second person, so no specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('sentiment, summarization, topic detection, and intent recognition on text input') plus the specific call 'client.read.v1.text.analyze(...)', matching the 'lists multiple specific concrete actions' anchor rather than the partial anchor 2.

3 / 3

Completeness

An explicit 'Use when writing or reviewing Python code in this repo that calls Deepgram Text Intelligence / Read (`/v1/read`)...' clause answers both what and when with explicit triggers, satisfying the anchor-3 bar; not capped at 2 since the when-clause is present and explicit.

3 / 3

Trigger Term Quality

Explicit trigger list ('read API', 'text intelligence', 'analyze text', 'sentiment', 'summarize text', 'topics', 'intents', 'read.v1') gives good coverage of natural terms a user would say, not just jargon.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche and explicitly redirects the overlapping case ('Use `deepgram-python-audio-intelligence` when the source is audio instead of text'), making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
deepgram/deepgram-python-sdk
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.