setup

Detect deployment mode and guide Clawkeeper hook configuration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clawkeeper Setup provides an guided onboarding experience to determine the user's current deployment mode and configure the Clawkeeper plugin accordingly, reducing setup friction and confusion.

Core Features & Use Cases

  • Mode detection: automatically identifies push-hooks, user-level hooks, connected, disconnected, or local opt-in states and guides the user through setup.
  • Status guidance: presents actionable status blocks with recommended commands such as /clawkeeper-code:status, /clawkeeper-code:audit, or /clawkeeper-code:connect based on current mode.
  • Blocking mode configuration: introduces a configurable detection mode (warn or block) and persists changes to the config.json for consistent policy.
  • Local vs connected workflows: supports local-only opt-in with bundled features or full connected workflows with dashboard and API-backed status.

Quick Start

Begin the guided onboarding by running /clawkeeper-code:setup and follow the prompts to detect mode and configure hooks.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I configure git hooks for a security plugin during onboarding?

Guided hook setup automatically detects your deployment mode and validates configuration against settings and config files. It coordinates mode detection and stepwise validation to enforce safe defaults for push-hooks, user-level hooks, and local opt-in scenarios.

What is the difference between warn and block modes for security hook configuration?

Warn and block modes determine how policy violations are handled during setup. The guided flow persists your chosen detection mode to config.json, using conditional prompts to enforce either blocking or warning states for consistent policy enforcement.

Do I need API keys to set up local opt-in security hooks?

Local opt-in security hooks do not require API keys. The guided setup supports local-only workflows with bundled features, distinguishing them from connected deployments which require API key validation and dashboard-backed status checks.

How do I switch from disconnected to connected mode for my security plugin setup?

Switching from disconnected to connected mode involves mode-change prompts with stepwise status validation. The guided flow detects your current state, validates configuration files, and recommends connect commands to transition your deployment safely.

Why does my security plugin onboarding check .claude/settings.json?

Onboarding checks .claude/settings.json to validate your configuration state and determine deployment mode. This deterministic setup flow performs stepwise status validation against settings files, API keys, and config.json to ensure safe defaults before applying hooks.