generated: '2026-08-26'
method: generated
source: openapi/scimar-content-openapi.yml
note: >-
  Packaged Agent Skills for the only machine-readable surface Scimar exposes: the scimar.ca WordPress
  REST content API. Scimar publishes no product API, no developer portal, and no skills or AGENTS.md of
  its own (searched 2026-08-26), so these were GENERATED by the API Evangelist enrichment pipeline.
  Every operationId referenced in every skill was verified to exist verbatim in the referenced OpenAPI —
  none was invented. Each skill is read-only by design: every write operation on this API requires a
  WordPress Application Password that no third party holds.
api: scimar:content
base_url: https://scimar.ca/wp-json/wp/v2
auth: none (anonymous read; writes are gated and out of scope for these skills)
skills:
- file: scimar-read-news-and-science.md
  name: Read the Scimar news archive and science pages
  description: >-
    Page through Scimar's 46 published news stories and its 19 Science & Products and About pages as
    JSON, resolving categories, authors and featured images in a single request via _embed, and
    trimming the large All in One SEO block that this site injects into every record.
  api: openapi/scimar-content-openapi.yml
  operations: [getPosts, getPostsById, getPages, getPagesById, getCategories, getCategoriesById,
    getTags, getMedia, getMediaById]
- file: scimar-search-the-site.md
  name: Search scimar.ca and resolve results
  description: >-
    Run a cross-content-type search, resolve each lightweight result pointer into the full object by
    branching on subtype or following _links.self, and check the type/taxonomy/status registries first
    to avoid chasing sitemap sections that have no REST route.
  api: openapi/scimar-content-openapi.yml
  operations: [getSearch, getPostsById, getPagesById, getTypes, getTypesByType, getStatuses,
    getTaxonomies, getMediaById]
cross_references:
  conventions: conventions/scimar-conventions.yml
  errors: errors/scimar-problem-types.yml
  data_model: data-model/scimar-data-model.yml
  authentication: authentication/scimar-authentication.yml
  rate_limits: rate-limits/scimar-rate-limits.yml
not_covered:
- surface: Scimar MCP servers (WordPress MCP Adapter)
  reason: >-
    tools/list is authentication-gated on both /wp-json/mcp/mcp-oauth-server (401 mcp_unauthorized,
    with an RFC 9728 challenge) and /wp-json/mcp/mcp-adapter-default-server (401 rest_forbidden),
    observed 2026-08-26, and the backing wp-abilities registry is gated too. No tool name or input
    schema is publicly observable, so no skill is written against a tool set that cannot be verified.
- surface: Write operations on wp/v2
  reason: >-
    Every create/update/delete operation requires a WordPress Application Password issued from
    https://scimar.ca/wp-admin/authorize-application.php. No third party holds one, so writes are
    deliberately out of scope. Their reversal semantics are still recorded in
    conventions/scimar-conventions.yml for anyone who does hold credentials.
- surface: SciMar NuPa Test, NuPa Renew, NuPa Daily and Hepatalin-S
  reason: >-
    Scimar's actual products — a diagnostic test meal and three therapeutic candidates — have no API,
    no endpoint and no documentation. They are described in prose on
    https://scimar.ca/science-products/product-pipeline/ only. Nothing is written against a surface
    that does not exist.
- surface: Team and Member Category
  reason: >-
    Both appear in sitemap.xml and llms.txt but neither is a registered REST route — GET /wp/v2/types
    returns no custom post type. Recorded here so a later round does not write a skill against them.