team-identity SKILL.md skillA
team-identity from nebius/nebius-physical-ai is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nebius/nebius-physical-ai/team-identity@git:20261010.10de9e7Pins git:20261010.10de9e7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nebius/nebius-physical-ai
- Path
skills/tools/team-identity/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261010.10de9e7, committed Oct 10, 2026
- Size
- 4,600 bytes
- Repository stars
- 106
- License
- Apache-2.0
Configure or use optional Workbench team identities, including local access keys, explicit generic JWT links, and native Nebius human identity verification.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Workbench identity and access Use this skill for the `npa workbench access` identity boundary. It is not a chat-agent routing feature and does not provision a cluster, gateway, or browser login flow. Local Workbench accounts are the stable ownership domain. Create an `account_namespace` once, then use `Accounts` for local people and `issue_key_file` for a personal mode-0600 key. `TeamClient` is the supported agent-callable API for an already-authorized service endpoint. Obtain credentials through the private saved-session provider or the explicit `load_bearer_token` file/environment path. Never print bearer credentials or copy them into reports. For end users, start with `npa login --endpoint <workbench-HTTPS-endpoint>` and choose a privately delivered personal key or `--nebius`. Successful login saves a private named connection and unambiguous placement defaults. Use `npa workbench whoami`, `submit`, `runs`, and `run` for ordinary execution; administrators use `npa workbench access`. The same commands support an individual or a shared installation. Older `npa workbench team` commands remain compatible. …
Read the whole file at its exact version.
How to install
mdr add nebius/nebius-physical-ai/team-identity@sha256:1c7297deabeb88a0The line at the top of this page pins the label git:20261010.10de9e7, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_kv6ui7hqabbffemv)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 10, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4600 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nebius/nebius-physical-ai · 106 stars · license Apache-2.0 · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kv6ui7hqabbffemv GET https://markdownregistry.com/api/v1/resolve?ref=nebius/nebius-physical-ai/team-identity GET https://markdownregistry.com/api/v1/blob/1c7297deabeb88a026a3cd6a7361f0f812b120608efb4a3ad4e6f7440d19ec69
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.