skills.rest
fstr21
fstr21COMMUNITY
Explore all skills by this author →
GitHub

Config Check

Validate .claude configuration files and report statuses with timestamps.

Updated Aug 23, 2026
Search Tags:#Claude AI#project setup#verification#configuration#setup#environment#health check
One-click install
npx skills add https://github.com/fstr21/sportsbot --skill config-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Config Check
Source: https://github.com/fstr21/sportsbot/tree/main/.claude/skills/config_check
Command: npx skills add https://github.com/fstr21/sportsbot --skill config-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Incorrect or missing configuration files can prevent Claude from operating effectively, leading to frustrating errors and wasted time. This Skill ensures all essential .claude/ context files are present and up-to-date, guaranteeing a stable environment.

Core Features & Use Cases

  • Required File Verification: Confirms the existence of critical .claude/ context files like CLAUDE.md, architecture.md, and constraints.md.
  • Timestamp Reporting: Displays the last modified timestamp for CLAUDE.md, indicating the freshness of your core instructions.
  • Automated Health Check: Can be run automatically at session start to ensure a stable environment before any complex tasks begin.
  • Use Case: Run this Skill at the beginning of a session or after pulling new changes from the repository to quickly verify your Claude setup is ready for action.

Quick Start

Run the configuration check

python .claude/skills/config_check/check_config.py

Frequently Asked Questions about Config Check

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

FAQPage Schema
How do I verify my Claude configuration files are present and valid?▼

Configuration verification checks that critical `.claude/` context files like `CLAUDE.md`, `architecture.md`, and `constraints.md` exist and reports their status as [OK], [WARN], or [FAIL], plus displays the last modified timestamp for `CLAUDE.md` to confirm your setup is current.

Why would my Claude setup fail to start, and how can I prevent it?▼

Missing or incorrect configuration files prevent Claude from operating effectively. Running a configuration health check at session start ensures all essential `.claude/` files are present before complex tasks begin, catching problems early.

When should I run a configuration check after project changes?▼

Run the configuration verification after pulling new repository changes or updating your project setup to quickly confirm your `.claude/` environment is ready and all required context files are in place and up-to-date.

What does it mean when a configuration file shows a [WARN] or [FAIL] status?▼

Status codes indicate file integrity: [OK] means the file exists and is current, [WARN] signals a potential issue like staleness, and [FAIL] indicates a missing or corrupted critical configuration file that requires immediate attention.

Can I automate configuration verification at the start of each session?▼

Yes, configuration checks can run automatically when a session begins, providing an immediate health report before you start work and preventing errors from undetected missing or outdated files.

Related Skills

Explore More Software Engineering Skills→
craftwerk-studiocraftwerk-studio

scaffold

Generate project directory structures and starter files from SPEC.md and CLAUDE.md.

Official
Intermediate
bhianerdbhianerd
1

browse

Run automated headless browser tasks to verify web UI behavior.

Community
Advanced
furedeafuredea
1

nix-dev-init

Automates repository setup, Nix flake configuration, and direnv for project environments.

Community
Intermediate
Kirankumar2604Kirankumar2604

workflows

Manage persistent shell-based background processes and long-running services.

Community
Intermediate