claude-kickoff

Configure Claude Code permissions, plugin cadence, and CLAUDE.md merging after generic kickoff.

6|Updated May 4, 2026
One-click install
npx skills add https://github.com/zauberzeug/game-of-cards --skill claude-kickoff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-kickoff
Source: https://github.com/zauberzeug/game-of-cards/tree/main/claude-plugin/skills/claude-kickoff
Command: npx skills add https://github.com/zauberzeug/game-of-cards --skill claude-kickoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude Code requires specialized kickoff steps after the generic kickoff, including Bash(goc:*) permission grants, plugin installation cadence, and per-file CLAUDE.md / CLAUDE.local.md merge prompts. This skill ensures Claude-specific state is established without disrupting non-Claude setups.

Core Features & Use Cases

  • Complement to the generic kickoff by handling Claude-specific permissions, plugin cadence, and CLAUDE merge prompts for Claude Code repos.
  • Auto-invocation after the generic kickoff completes or when the user requests Claude-specific GoC setup, ensuring GoC-managed state is ready for subsequent sessions.

Quick Start

Run this after the generic kickoff to finalize Claude Code integration and enable Claude-specific prompts and plugin management.

Frequently Asked Questions about claude-kickoff

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

FAQPage Schema
How do I configure Bash(goc:*) permissions for Claude Code?▼

You can configure Bash(goc:*) permissions by running the Claude kickoff skill after the generic kickoff. It automatically updates .claude/settings.json to grant the required GoC toolchain access for your repository.

How do I merge CLAUDE.md and CLAUDE.local.md files for a project?▼

Merging CLAUDE.md and CLAUDE.local.md is handled through per-file merge prompts during the Claude kickoff process. It reads both files and updates your project configuration to integrate Claude-specific instructions across project files.

Do I need the GoC toolchain on path to set up Claude Code repositories?▼

Yes, the GoC toolchain must be on path to use Claude kickoff. The skill requires existing repository state from the generic kickoff and relies on the GoC toolchain to establish Claude-specific permissions and plugin cadence.

What is the best way to manage plugin installation cadence for Claude Code?▼

Managing plugin installation cadence is done by running the Claude kickoff skill after your generic kickoff completes. It establishes the correct plugin cadence and Claude-specific state without disrupting non-Claude setups in your repository.

Can I use Claude kickoff without running the generic kickoff first?▼

No, Claude kickoff requires existing repository state from the generic kickoff. It is designed as a complement that applies after the generic kickoff completes to handle Claude-specific permissions and CLAUDE.md integration.

Why does Claude kickoff not disrupt my non-Claude project setups?▼

Claude kickoff isolates changes to Claude-specific state by only updating .claude/settings.json and handling CLAUDE.md merge prompts. It extends the generic kickoff without altering configurations needed by non-Claude setups.