What data sources does mags-status use?

It calls mags_project_summary, mags_validate_docs, and mags_recall with a query of recent decisions and blockers to surface a full dashboard.

Can the dashboard be customized?

The format is fixed to the defined sections, but you can influence the data by changing the prompts or the recalled memories; for deeper customization, adjust the underlying tool calls.

How do I share or export the dashboard?

The output is a text-based dashboard that you can copy-paste into reports or messages. Use the provided actions to fix docs or remember decisions as needed.

mags-status

Scanned

npx machina-cli add skill doancan/mags/mags-status --openclaw

Files (1)

SKILL.md

1.5 KB

MAGS Status

Display a comprehensive project status dashboard.

Steps

1. Gather data

Call these in parallel:

mags_project_summary — Get overall project summary
mags_validate_docs — Check documentation health
mags_recall with query "recent decisions and blockers" — Surface relevant memories

2. Format the dashboard

Present the output as a clean dashboard. Use this format:

== MAGS Project Status ==

PROJECT
  Name:     <project name>
  Stack:    <tech stack>
  State:    <project state>

DOCUMENTATION HEALTH
  Total docs:      <N>
  Valid:           <N> ok
  Warnings:        <N> (list brief reasons)
  Errors:          <N> (list brief reasons)

RECENT MEMORY
  - <any recalled decisions or notes>

NEXT STEPS
  1. <recommended action>
  2. <recommended action>
  3. <recommended action>

3. Offer actions

After displaying the dashboard, say:

"Run /mags-docs-validate to fix doc issues, or use mags_remember to save important decisions."

Do not take any further action unless the user asks.

Related commands:

Command	Description
`/mags-help`	See all available commands
`/mags-docs-validate`	Check documentation health in detail

Source

git clone https://github.com/doancan/mags/blob/main/skills/mags-status/SKILL.mdView on GitHub

Overview

MAGS Status compiles a project snapshot by querying the project summary, docs health, and recent decisions, then presents a clean dashboard. It helps teams quickly gauge progress, assess documentation quality, and plan next steps. The output uses sections for PROJECT, DOCUMENTATION HEALTH, RECENT MEMORY, and NEXT STEPS.

How This Skill Works

It calls mags_project_summary, mags_validate_docs, and mags_recall with the query 'recent decisions and blockers' in parallel. It formats the results into a structured dashboard with sections PROJECT, DOCUMENTATION HEALTH, RECENT MEMORY, and NEXT STEPS. After displaying, it suggests actions like running /mags-docs-validate or using mags_remember.

When to Use It

Kickoff or weekly status meetings to review overall progress
Sprint reviews focusing on progress, health of docs, and blockers
Assess documentation health before customer demos
Onboard new team members with a concise project snapshot
Prepare executive updates on progress and next steps

Quick Start

Step 1: Gather data by calling mags_project_summary, mags_validate_docs, and mags_recall with query 'recent decisions and blockers' in parallel.
Step 2: Format the dashboard output as shown in the guide, including sections PROJECT, DOCUMENTATION HEALTH, RECENT MEMORY, and NEXT STEPS.
Step 3: After displaying, follow the recommended actions: Run '/mags-docs-validate' to fix doc issues, or use mags_remember to save important decisions.

Best Practices

Run the three data sources in parallel to minimize latency
Validate documentation health metrics before sharing
Keep NEXT STEPS actionable with concrete next actions
Summarize warnings and errors with brief, actionable notes
Refresh data right before stakeholder-facing presentations

Example Use Cases

Open-source project weekly status dashboard
Internal product feature development status
Migration project with documented blockers
R&D sprint review with decisions and next steps
Customer onboarding project health check

Frequently Asked Questions

Add this skill to your agents