Add OpenClaw EVE ESI Skill to community services

[burnshall-ui]

This resubmits #273, which @steven-noorbergen closed on 2026-02-09 for two reasons. Both have been addressed.

"Public for at least three months." The repository has been public since 2026-02-08 — a little over six months now — and has received regular updates since, most recently today.

"Using the old Swagger interface / versioned URLs." Both are gone:

• Requests go to https://esi.evetech.net with no version prefix and carry X-Compatibility-Date, pinned to a reviewed date. /latest, /legacy, /dev and /vN are stripped if one reaches the client from an old copy-pasted example.
• The documentation now points at meta/openapi.json rather than swagger.json, and explains that a request omitting the compatibility date is served the oldest supported behaviour rather than the newest.
• Migrating surfaced one real break, now fixed: GET /route/ became a POST with a request body at compatibility date 2025-09-30.

While in there, a few things were brought in line with the best-practices page: 429 is retried after Retry-After alongside the older 420 handling, a rate limit bucket below 20% warns, and every ESI and SSO request now sends a User-Agent naming the application, its version and its repository — the auth scripts previously announced themselves as Python-urllib. Token verification moved to the /v2/oauth/verify endpoint named by the SSO metadata document.

Against the listing requirements

1. EVE-related — an ESI client, nothing else.
2. Developer License Agreement — the README carries the proprietary notice from §7.1. The tool is free, unmonetised and carries no advertising.
3. Public — GitHub (MIT) and ClawHub.
4. Production-ready — verified against a live account: 2,914 assets across three pages, six PI colonies, wallet, mail and killmails; 32 regression tests.
5. Public for three months — six months.
6. Actively maintained — yes.

The page follows sample-service, keeps the required search: exclude: true, and is picked up by the existing community/*/index.md nav glob.

One note on scope

The description deliberately does not claim scheduled alerts or notification delivery. The skill defines and validates a config vocabulary for them but ships no poller, scheduler or sender, and I would rather the listing say what the code does.

I was not able to run make test locally — the host has no pip/ensurepip and I did not want to install system packages on it — so I verified by hand instead: front matter matches the template key for key, type: service and the title match the directory name, the macro's required fields are present, all three outbound links return 200, and the page contains no relative links that strict mode could flag. Happy to fix anything CI turns up.