Към всички skills
eve-esi-api
EVE Online ESI API patterns and zkillboard integration. Covers ESI endpoints, authentication, data models, zkillboard RedisQ listener, caching strategies, and EVE-specific IDs (characters, corporations, alliances, ships, systems, regions). Use when working with killmail data, fetching EVE universe i
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 6
- Лиценз
- Не е посочен. Проверете в репозитория.
- Последна проверка на записа
- Няма посочена дата
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add ocn/zk-activityСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
EVE ESI API
Workflow
- Select every affected branch and read only its reference:
- public contracts, lifecycle, delivery, or backlog metrics → CONTRACTS.md;
- rate limits, conditional caching, or ESI health → LIMITER-CACHE-HEALTH.md;
- player structures, SSO, JWT, or JWKS → STRUCTURES-AUTH.md;
- R2Z2, RedisQ, zKillboard metadata, or killmail flow → KILLMAIL.md;
- EVE identifiers or identity/observation clocks → IDENTIFIERS.md.
- For each affected ESI HTTP operation:
- record method/path, authentication scope, runtime compatibility header, and typed identifiers;
- run
.claude/skills/eve-esi-api/scripts/inspect-openapi.sh '<path>' [method]; - treat OpenAPI as the latest schema and observed headers/body as the actual request; compare operation
x-compatibility-datewith runtimeX-Compatibility-Date, noting that an unversioned request receives the oldest compatible behavior; - record official schema, observed wire behavior, and project fixtures separately; when they differ, require an explicit tested compatibility rule;
- complete the five-axis evidence note: Wire, Cache, Limiter, Domain, and State. Mark an inapplicable axis
N/Awith its reason.
- For a feed, model, or identifier change without an ESI request, record source authority, typed input/output, permitted transformation or checkpoint transition, preserved provenance, and retry/failure boundary.
- Apply every verification item from each selected branch.
Completion criteria
- An ESI HTTP change is complete when every axis cites wire/project evidence or a justified
N/A, and tests cover each permitted transition and failure boundary. - A feed, model, or identifier change is complete when source authority, typed transformation, state/checkpoint invariant, provenance, and retry/failure behavior are explicit and verified.
- A multi-branch change satisfies both criteria and every selected branch's verification section.