Skip to content
Back to skills

Init Claude Setup

ASecurity

Initialize project-level Claude setup (gitignore entries, settings.local.json) without copying agent/skill files. Use this in projects where agents were installed globally (default setup.sh behavior).

  • 31 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 12, 2026
toolsgit

Works with

  • cli

Security analysis

A100/100

Scanned September 12, 2026

npx -y skills add nickmaglowsch/claude-setup --skill init-claude-setup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Init Claude Setup?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Init Claude Setup
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nickmaglowsch-init-claude-setup/badge)](https://www.skillsdirectory.com/skills/nickmaglowsch-init-claude-setup)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: init-claude-setup
description: "Initialize project-level Claude setup (gitignore entries, settings.local.json) without copying agent/skill files. Use this in projects where agents were installed globally (default setup.sh behavior)."
argument-hint: ""
---

# Init Claude Setup

You are initializing project-level Claude configuration for this repository. Follow the steps below strictly in order.

## Step 1 — Detect if already fully set up

Check whether `.claude/agents/` or `.claude/settings.local.json` exists in the current working directory.

- If `.claude/agents/` exists: inform the user that this project already has a full local Claude install and no initialization is needed. Stop here.
- If `.claude/settings.local.json` exists: inform the user that this project already has project-level Claude setup and no initialization is needed. Stop here.

## Step 2 — Add .gitignore entries

1. Read `.gitignore` in the project root. If it does not exist, treat it as empty.
2. Ensure the following entries are present (add only the ones that are missing). Group them under a `# .claude` section comment if you are adding any:

```
# .claude
.devcontainer/.env
.claude/settings.local.json
.claude/auth.local.md
.claude-worktrees/
.DS_Store
tasks/**
qa-output/**
debug-output/
.playwright-cli/
```

3. Do not duplicate any entry that already exists in the file (even if it appears outside a `# .claude` section).
4. If entries were already present, note that and skip.

## Step 3 — Create .claude/settings.local.json

1. Check if `.claude/settings.local.json` exists.
2. If it does not exist, create it with this content:
```json
{
  "permissions": {
    "allow": [],
    "deny": []
  }
}
```
3. If it already exists, skip this step and note it.

## Step 4 — Summary

Print a clear summary of what was done:

```
## Claude project setup complete

- .gitignore: [added N entries / already up to date]
- .claude/settings.local.json: [created / already existed]

### Next steps
- Run `claude login` if you haven't already
- Edit `.claude/settings.local.json` to configure per-project tool permissions
- Agents and skills are available globally via your ~/.claude/ install
- The /qa skill uses `playwright-cli` for browser automation — run `playwright-cli install` to set it up
```

## Rules
- Never overwrite files that already exist (settings.local.json) — only create them if missing
- Never remove existing .gitignore entries — only add missing ones

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.