configure-claude

Install Claude Code configurations into a project's .claude directory.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ckallum/calsuite --skill configure-claude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-claude
Source: https://github.com/ckallum/calsuite/tree/main/.claude/skills/configure-claude
Command: npx skills add https://github.com/ckallum/calsuite --skill configure-claude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the installation of Claude Code configurations into a project's .claude directory, enabling consistent tooling across projects.

Core Features & Use Cases

  • Copy scripts/hooks and scripts/lib into the target project's .claude/scripts/ to bootstrap tooling.
  • Merge hooks config and enable all manifest plugins in .claude/settings.json while preserving existing keys.
  • Validate against global settings and warn about missing marketplaces, plugins, or statusLine configurations; optionally install ccstatusline for completeness.

Quick Start

Run the installer against your target project to apply Claude Code configurations.

Frequently Asked Questions about configure-claude

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

FAQPage Schema
How do I automate Claude Code configuration setup across multiple projects?

You can automate Claude Code configuration by running an installer that copies scripts and merges hooks into the .claude directory. This process preserves existing settings keys while enabling plugins to ensure consistent tooling across projects.

What is the best way to sync Claude Code hooks and plugins between existing projects?

The best way to sync Claude Code hooks and plugins is to use an installer that merges settings.json configurations. It reads hook definitions, copies necessary script files, and enables all manifest plugins without overwriting your existing project keys.

Does installing Claude Code settings overwrite my existing .claude directory configurations?

Installing Claude Code settings does not overwrite your configurations. The installer merges hooks config and enables plugins in settings.json while specifically preserving existing keys to maintain your current project configurations.

Why does my Claude Code configuration warn about missing marketplaces or statusLine settings?

Your Claude Code configuration warns about missing marketplaces or statusLine settings because the installer validates your project against global settings. It surfaces these warnings and can optionally install ccstatusline to ensure configuration completeness.

When do I need to run a Claude Code config installer for my project?

You need to run a Claude Code config installer during initial project setup or when syncing standardized tooling. It bootstraps your .claude/scripts directory with hooks and libraries to establish consistent automation environments.