generated: '2026-08-04'
method: generated
source: openapi/enveda-biosciences-content-openapi.yml
note: >-
  Packaged Agent Skills for the only machine-readable surface Enveda exposes: the enveda.com
  WordPress REST content API. Enveda publishes no product API, no developer portal, and no
  skills or AGENTS.md of its own (searched 2026-08-04), 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: all write operations on this API require a WordPress Application Password that no
  third party holds.
api: enveda-biosciences:content
base_url: https://enveda.com/wp-json/wp/v2
auth: none (anonymous read; writes are gated and out of scope for these skills)
skills:
- file: enveda-biosciences-read-newsroom.md
  name: Read the Enveda newsroom
  description: >-
    Page through Enveda's published news releases (the `news` custom post type) and In-Veda
    blog posts, resolving categories, authors and featured images in a single request via
    _embed.
  api: openapi/enveda-biosciences-content-openapi.yml
  operations: [getNews, getNewsById, getNewsCategory, getNewsCategoryById, getPosts, getPostsById,
    getIssue, getUsers]
- file: enveda-biosciences-trial-sites.md
  name: List Enveda clinical-trial sites and trial pages
  description: >-
    Retrieve the 40-record clinical-trial site directory (`wpsl_stores`) and the atopic
    dermatitis / asthma recruitment pages that consume it, as JSON instead of scraping the
    trial-finder widget.
  api: openapi/enveda-biosciences-content-openapi.yml
  operations: [getWpslStores, getWpslStoresById, getWpslStoreCategory, getWpslStoreCategoryById,
    getPages, getPagesById]
- file: enveda-biosciences-search-and-people.md
  name: Search enveda.com and resolve people
  description: >-
    Run a cross-content-type search, resolve each lightweight result pointer into the full
    object by branching on subtype, and read the leadership / board / advisor roster from the
    `person` custom post type.
  api: openapi/enveda-biosciences-content-openapi.yml
  operations: [getSearch, getPostsById, getPagesById, getNewsById, getPerson, getPersonById,
    getPersonCategory, getPersonCategoryById, getTypes, getTypesByType, getMedia, getMediaById]
cross_references:
  conventions: conventions/enveda-biosciences-conventions.yml
  errors: errors/enveda-biosciences-problem-types.yml
  data_model: data-model/enveda-biosciences-data-model.yml
  authentication: authentication/enveda-biosciences-authentication.yml
  examples: examples/enveda-biosciences-examples.yml
not_covered:
- surface: Enveda MCP Server (WordPress MCP Adapter)
  reason: >-
    tools/list and initialize are both authentication-gated (HTTP 401 rest_forbidden, observed
    2026-08-04), so no tool name or input schema is publicly observable. 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://enveda.com/wp-admin/authorize-application.php. No third party holds one, so writes
    are deliberately out of scope.
- surface: Enveda's PRISM platform / molecule library
  reason: >-
    Enveda's actual scientific platform — the PRISM foundation model and the plant-molecule
    library — has no public API, no endpoint and no documentation. It is described in prose on
    https://enveda.com/platform/ only. Nothing is written against a surface that does not exist.