setup-status

Reports green/amber/red health status for all Dream plugin infrastructure files in a project.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill setup-status-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-status
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/setup-status
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill setup-status-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers using the Dream plugin cannot easily tell whether their project setup is complete, fresh, or broken. This Skill performs a non-destructive health check across every generated file and configuration, surfacing exactly what is missing, stale, or misconfigured before it causes silent failures. ## Core Features & Use Cases - Infrastructure Health Checks: Verifies CLAUDE.md identity placeholders, memory files, .claude/rules deployment manifests, command stubs, architecture docs, the knowledge graph, file caches, and ignore-file coverage, reporting green/amber/red per item. - Security & Governance Checks: Detects credential leak risks (unprotected settings.local.json, secrets in committed settings.json), open findings across review ledgers, hook integrity via hash verification, and audit-trail liveness. - Actionable Remediation: Every amber/red status includes the exact command to fix it (e.g., /setup-init, /setup-sync, /gitignore-sync, REFRESH RULES). - Use Case: Before starting work on a project, run the status check to confirm the knowledge graph is fresh, rules are deployed, hooks are wired, and no critical findings are open. ## Quick Start Ask the assistant to check the Dream plugin setup status and report what is missing or stale in this project.

Frequently Asked Questions about setup-status

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

FAQPage Schema
How do I check if the Dream plugin is set up correctly in my project?

Run the setup-status skill, which performs a non-destructive health check on all plugin infrastructure. It reports green, amber, or red status for each item including CLAUDE.md, memory files, rules, hooks, and the knowledge graph, with the exact command to fix any issue.

What does the setup status health check actually verify?

It checks CLAUDE.md identity placeholders, memory files, deployed rule manifests and staleness, command stubs, architecture docs, the knowledge graph freshness flag, ignore-file coverage, hook integrity via SHA-256 hashes, open findings in review ledgers, and model version freshness.

Does the status check modify any project files?

No, the check is strictly read-only. It reads file metadata and runs grep and Node.js inspections but never writes, deletes, or modifies anything. Remediation is always left to explicit follow-up commands like /setup-init or /setup-sync.

Why does the status check report a credential leak risk?

A red credential warning appears when .claude/settings.local.json is not covered by the repo's ignore file or is already tracked in TFVC, or when a secret is detected in the committed .claude/settings.json. The report includes the exact fix, such as running /gitignore-sync or untracking the file.

What should I do when rules show as stale in the status report?

Stale rules mean they were deployed over 180 days ago or the build files changed since detection. Run /setup-sync to redeploy, or use the REFRESH RULES command shown in the report to review a three-way merge of plugin changes against your edits.