mcpField
S
service-health-check

service-health-check

github.com/revitalb-portCloud & DevOps067 installsUpdated 10w ago
Repository

About service-health-check

service-health-check is a skill for producing a service health overview from Port's catalog. It combines service metadata, scorecard status, incidents, deployments, and dependency checks for deployment reviews, on-call handoffs, and investigations.

Key features

  1. 01Retrieve service ownership and dependency data
  2. 02Review production-readiness scorecards
  3. 03Summarize recent incidents and MTTR
  4. 04Inspect recent deployments
  5. 05Check dependency health recursively

Use cases

  1. 01Assess a service before deployment
  2. 02Prepare an on-call rotation handoff
  3. 03Investigate service issues
  4. 04Review capacity or planned changes

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/revitalb-port/skills-registry-demo --skill service-health-check

After installing, type/service-health-checkin Claude Code to confirm it loaded.

Details

From the project README

Service Health Check Skill

Get a comprehensive health overview of any service using Port's catalog.

When to Use

  • Before deploying to a service
  • During on-call rotation handoff
  • Investigating service issues
  • Planning capacity or changes

Health Check Process

Step 1: Basic Service Info
get_entity(blueprint="service", identifier="service-name", include=[
  "tier", "team", "owner", "on_call", 
  "depends_on", "repository", "scorecard_status"
])
Step 2: Scorecard Status

Check production readiness:

get_entity(blueprint="service", identifier="service-name")
# Look at scorecard properties:
# - has_readme
# - has_runbook
# - has_monitoring
# - has_slo
# - security_scan_passed
Step 3: Recent Incidents
list_entities(blueprint="incident", query={
  primary_service: "service-name",
  created_at: ">30d"
})

Count by severity and calculate MTTR.

Step 4: Recent Deployments
list_entities(blueprint="deployment", query={
  service: "service-name",
  deployed_at: ">7d"
})
Step 5: Dependency Health

For each dependency:

get_entity(blueprint="service", identifier="dep-service")

Check their health status recursively.

Output Format

# Service Health: [service-name]

## Overview
| Property | Value |
|----------|-------|
| Tier | Tier1-Critical |
| Team | payments-team |
| Owner | [email protected] |
| On-Call | [email protected] |

## 📊 Scorecard: 4/5 Passing
| Check | Status |
|-------|--------|
| Has README | ✅ |
| Has Runbook | ✅ |
| Has Monitoring | ✅ |
| Has SLO | ✅ |
| Security Scan | ❌ Last scan failed |

## 🚨 Incidents (Last 30 Days)
| Severity | Count | MTTR |
|----------|-------|------|
| Sev1 | 0 | - |
| Sev2 | 1 | 45min |
| Sev3 | 2 | 2h |

## 🚀 Recent Deployments
| Date | Version | Status |
|------|---------|--------|
| 2026-05-04 | v2.3.5 | ✅ Success |
| 2026-05-02 | v2.3.4 | ✅ Success |

## 🔗 Dependencies
| Service | Health | Tier |
|---------|--------|------|
| user-api | 🟢 Healthy | Tier1 |
| db-primary | 🟢 Healthy | Tier1 |
| cache-redis | 🟡 Degraded | Tier2 |

## Recommendations
1. Fix failing security scan
2. Monitor cache-redis degradation

Quality Checklist

  • Retrieved all scorecard data
  • Calculated incident metrics
  • Checked all dependencies
  • Provided actionable recommendations

Comments

Markdown supported