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".
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that is highly specific, includes comprehensive trigger terms, clearly answers both what and when, and proactively distinguishes itself from a closely related skill. The explicit SDK path references and the differentiation clause ('Use `deepgram-python-voice-agent` when you want to run an agent interactively, this skill to PERSIST/LIST agent configs') are particularly strong. The description is dense but informative without unnecessary fluff.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and resources: projects, API keys, members, invites, usage, billing, models, voice agent configurations, with specific SDK paths like `client.manage.v1.projects`, `client.voice_agent.configurations.*`. | 3 / 3 |
Completeness | Clearly answers both 'what' (calling Deepgram Management APIs for projects, keys, members, usage, billing, models, voice agent configs) and 'when' (explicit 'Use when writing or reviewing Python code... that calls Deepgram Management APIs' plus explicit trigger list). Also distinguishes from a related skill (`deepgram-python-voice-agent`). | 3 / 3 |
Trigger Term Quality | Includes a rich set of natural trigger terms users would say: 'management API', 'list projects', 'API keys', 'members', 'usage stats', 'billing', 'list models', 'agent configurations', 'manage.v1'. These cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche (Deepgram Management APIs in Python), and explicitly differentiates itself from the related `deepgram-python-voice-agent` skill for running agents interactively vs. persisting/listing configs. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A strong, comprehensive management API skill with excellent actionability — nearly every API surface has executable, copy-paste-ready code. The Gotchas section adds significant value by documenting non-obvious SDK behaviors. Main weaknesses are some redundancy between inline comments and Gotchas, and the lack of explicit guard patterns for destructive operations despite acknowledging their irreversibility.
Suggestions
Add a concrete guard/confirmation pattern for destructive operations (delete project, delete key, delete agent config) — e.g., a pre-check that lists the resource before deleting, or a wrapper function that prompts for confirmation.
Consolidate the agent config body explanation — it's stated in the Quick start code comments, the 'When to use' section, AND Gotchas #4/#5/#6. State it once clearly and reference that location.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good code examples, but some sections are slightly verbose — e.g., the 'Central product skills' section and repeated explanations about what the agent config block contains (mentioned in Quick start comments AND Gotchas #4, #5, #6). The Gotchas section, while valuable, has 10 items that could be tightened. | 2 / 3 |
Actionability | Excellent executable code examples covering all major API surfaces — projects, keys, members, invites, usage, billing, models, voice agent configs, and async. Method signatures include actual parameter names and realistic values, making them copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill covers many independent API calls rather than a multi-step workflow, so sequencing is less critical. However, destructive operations (delete project, delete key, delete agent config) lack explicit validation/confirmation steps — the Gotchas mention 'delete is irreversible' and 'wire tests comment out destructive calls' but there's no explicit guard pattern shown. Per rubric, missing feedback loops for destructive changes caps this at 2. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from authentication → quick starts → async → API reference → gotchas. References to example files, reference.md, external docs, and related skills are clearly signaled and one level deep. Content is appropriately split between inline code and external references. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- deepgram/deepgram-python-sdk
- Commit
16b9839
- 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.