CtrlK
BlogDocsLog inGet started
Tessl Logo

deepgram-python-management-api

Use when writing or reviewing Python code in this repo that calls Deepgram Management APIs - projects, API keys, members, invites, usage, billing, models, and reusable Voice Agent configurations. Covers `client.manage.v1.projects`, project-scoped resources under `client.manage.v1.projects.*` (keys, members, members.invites, usage, billing, models, requests), global `client.manage.v1.models`, think-model discovery at `client.agent.v1.settings.think.models`, and `client.voice_agent.configurations.*`. Use `deepgram-python-voice-agent` when you want to run an agent interactively, this skill to PERSIST/LIST agent configs. Triggers include "management API", "list projects", "API keys", "members", "usage stats", "billing", "list models", "agent configurations", "manage.v1".

68

Quality

81%

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

76%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 highly actionable SDK reference with excellent executable examples and well-organized gotchas, held back by missing validation steps around irreversible delete operations (capping workflow clarity) and some redundancy between the intro, quick starts, and Gotchas. Progressive disclosure is good but the reference.md path is not verifiable in the bundle.

Suggestions

Add explicit validation before destructive calls, e.g. 'Before delete, get the resource and confirm the ID/name; deletes are irreversible' as a workflow checkpoint rather than only a warning.

Consolidate the agent-config caveats: state the JSON-string, agent-block-only, and immutable rules once (Gotchas) and trim their repetition from the intro and quick-start comments.

Clarify the in-repo reference path (e.g. 'references/reference.md') so the pointer is resolvable from the skill bundle.

DimensionReasoningScore

Conciseness

Largely lean and dense with no filler or explanations of known concepts, but there is repeated content: the SDK namespace enumeration appears in both the intro and Gotcha 2, and the agent-config caveats (JSON string, agent-block-only, immutable) are stated in the intro, quick-start comments, and Gotchas 4-6. Not quite the 5 anchor's 'every token earns its place'.

4 / 5

Actionability

Copy-paste-ready executable code for every sub-module with exact method chains, parameter shapes ('request={"comment": ..., "scopes": [...]}', 'config=json.dumps(...)'), and real accessor names — fully covers common cases and encodes SDK quirks inline.

5 / 5

Workflow Clarity

Quick starts give per-resource sequences and Gotcha 8 flags 'Delete is irreversible', but there are no verification checkpoints before destructive calls (delete project/key/config) — per the rubric's explicit cap, a skill involving destructive operations without validation steps cannot score above 3, and this sits at the 'sequence present but checkpoints implicit' anchor rather than the 4 anchor's 'most checkpoints present'.

3 / 5

Progressive Disclosure

Good section structure with layered, one-level-deep pointers (in-repo reference, OpenAPI, Context7, product docs). Minor gaps: the 'reference.md' pointer is not a clearly resolvable bundle path (no references/ directory exists in the skill bundle), and repo example files are listed inline — mostly clear but not the top anchor's well-signaled, appropriately split organization.

4 / 5

Total

16

/

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 description: concrete capability enumeration, exact SDK namespaces, explicit use-when guidance with a trigger list, and clear differentiation from the sibling voice-agent skill. Minor deductions for a second-person clause and a few missing natural trigger synonyms.

Suggestions

Rewrite the second-person clause in third person, e.g. 'Use deepgram-python-voice-agent to run an agent interactively; use this skill to persist or list agent configs'.

Add natural trigger synonyms users would say, such as 'invites', 'add team member', 'create API key', and 'spend/credits'.

The awkward phrasing 'this skill to PERSIST/LIST agent configs' would read more naturally as 'this skill to persist or list agent configs'.

DimensionReasoningScore

Specificity

Enumerates concrete capabilities comprehensively ('projects, API keys, members, invites, usage, billing, models, and reusable Voice Agent configurations') with exact SDK namespaces, matching the comprehensive anchor; reduced by 1 per rubric guideline for the second-person clause 'Use `deepgram-python-voice-agent` when you want to run an agent interactively'.

4 / 5

Completeness

Explicitly answers both what (specific resource types and SDK namespaces covered) and when ('Use when writing or reviewing Python code in this repo that calls Deepgram Management APIs', plus a concrete trigger-phrase list), matching the top anchor.

5 / 5

Trigger Term Quality

Nine explicit trigger phrases ('management API', 'list projects', 'API keys', 'members', 'usage stats', 'billing', 'list models', 'agent configurations', 'manage.v1') give good natural coverage, but common variations like 'invites', 'team members', 'create/rotate keys', and 'spend/credits' are missing — between the 4 and 5 anchors, closer to 4.

4 / 5

Distinctiveness Conflict Risk

Clear niche (management/persistence vs. interactive use) with explicit disambiguation: 'Use `deepgram-python-voice-agent` when you want to run an agent interactively, this skill to PERSIST/LIST agent configs', plus scope limited to 'Python code in this repo'.

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.

Validation — 16 / 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.