Skip to content
Back to skills

Didit Users Team

ASecurity

Manages the team, roles, applications and API keys in their Didit account. Use when the user says "who is on my team", "invite a teammate", "change their role", "remove a member", "list roles", "API key", "create an API key", "show me the API key", "I lost our key", or asks about their Didit organizations and applications.

  • 28 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agentsgoapi

Works with

  • claude code
  • api

Security analysis

A100/100

Scanned November 18, 2026

npx -y skills add didit-protocol/skills --skill didit-users-team --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Didit Users Team?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Didit Users Team
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/didit-protocol-didit-users-team/badge)](https://www.skillsdirectory.com/skills/didit-protocol-didit-users-team)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: didit-users-team
description: Manages the team, roles, applications and API keys in their Didit account. Use when the user says "who is on my team", "invite a teammate", "change their role", "remove a member", "list roles", "API key", "create an API key", "show me the API key", "I lost our key", or asks about their Didit organizations and applications.
---

# Workspace team, API keys and applications

Follow the rules of didit-users-start first: call `didit_context_get` and pick the organization. This skill is about your own Didit workspace, not the people you verify.

## 1. Organizations and applications

- `didit_context_get` is the quickest way to see every organization and application with their ids and whether each application is sandbox or live.
- `didit_org_list` lists organizations; `didit_org_list_applications` with `organization_id` lists its applications.
- `didit_org_get_application` with `organization_id` and `application_id` returns application details. The API key in it is redacted: a masked preview and an `api_key_set` flag.
- `didit_org_get_balance` returns the organization's credit balance. Report the fields it returns; never state prices, link https://didit.me/pricing.

## 2. Members and roles

Needs a person sign-in: on an API key connection these member and role tools are not available (see didit-users-start).

- `didit_org_list_members` lists members. Each row has a `uuid` (what remove and update take) and a `user_id` (what case assignment takes).
- `didit_org_list_roles` lists the roles with their ids.
- `didit_org_invite_member`: `emails` (1 to 5), `role` (a role id from `didit_org_list_roles`) and `app_ids` (application ids from `didit_context_get` or `didit_org_list_applications`). Repeat the emails, role name and applications and wait for the person to confirm before inviting.

  ```json didit_org_invite_member
  {"emails": ["name@example.com"], "role": "<role_id from didit_org_list_roles>", "app_ids": ["<application_id>"]}
  ```

  `emails` is a list even for one person, `role` is the role's id (match the role the person named against `didit_org_list_roles`), and `app_ids` lists application ids. All three are required. When the person did not say which applications, list them from `didit_context_get` and ask which ones; never pick for them. With only one application, name it in the confirmation.
- `didit_org_update_member`: `member_id`, `role` and `accessible_applications` (the full list after the change). State the old and new role and applications and wait for a yes.
- `didit_org_remove_member`: `member_id`, the member row's `uuid` (not `user_id`, not the email). It cannot be undone; the person would need a new invitation. Name the member and wait for the person to confirm.

## 3. API keys

Needs a person sign-in: on an API key connection these API key tools are not available (see didit-users-start).

- `didit_org_list_api_keys` with `application_id` lists one application's key metadata. Raw key values are redacted.
- `didit_org_create_api_key` issues a credential for one application. Required: `organization_id`, `application_id`, `confirm: true`. Optional: `label`, `scopes` (resource to `read` or `write`), `workflow_ids` (needs `scopes`), `expires_at`.

Before creating a key:

1. Pick the application by its mode in `didit_context_get`: a sandbox key to build and test, a live key to go live.
2. State the application, label, scopes and expiry, and ask the person to confirm. Send `confirm: true` only after that yes.
3. The secret is returned once. Follow the tool's own delivery rule: where you can write files in the person's project (Claude Code, Cowork on their computer), write it straight to the project's secret store or `.env` and do not print it in the chat. Where you cannot write files (chat), show it once and tell the person to store it in their secret manager. Never repeat it later, never put it in notes or memory, and never send it anywhere else.

Didit allows one live key per connected app and application, scoped to what the signed-in person can do. The person can revoke it in the console.

When the person asks to see an application's existing key ("I lost our key"): `didit_org_reveal_application_api_key` is local server only; on the hosted server a new key is created with `didit_org_create_api_key`. Say that an existing key cannot be shown again here, name the application and its mode from `didit_context_get`, and offer a new scoped key with the steps above. The person can revoke the lost key in the console.

## What good output looks like

- Members as a table: name or email, role, applications.
- The exact invitation, role change or removal stated before it runs.
- For a new API key: the application and its mode named, and the secret shown once.

## Do not

- Never ask for credentials (password, API key, one-time code).
- Never fall back to raw HTTP calls (curl/REST) for a console task.
- Never invent role ids, member ids or application ids.
- Never repeat or log an API key secret, and never keep it in notes or memory. It goes once to the project's secret store or `.env`, or is shown once where files cannot be written.
- Never state prices. Link https://didit.me/pricing.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.