verify-claude-setup
Verify .claude directory configuration is complete and correct. Use when checking if agents, hooks, rules, and memory are properly set up, or after making changes to .claude configuration.
Best use case
verify-claude-setup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Verify .claude directory configuration is complete and correct. Use when checking if agents, hooks, rules, and memory are properly set up, or after making changes to .claude configuration.
Teams using verify-claude-setup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/verify-claude-setup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How verify-claude-setup Compares
| Feature / Agent | verify-claude-setup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Verify .claude directory configuration is complete and correct. Use when checking if agents, hooks, rules, and memory are properly set up, or after making changes to .claude configuration.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Verify .claude Setup Quick verification that .claude directory is properly configured. ## When to Use - After updating agents, rules, hooks, or memory - Before starting complex work (ensure system is ready) - User asks "is everything set up correctly?" - Troubleshooting configuration issues ## Verification Checklist ### 1. Agents (should have 6) ```bash ls .claude/agents/ | wc -l ``` Verify all agents have: - Proper YAML frontmatter - Research-First Protocol section - Clear responsibilities ### 2. Hooks (should have 11 scripts + README) ```bash ls .claude/hooks/scripts/*.ts | wc -l ``` Check: - All scripts executable (`chmod +x`) - All have Bun shebang (`#!/usr/bin/env bun`) - settings.json has all hooks configured - Pre-tool and Post-tool hooks exist ### 3. Rules (should have research-first-protocol.md) ```bash ls .claude/rules/*.md ``` Verify: - research-first-protocol.md exists - Has `alwaysApply: true` ### 4. Memory (should have 8 files) ```bash ls .claude/memory/ | wc -l ``` Check CLAUDE.md imports all: - research-first-enforcement.md - coding-standards.md - testing-standards.md - architecture-patterns.md - common-workflows.md - build-commands.md - asset-forge-guide.md - security-protocols.md ### 5. Settings ```bash grep -c "hooks" .claude/settings.json ``` Verify: - SessionStart, UserPromptSubmit hooks - PreToolUse (Bash, Write, Edit) hooks - PostToolUse (Write, Edit, Read, Grep, Glob) hooks - PreCompact, Stop, SubagentStop, SessionEnd hooks ### 6. Commands (should have ~20) ```bash find .claude/commands -type f -name "*.md" | wc -l ``` ## Quick Verification Run all checks: ```bash echo "Agents: $(ls .claude/agents/ | wc -l)" echo "Hooks: $(ls .claude/hooks/scripts/*.ts | wc -l)" echo "Rules: $(ls .claude/rules/*.md | wc -l)" echo "Memory: $(ls .claude/memory/ | wc -l)" echo "Commands: $(find .claude/commands -type f -name "*.md" | wc -l)" echo "Skills: $(ls .claude/skills/ | wc -l)" ``` ## Expected Counts - Agents: 6 - Hook Scripts: 11 - Rules: 2 (README + research-first-protocol) - Memory: 8 - Commands: ~20 - Skills: ~40 ## Report Format Provide summary: ``` ✅ Agents: 6/6 with Research-First Protocol ✅ Hooks: 11/11 executable, all configured ✅ Rules: research-first-protocol.md active ✅ Memory: 8/8 files, all imported in CLAUDE.md ✅ Commands: 20 organized slash commands ✅ Skills: 40 skills ready Status: .claude configuration VERIFIED ``` Or if issues found: ``` ⚠️ Agents: Missing Research-First Protocol in database-specialist.md ⚠️ Hooks: pre-tool-write.ts not executable ❌ Memory: research-first-enforcement.md not imported in CLAUDE.md Status: Configuration INCOMPLETE - needs fixes ```
Related Skills
claude-player
An AI-powered Game Boy emulator agent that uses Claude's vision and reasoning to autonomously play Game Boy games.
claude-opus-4-5-migration
Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.
claude-config-management
Claude Code設定(リポジトリルート)の構成管理ガイド。ファイルレベルsymlinkによる設定管理、管理対象の追加・削除、Taskfileタスクの実行方法を提供する。「設定ファイルを追加して」「新しいスキルを追加して」「symlinkの状態を確認して」「Claude設定を変更して」のようにClaude Code設定の構成変更を行うときに使用する。
agent-setup
Configure AI coding agents like Cursor, GitHub Copilot, or Claude Code with project-specific patterns, coding guidelines, and MCP servers for consistent AI-assisted development.
agent-canvas-setup
Dependency checker and installer for agent-canvas, agent-eyes, and canvas-edit skills. Use BEFORE running any canvas skill for the first time, or when canvas skills fail with import/browser errors. Triggers on "setup agent canvas", "install canvas dependencies", "canvas not working", "playwright not found", or any setup/installation request for canvas skills.
academic-course-setup-automator
When the user needs to set up multiple academic courses in a learning management system (Canvas/LMS) from structured data sources. This skill automates the entire workflow extracting course schedules from emails/attachments, matching instructors from CSV files, creating courses, enrolling teachers, publishing announcements with class details, uploading syllabi, enabling resource sharing for instructors teaching multiple courses, and publishing all courses. Triggers include course schedule setup, Canvas/LMS administration, academic term preparation, instructor assignment, syllabus distribution, and multi-course management.
32-analyze-verify-150
[32] ANALYZE. Ensure every critical claim has verifiable evidence with confidence levels. Each fact must have source + confidence percentage. If confidence <85%, enter Loop150 to find more sources. Use for critical decisions, factual claims, legal/compliance work, or any situation where unverified claims are dangerous.
varlock-claude-skill
Secure environment variable management ensuring secrets are never exposed in Claude sessions, terminals, logs, or git commits
templar-miner-claude-skill
This skill should be used when setting up, optimizing, or managing Templar AI miners on Bittensor Subnet 3 (netuid 3). Use it for tasks involving miner configuration, performance optimization, troubleshooting gradient scoring issues, managing Bittensor wallets with btcli, monitoring miner metrics, renting GPUs via Basilica for mining operations, or strategizing to achieve top miner ranking in the Templar decentralized training network. Integrates seamlessly with the basilica-cli-helper skill for GPU rentals.
setup-workflow
Initial setup workflow for claude-pilot plugin - directory creation, statusline configuration, documentation sync, GitHub star request
scode-dist-rust-setup
Set up or standardize a Rust repository with cargo-dist release automation, Linux-focused CI with macOS release-plan tag gates, git-cliff changelog generation, Conventional Commit PR title enforcement, and Homebrew publishing to scode/homebrew-dist-tap. Use when creating a new Rust release pipeline or migrating an existing repo to this exact distribution model.
Project Setup and CCAGI Integration
Complete project initialization including Node.js/TypeScript setup, GitHub integration, and CCAGI framework integration. Use when creating new projects or integrating CCAGI components.