Use when writing or reviewing Go code in this repo that works with Deepgram management endpoints for projects, keys, members, scopes, invitations, usage, balances, models, reusable agent configurations, or agent variables. Route live voice runtime to deepgram-go-voice-agent and repo workflow questions to deepgram-go-maintaining-sdk.
68
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Use this skill for admin and account operations in pkg/client/manage and pkg/api/manage/v1.
Use a different skill when:
deepgram-go-voice-agent)deepgram-go-maintaining-sdk)Set DEEPGRAM_API_KEY before constructing the management client.
export DEEPGRAM_API_KEY="your_api_key"package main
import (
"context"
"fmt"
"log"
api "github.com/deepgram/deepgram-go-sdk/v3/pkg/api/manage/v1"
manage "github.com/deepgram/deepgram-go-sdk/v3/pkg/client/manage"
)
func main() {
if err := run(); err != nil {
log.Fatal(err)
}
}
func run() error {
ctx := context.Background()
client := manage.NewWithDefaults()
mg := api.New(client)
projects, err := mg.ListProjects(ctx)
if err != nil {
return err
}
fmt.Println(projects)
return nil
}manage.NewWithDefaults()manage.New(apiKey, options)pkg/api/manage/v1, usually via api.New(client)
ListProjects, GetProject, UpdateProject, DeleteProjectListKeys, GetKey, CreateKey, DeleteKeyListMembers, RemoveMemberGetMemberScopes, UpdateMemberScopesListInvitations, SendInvitation, DeleteInvitation, LeaveProjectListRequests, GetRequest, GetFields, GetUsageListBalances, GetBalanceListModels, GetModels, GetModel, ListProjectModels, GetProjectModels, GetProjectModelmanagev1.Client.APIRequest(...)README.mddocs.gopkg/client/manage/client.gopkg/client/manage/v1/client.gopkg/api/manage/v1/projects.gopkg/api/manage/v1/keys.gopkg/api/manage/v1/members.gopkg/api/manage/v1/scopes.gopkg/api/manage/v1/invitations.gopkg/api/manage/v1/usage.gopkg/api/manage/v1/balances.gopkg/api/manage/v1/models.gopkg/api/manage/v1/agents.gopkg/api/manage/v1/agent-variables.gohttps://developers.deepgram.com/openapi.yamlagents.go and agent-variables.go, the in-repo models
are the source of truth, not the spec. The spec and the published API
reference disagree with production on field names (agent_uuid /
agent_variable_uuid, not agent_id / variable_id), on list responses
(a bare JSON array, not {"agents": [...]}), and on the type of config
(a JSON string, not an object). Agent metadata values are arbitrary
JSON, so Metadata is map[string]interface{}, not
map[string]string — narrowing it fails the decode of the entire
response. The models here were captured from live responses; do not
"correct" them back toward the spec.https://developers.deepgram.com/asyncapi.yaml/llmstxt/developers_deepgram_llms_txthttps://developers.deepgram.com/reference/manage/projects/listhttps://developers.deepgram.com/reference/manage/models/listpkg/api/manage/v1; use api.New(client) before calling helpers like ListProjects.APIRequest(...) rather than inventing a new transport layer.examples/manage/projects/main.goexamples/manage/keys/main.goexamples/manage/models/main.goexamples/manage/usage/main.goexamples/manage/agents/main.goFor cross-language Deepgram product knowledge — the consolidated API reference, documentation finder, focused runnable recipes, third-party integration examples, and MCP setup — install the central skills:
npx skills add deepgram/skillsThis SDK ships language-idiomatic code skills; deepgram/skills ships cross-language product knowledge (see api, docs, recipes, examples, starters, setup-mcp).
deepgram/deepgram-go-sdk
8da671a
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.