CtrlK
BlogDocsLog inGet started
Tessl Logo

deepgram-java-text-intelligence

Use when writing or reviewing Java code in this repo that calls Deepgram Text Intelligence / Read (`/v1/read`) for text analysis. Covers `client.read().v1().text().analyze(...)` with `ReadV1Request` or `TextAnalyzeRequest`. Use `deepgram-java-audio-intelligence` when the source is audio instead of text. Triggers include "read api", "text intelligence", "analyze text", "sentiment", "topics", "intents", and "summarize text".

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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, executable skill body with complete code examples and clear navigation to authoritative references. It is slightly above the simplest-case threshold in length, leaving minor conciseness and progressive-disclosure room rather than full marks.

Suggestions

Move the bulk of the "API reference (layered)" link list and "Key parameters / API surface" into a separate reference file (e.g. references/api-surface.md) so SKILL.md stays a lean overview.

Trim the closing "Central product skills" promotional block or condense it to a single line to recover token budget.

Consider extracting the custom-topics/intents and async examples into a references/examples.md, keeping only the base quick start inline.

DimensionReasoningScore

Conciseness

Mostly lean code-first content that assumes competence, but the layered API-reference list and the trailing "Central product skills" promo could be trimmed without losing usefulness.

4 / 5

Actionability

Complete, copy-paste-ready Java examples with imports for the main case, custom topics/intents, and async, supplemented by a concrete "Key parameters / API surface" list covering common cases.

5 / 5

Workflow Clarity

Single-purpose API skill where the action (build TextAnalyzeRequest, call client.read().v1().text().analyze, read results) is unambiguous; no destructive/batch operation requires validation checkpoints, so the simple-skill exception applies.

5 / 5

Progressive Disclosure

Well-organized into clear sections with clearly signaled in-repo paths and external doc links in the layered API-reference section, but all content is inline in SKILL.md (~125 lines) with no separate reference files, so it is not the leanest overview-with-references structure.

4 / 5

Total

18

/

20

Passed

Description

87%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 strong, specific description that answers both what and when, lists natural trigger terms, and explicitly distinguishes itself from the related audio skill. Minor gaps in action breadth and trigger synonyms keep specificity and trigger_term_quality just below full marks.

DimensionReasoningScore

Specificity

Names concrete actions ("writing or reviewing Java code", "calls Deepgram Text Intelligence / Read (`/v1/read`) for text analysis") and specific code paths (`client.read().v1().text().analyze(...)`, `ReadV1Request`, `TextAnalyzeRequest`), plus sentiment/topics/intents/summarize, but coverage of distinct actions is somewhat narrow around a single analyze call.

4 / 5

Completeness

Clearly states what it does (Java code calling Read for text analysis with specific request types) and when to use it ("Use when writing or reviewing Java code in this repo...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Explicit trigger list ("read api", "text intelligence", "analyze text", "sentiment", "topics", "intents", "summarize text") gives good natural-term coverage, but a few common synonyms (e.g. "summarization", "tone") are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Java SDK text analysis in this repo) with an explicit boundary ("Use `deepgram-java-audio-intelligence` when the source is audio instead of text"), minimizing conflict risk.

5 / 5

Total

18

/

20

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-java-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.