CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deepgram-dotnet-speech-to-text

Use when writing or reviewing C# code in this repo that calls Deepgram Speech-to-Text for prerecorded or live transcription. Covers `ClientFactory.CreateListenRESTClient()` with `TranscribeUrl` / `TranscribeFile`, and `ClientFactory.CreateListenWebSocketClient()` with `Connect`, `Subscribe`, and `Send`. Use `deepgram-dotnet-audio-intelligence` for summaries/sentiment/topics overlays, `deepgram-dotnet-conversational-stt` for Flux-specific work, and `deepgram-dotnet-voice-agent` for full-duplex assistants.

74

Quality

93%

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

90%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.

High-quality body: executable code for all three usage modes, terse key-param summaries, and genuinely useful gotchas rooted in the real SDK surface. Workflow validation checkpoints exist but are implicit in code rather than stated as steps, and the single-file structure is good though not an exemplar of bundle-based progressive disclosure.

DimensionReasoningScore

Conciseness

Lean throughout: no explanation of concepts Claude already knows, code-first quick starts, and terse pointers like "Full list in `Deepgram/Models/Listen/v1/REST/PreRecordedSchema.cs`" instead of inlining reference tables. Every section earns its tokens.

5 / 5

Actionability

Three fully executable, copy-paste-ready quick starts (REST URL, REST file bytes, WebSocket live with microphone), an install command, and concrete gotches such as "`Listen.v2.WebSocket.Client.Connect` throws if you use `Keyterm` with a non-`nova-3` model". The common cases are covered end-to-end.

5 / 5

Workflow Clarity

Sequences are clear and mostly validated — "Register `Subscribe(...)` handlers before `Connect(...)`" and the explicit `if (!connected)` error check with recovery hint — but there is no explicit validate-fix-retry loop for the setup/teardown path. This matches 'clear sequence with most checkpoints present; minor validation gaps', not 5 (no feedback loop) and not 3 (checkpoints are present).

4 / 5

Progressive Disclosure

Well-organized single-file body with bulk detail delegated to in-repo source files ("Full list in ... PreRecordedSchema.cs") and example programs under `examples/speech-to-text/...`. Minor gaps: navigation points at repo paths and external doc URLs rather than a clean one-level bundle structure, and no separate reference files exist.

4 / 5

Total

18

/

20

Passed

Description

92%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 description: concrete API-level specificity, an explicit 'Use when' trigger tied to a specific language and repo context, and explicit routing to sibling skills to prevent mis-triggering. Only gap is modest coverage of natural synonym phrasings (streaming/real-time/STT/transcribe).

DimensionReasoningScore

Specificity

The description names concrete API methods for both surfaces — "Covers `ClientFactory.CreateListenRESTClient()` with `TranscribeUrl` / `TranscribeFile`, and `ClientFactory.CreateListenWebSocketClient()` with `Connect`, `Subscribe`, and `Send`" — comprehensively covering the SDK surface rather than stopping at 1-2 actions.

5 / 5

Completeness

It explicitly answers both: an explicit trigger clause ("Use when writing or reviewing C# code in this repo that calls Deepgram Speech-to-Text") and a concrete what (both client factories with their methods for prerecorded and live transcription).

5 / 5

Trigger Term Quality

Good natural keywords users would say: "C# code", "Deepgram Speech-to-Text", "prerecorded or live transcription". A few common variations are missing (e.g., "transcribe", "streaming", "real-time", "STT"), keeping it just short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (STT only) and actively routes overlaps away: "Use `deepgram-dotnet-audio-intelligence` for summaries/sentiment/topics overlays, `deepgram-dotnet-conversational-stt` for Flux-specific work, and `deepgram-dotnet-voice-agent` for full-duplex assistants."

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

deepgram/deepgram-dotnet-sdk

Path

.agents/skills/deepgram-dotnet-speech-to-text/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.