← Physical ValidationCONTENT HISTORY

Update to Physical Validation

Snapshot Nov 13, 2026 · 00:10 UTC · version 1.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Physical Validation and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Find, review, delete, or submit an existing Physical Validation account draft, including drafts started in the browser. Use when a person asks about their saved experiment requests.",
  "included_files": [],
  "name": "manage-request-drafts",
  "skill_md_contents": "---\nname: manage-request-drafts\ndescription: Find, review, delete, or submit an existing Physical Validation account draft, including drafts started in the browser. Use when a person asks about their saved experiment requests.\n---\n\nUse the host's managed OAuth connection for the person's Physical Validation account. If the connector requests sign-in, use the host's connection flow. Work only with drafts returned for that connected account.\n\n- Use `list_request_drafts` to find the requested draft. Follow a returned cursor when needed. Identify the draft by its returned title and ID, and clarify if several match the person's description.\n- Use `get_request_draft` before reviewing, deleting, or submitting. Preserve its full contents, ID, and current revision. Surface missing information and offer its returned browser review link for editing or attachments.\n- The exposed MCP draft tools list, read, and delete existing drafts. `prepare_request` produces a review link without persisting an account draft. Do not claim a draft was created or updated by one of those reads or preparation calls. If the person wants edits saved, use the browser review link.\n- Delete only the draft the person explicitly asked to remove, using its current revision with `delete_request_draft`. A revision conflict means the draft changed. Read it again and verify that the deletion still matches the person's intent before retrying.\n- Submit a saved draft only after the person agrees to its complete contents and the service terms and privacy notice. Use `submit_request` with the draft ID and current revision, preserving the idempotency key for an unchanged retry. Report the returned submission receipt and any `draftDeleted` result accurately.\n\nThe draft tools do not provide live request progress. Use the service's returned links when the person needs information beyond the exposed tools.\n"
}

SHA-256 of public snapshot: 868033b4bdf30e9dc893e43954430231b018999678cafbee5645c081c0b15f53