monitoring

Generate project status reports, burndown updates, and health checks.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/LauraFlorentin/skills-marketplace --skill monitoring-lauraflorentin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring
Source: https://github.com/LauraFlorentin/skills-marketplace/tree/main/project-management/skills/monitoring
Command: npx skills add https://github.com/LauraFlorentin/skills-marketplace --skill monitoring-lauraflorentin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates project monitoring by providing standardized status updates, risk reviews, and health insights, reducing manual reporting overhead and improving decision speed.

Core Features & Use Cases

  • Automated Status Reporting: generate regular project health updates with RAG scoring and actionable items.
  • Burndown & Progress Tracking: visualize progress against plan, forecast variances, and identify at-risk areas.
  • Risk, Dependency, and Health Checks: maintain risk registers, dependency maps, and multi-dimensional health assessments for software and general PMs.
  • Use Case: When stakeholders request a quick project snapshot, the skill compiles an up-to-date status report including top risks and mitigation actions.

Quick Start

Generate a concise project status report for the current sprint.

Frequently Asked Questions about monitoring

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

FAQPage Schema
How do I generate an automated project status report for my current sprint?

To generate a project status report, the skill compiles sprint status updates, RAG scoring, and actionable items into structured content. It automatically formats the output with required YAML frontmatter, providing a quick project snapshot including top risks.

What is included in a project health check for non-software projects?

A project health check involves multi-dimensional health assessments, risk register maintenance, and dependency mapping. It evaluates team health and tracks risks, ensuring both software and general projects maintain clear visibility into potential issues.

Can I track burndown and forecast variances without manual reporting overhead?

Yes, burndown tracking visualizes progress against the initial plan to forecast variances. By automating these updates, the skill reduces manual reporting overhead and helps project managers identify at-risk areas early.

Does this project monitoring approach work for both software and general PMs?

Project monitoring applies to both software and non-software projects. It covers sprint status, risk reviews, and dependency tracking, making it suitable for software development teams and general project managers alike.

What's the best way to maintain a risk register and dependency map for stakeholders?

The best way to maintain a risk register is through automated risk reviews and dependency tracking. This skill compiles up-to-date status reports that highlight top risks and mitigation actions, improving stakeholder decision speed.

Are there limitations to automating status reporting with YAML frontmatter?

A limitation of this status reporting approach is that it enforces strict YAML frontmatter with name and description fields. Outputs are structured for PM workflows using predefined triggers, which may require adjustment for non-standard reporting formats.