generated: '2026-08-05' method: generated source: openapi/recode-therapeutics-content-openapi.yml summary: >- Three packaged Agent Skills for the ReCode Therapeutics content API. Every operation referenced in them exists in openapi/recode-therapeutics-content-openapi.yml and was verified to return 200 anonymously on 2026-08-05. ReCode Therapeutics publishes no skills, no AGENTS.md and no developer documentation of its own — these are generated by API Evangelist from the observed contract. api: recode-therapeutics:recode-therapeutics-content-api base_url: https://recodetx.com/wp-json authentication: none skills: - name: recode-therapeutics-track-press-releases file: recode-therapeutics-track-press-releases.md summary: >- Incremental sync of the 82-item news stream — clinical milestones for RCT1100 and RCT2100, FDA designations, financings, partnerships and publications — using modified_after + Link rel=next. operations: [listPosts, getPost, listCategories, listTags, getMediaItem] - name: recode-therapeutics-read-corporate-content file: recode-therapeutics-read-corporate-content.md summary: >- Read the 18-page corporate site — purpose, SORT LNP platform, pipeline, patient programs, leadership, legal — plus the 6 company values, as structured records instead of scraped HTML. operations: [listPages, getPage, listValues, getValue, searchContent, listTypes] - name: recode-therapeutics-harvest-events-and-media file: recode-therapeutics-harvest-events-and-media.md summary: >- Harvest the 50 conference and investor event listings and the 305-item media library, including the conference posters and decks published only as PDFs. operations: [listEvents, getEvent, listMedia, getMediaItem, searchContent] deliberate_exclusions: - operations: [listUsers, getUser] path: /wp/v2/users reason: >- DELIBERATE OMISSION, not an oversight. The collection returns 200 with 5 identifiable author records anonymously — author enumeration is left open on this WordPress install. Packaging a working, paginated people-lookup as an agent skill would turn a documented exposure into a distributed tool. API Evangelist records that the endpoint exists (it is in the OpenAPI, with an x-personal-data annotation and a remediation note for the provider) and stops there. Every skill above carries an explicit "do not call /wp/v2/users" instruction. personal_data: true - operations: [administrative namespaces] paths: [/wp/v2/settings, /wp/v2/themes, /wp/v2/plugins, /wp/v2/templates, /wp/v2/menu-items, /wp-json/aioseo/v1/*, /wp-json/elementor*/v1/*, /wp-json/redirection/v1/*, /wp-json/wp-site-health/v1/*, /wp-json/wp-abilities/v1/*] reason: >- All return 401 anonymously. No public credential exists that would lift the denial, so there is no skill to write. Noted specifically for wp-abilities/v1 — the WordPress Abilities API, an agent-facing capability registry the install registers but does not open — so that its absence from this repository reads as a closed door rather than a missed probe. personal_data: false operating_constraints: - No API key, no signup, no developer program. Anonymous read only. - No published rate limit and no RateLimit-* headers. Cloudflare edge. Serialize requests and back off on any non-JSON body. - per_page hard cap 100; 101 returns 400 rest_invalid_param. - Counts and next-page links are in response HEADERS (X-WP-Total, X-WP-TotalPages, Link), not the body. - No status page, no SLA, no changelog, no versioning policy, no support channel. Treat as unmanaged. - Errors are the WordPress envelope, NOT RFC 9457. Branch on `code`, never on `message`. cross_references: openapi: openapi/recode-therapeutics-content-openapi.yml conventions: conventions/recode-therapeutics-conventions.yml errors: errors/recode-therapeutics-problem-types.yml authentication: authentication/recode-therapeutics-authentication.yml lifecycle: lifecycle/recode-therapeutics-lifecycle.yml data_model: data-model/recode-therapeutics-data-model.yml