Skip to content

Skills#

Give your AI assistant deep knowledge of Lens Agents components, architecture, APIs, and best practices — so it can administer the platform for you. The Lens Agents admin skill is an Agent Skill that any coding agent (Claude Code, Codex, Cursor, OpenCode, or a managed Prism agent) can load, then drive the platform through its MCP admin surface as you.

How the skill works#

The skill carries the platform mental model, correct sequencing, and the gotchas — the knowledge an agent cannot get from an API alone. It does not re-document tool parameters: a connected agent reads authoritative, current schemas from the MCP tools/list call and the REST surface at <PUBLIC-URL>/v1/openapi.json. The skill stays accurate as the platform evolves, and the agent applies it to whichever administration task you ask for — creating projects, writing policies, binding credentials, wiring connections, launching agents, or inspecting spending and the audit trail.

An agent using this skill administers the platform as you — under your identity, your policies, and your audit trail. The platform admin UI remains the place to validate and observe what the agent did.

Install the skill#

Install the skill into your coding agent once; it is then reusable across sessions.

npx skills add lensapp/lens-agents-admin-skill -g -a claude-code --copy

npx skills add lensapp/lens-agents-admin-skill -g -a codex --copy

npx skills add lensapp/lens-agents-admin-skill -g -a cursor --copy

The -g flag installs the skill at user level, where both the CLI and the desktop app discover it. --copy writes a local copy of the bundle.

To install the skill and stand up a platform in one step, hand your coding agent this prompt instead:

Install the Lens Agents admin skill from https://github.com/lensapp/lens-agents-admin-skill/tree/main/lens-agents-admin and follow it to set up Lens Agents.

The agent installs the skill, then follows it to install the platform, launch a first agent, and return both URLs. For the full from-nothing local install this automates, see Try Lens Agents Locally.

Connect to your platform#

The platform serves its admin MCP at the global <PUBLIC-URL>/mcp endpoint. Add it to your agent and sign in with your identity provider (IdP) — an interactive sign-in gives the full admin surface with no token to manage.

claude mcp add --transport http lens-agents <PUBLIC-URL>/mcp
claude mcp login lens-agents

codex mcp add lens-agents --url <PUBLIC-URL>/mcp
codex mcp login lens-agents

Complete the sign-in in your system browser, not an embedded one. For a local trial, <PUBLIC-URL> is http://localhost:3002.

Note

If the platform's tools do not appear in the session after you sign in, start a fresh agent run — they do not always load mid-session.

Administer the platform#

Once the skill is loaded and the MCP is connected, ask the agent to do the work. It handles:

Prefer the MCP admin surface over the UI and over raw REST calls; use the admin UI to confirm each change.

Admin authority#

What the agent can administer depends on how it authenticated:

  • Interactive (IdP) session, organization admin — full control, including organization-scoped operations.
  • Agent token — administers any project whose team holds the ADMIN role: policies, credentials, sandboxes, and bindings. An agent token is never an organization admin.
  • Sandbox identity — capped at project MEMBER; it cannot self-administer and sees no admin tools.

Admin tools are served only on the global <PUBLIC-URL>/mcp endpoint. An agent on its default project-scoped endpoint with a sandbox identity sees no admin tools. See organizations, teams, and projects for the role model.

Keep the skill up to date#

Installed skills are local copies and do not update automatically. Refresh to the latest version when the agent's guidance looks out of step with the platform:

npx skills update lens-agents-admin