generated: '2026-08-06'
method: generated
source: >-
  openapi/accelsius-*-openapi.yml (every operationId referenced below was taken from the specs in
  this repo; none are invented) plus conventions/accelsius-conventions.yml and
  errors/accelsius-problem-types.yml
note: >-
  Accelsius publishes no AGENTS.md, no skills, no llms.txt and no developer documentation of any
  kind — searched 2026-08-06. These three skills were GENERATED by API Evangelist over the derived
  contract for the public WordPress content API behind accelsius.com, and are grounded only in
  operations verified to return HTTP 200 anonymously. Every one of them leads with the same
  operational constraint, because on this host it is the constraint that decides whether the skill
  works at all: the origin runs a behavioural firewall that will 403 a caller with no warning and
  no rate-limit header.
skills:
- file: accelsius-research-cooling-library.md
  name: Research the Accelsius technical library
  description: >-
    Find and read Accelsius white papers, case studies, benchmark posts and podcasts on two-phase
    direct-to-chip cooling, resolving content classes and topic tags correctly.
  api: openapi/accelsius-content-api-openapi.yml
  operations: [listCategories, listTags, listContent, getContentItem, listMedia]
- file: accelsius-harvest-site-content.md
  name: Harvest the Accelsius site
  description: >-
    Mirror the product pages, the resource library, the press-coverage type and the media library,
    driven by the discovery routes rather than a hardcoded content model, and without tripping the
    firewall.
  api: openapi/accelsius-discovery-api-openapi.yml
  operations: [getRootIndex, listPostTypes, listTaxonomies, listPages, getPage, listContent, listNews, listMedia]
- file: accelsius-track-company-news.md
  name: Track Accelsius announcements and coverage
  description: >-
    Watch for new Accelsius press releases, product announcements and third-party press coverage,
    separating the two content types the site uses for them.
  api: openapi/accelsius-news-api-openapi.yml
  operations: [searchSite, listContent, listNews, getNewsItem, getContentItem]
exclusions:
- route: /wp/v2/users
  status: 200
  reason: >-
    Deliberate. The WordPress user directory on this host answers anonymously with 14 author
    records — display names, slugs, descriptions, avatar URLs. It is a directory of named
    individuals, so no skill walks it, no MCP tool binds to it, and no operation for it appears in
    openapi/. Per the API Evangelist enrichment PII guardrail: document the exposure, do not ship
    the exploit. The exposure itself is recorded in
    authentication/accelsius-authentication.yml under `exposed_personal_data`.