HTTP Status Code Lookup and Website Accessibility Check

Problem It Solves

When an endpoint returns unexpected responses or a page appears unavailable, engineers often manually inspect HTTP status codes, response timing, and access paths before forming a diagnosis. This skill narrows status code lookup and website accessibility checks into a single service call, useful for quick troubleshooting, inspection records, pre- and post-deployment validation, and producing readable structured notes. It focuses on external access signals rather than internal application logic: whether 200, 301, 404, or 5xx responses indicate the site is reachable and serving expected content.

How It Works

The skill calls an analysis service provided by XiaoMeng AGI. Inputs can include text, CSV, JSON, Excel files, API endpoints, or custom requirements. A typical workflow is:
- Prepare the target site, endpoint, or request context
- Trigger the analyze script to run the lookup
- Complete payment for roughly 5 CNY per request through ClawTip
- Read the Data Overview, Analysis, Recommendations, and Action Plan output

For operations use cases, the first two sections are usually most important: confirm the status and accessibility conclusion first, then review the suggested follow-up checks.

Boundaries and Caveats

This is a per-request paid remote service that depends on https://xiaomeng-api.qisir.com and the ClawTip payment path, so it is not suitable for offline or network-restricted environments. The output is useful for quick diagnosis and records, but it should not replace a full observability setup such as distributed tracing, log aggregation, synthetic monitoring coverage, or alerting loops. If the target requires login, regional access, custom headers, or client-side rendering, the result may only reflect the visibility of the checked path at that moment.