42-status

Aggregate SEO project state into a status dashboard from 42-reports files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/chapter42/42-SEO-Skills --skill 42-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 42-status
Source: https://github.com/chapter42/42-SEO-Skills/tree/main/skills/42-status
Command: npx skills add https://github.com/chapter42/42-SEO-Skills --skill 42-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a consolidated status overview of an active SEO project by aggregating core state data from 42-reports and related artifacts into a single dashboard.

Core Features & Use Cases

  • Reads STATE.md, capabilities.json, and all reports/ and exports/ to construct a real-time project snapshot.
  • Highlights phase progress, findings count, API costs, blockers, and next actions for quick decision making.
  • Use Case: when stakeholders request a concise project status or when you need an up-to-date health check before a stand-up.

Quick Start

Use the status command to display the current project dashboard for the active domain.

Frequently Asked Questions about 42-status

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

FAQPage Schema
How do I get a live status dashboard for my active SEO project?

You can generate a consolidated SEO project status dashboard by reading core state files, capabilities.json, and the reports/ directory to highlight phase progress, API costs, and blockers.

What is the best way to prepare stakeholder updates from local SEO reports?

Aggregate local SEO project state files and exports into a single dashboard to highlight findings count, API costs, blockers, and next actions for stakeholder updates.

Does the 42-status dashboard require write access to modify project files?

No, the status dashboard operates with read-only access to local project files, ensuring your STATE.md, capabilities.json, and exports directories remain unmodified during health checks.

Can I track API costs and phase progress for an active SEO orchestrator project?

Yes, you can track API costs and phase progress by aggregating findings and state data from the 42-reports directory, presenting them in a consolidated project health dashboard.

What limitations exist when checking the health of an SEO project locally?

The health check is limited to read-only access of projects stored under 42-reports, relying on existing STATE.md and capabilities.json files, and does not modify or generate new project artifacts.