connect

Authenticate and link the Clawkeeper Cowork plugin to clawkeeper.dev via device authorization.

2|1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/rad-security/claude-code-plugin --skill connect-rad-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: connect
Source: https://github.com/rad-security/claude-code-plugin/tree/main/plugins/clawkeeper-cowork/skills/connect
Command: npx skills add https://github.com/rad-security/claude-code-plugin --skill connect-rad-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Connects the Clawkeeper Cowork plugin to clawkeeper.dev via device authorization to enable dashboard visibility and org policy synchronization for your workspace.

Core Features & Use Cases

  • Reuses an existing API key if already connected to avoid repeated authentication.
  • Registers a device, opens a browser for user approval, and polls for approval to securely obtain and store a new API key.
  • Provides clear success and error guidance, including a manual API key fallback if necessary.

Quick Start

Run the connect routine to initiate device authorization and link your account.

Frequently Asked Questions about connect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate and link my Clawkeeper Cowork plugin to clawkeeper.dev?

To authenticate and link your Clawkeeper Cowork plugin, initiate the device authorization workflow to register your device, open a browser for approval, and securely obtain an API key. It automatically reuses existing keys if already connected.

What should I do if device authorization fails to obtain an API key?

If device authorization fails to obtain an API key, you can use the manual API key fallback. This alternative method allows you to manually input the key to establish the connection and enable dashboard visibility and policy synchronization.

How does device authorization work for API key registration?

Device authorization works by registering your device, launching a cross-platform browser for user approval, and asynchronously polling the server. Once approved, it securely stores the newly obtained API key for workspace access.

Do I need to re-authenticate my device if I already have an API key?

No, you do not need to re-authenticate if you already have an API key. The connection process automatically detects and reuses existing valid keys to avoid repeated authentication flows and maintain workspace access.

Can I reconnect my Clawkeeper plugin if the connection drops?

Yes, you can reconnect your Clawkeeper plugin. The workflow supports both new connections and reconnections, ensuring your org policy synchronization and dashboard visibility are restored securely across your workspace.