- Home
- Skills
- Codyswanngt
- Lisa
- Ops Verify Health
ops-verify-health_skill
- TypeScript
1
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill codyswanngt/lisa --skill ops-verify-health- SKILL.md2.7 KB
Overview
This skill runs automated health checks across all environments to verify frontend URLs and backend GraphQL endpoints and to report response times. It discovers environment endpoints from project constants and .env files, then executes quick HTTP and GraphQL probes to surface status and timing metrics. Results are presented in a concise table highlighting failures and slow responses.
How this skill works
The skill reads frontend URLs from environment constants and GraphQL base URLs from environment files to build an environment table. For each environment it performs a frontend HTTP probe and inspects the first lines of HTML for framework markers. It posts a minimal GraphQL query for basic liveness and optionally runs an introspection query for schema validation. Response codes and timings are collected and flagged when status != 200 or time > 5s.
When to use it
- Before or after deployments to verify services are reachable in each environment.
- During CI/CD pipeline stages to gate promotions based on service health.
- For periodic monitoring or on-demand checks when investigating incidents.
- When validating new environment configuration or DNS changes.
Best practices
- Limit max-time for curl probes (e.g., 10s) to avoid long-running checks.
- Run the lightweight __typename query for liveness and use introspection only when deeper validation is needed.
- Flag any non-200 status or response time over 5s as a concern and surface details in the report.
- Keep environment URL mappings current in constants and .env files so checks remain accurate.
- Include EAS update:list to verify OTA deployments for each branch when relevant.
Example use cases
- Run health checks across local, dev, staging, and production before a release.
- Integrate into CI to prevent promoting a build if frontend or backend are down.
- Use during incident triage to quickly determine which environments or services are affected.
- Schedule nightly checks and send the generated table to the ops channel for review.
FAQ
The skill probes frontend URLs and backend GraphQL base URLs discovered from project constants and environment files.
How are slow or failing services flagged?
Any service returning a status other than 200 or taking longer than 5 seconds is flagged as a concern in the report.