project-status

Generates evidence-backed project status reports covering Azure resource health, sync freshness, and deployment currency.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Teams often cannot tell at a glance whether a deployed project is healthy, whether scheduled data syncs are running on time, or whether the deployed build matches the local Git revision. This Skill consolidates local Git state, sync telemetry, and read-only Azure resource evidence into one validated status report. ## Core Features & Use Cases - Azure resource health checks: Queries the subscription and cloud recorded in .azure/environment.json read-only to inventory resources and classify them as healthy, degraded, or unknown. - Sync freshness detection: Marks syncs failed, stale, healthy, or unknown based on heartbeats, expected intervals, and grace periods. - Deployment currency comparison: Compares local Git HEAD, CI artifacts, and deployed build markers to report current, outdated, unknown, or not-deployed. - Use Case: Ask whether an Azure Government web app is running and matches your local revision, and receive reports/project-status.json and reports/project-status.md with evidence for every conclusion. ## Quick Start Ask the agent to run the project-status skill and report whether the current deployment, Azure resources, and data syncs are healthy and up to date.

Frequently Asked Questions about project-status

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

FAQPage Schema
How do I check if my Azure deployment matches my local Git revision?

Run the project-status skill, which compares local Git HEAD, the latest validated CI artifact, and the deployed build or version marker. It reports the deployment as current, outdated, unknown, or not-deployed, and never claims current when no deployed marker exists.

How to detect stale or failed scheduled data syncs?

The skill reads sync status, heartbeat, and telemetry reports and classifies each sync. A sync is failed on its latest failure, stale when its last success exceeds the expected interval plus grace period, and unknown when no evidence exists.

Does this skill work with Azure Government cloud?

Yes. It uses the cloud and endpoint catalog recorded in the project's `.azure/environment.json` profile and verifies the Azure CLI active cloud matches it. It never infers or switches between Commercial and Government endpoints.

Can this skill restart or fix unhealthy Azure resources?

No. The skill is strictly read-only and only writes two report files under `reports/`. Azure login, deployment, sync execution, restart, cleanup, commit, and push all require separate approval through other workflows.

What happens when Azure authentication or evidence is unavailable?

The skill returns a partial status report and classifies each unavailable evidence source as unknown, listing the gaps in the limitations array. It never reports an unavailable resource, sync, or deployment as healthy or current.