AI Agent Hub
Back to skills
Pathology Slice Analysis icon

Pathology Slice Analysis

Professional Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Follow https://skillhub.cn/install/skillhub.md to install @user_ef14ddb2/analysis-pathology-slice into your AI assistant.

About this skill

Problem

Pathology slide AI diagnosis often gets stuck in fragmented steps: uploading WSI files to COS, creating file-record callbacks, creating WSI records, then polling diagnosis status. Manually chaining these calls risks missing parameters, malformed COS paths, or unclear recovery after a 401 token error.

How It Works

The skill runs a fixed six-step flow and prints machine-readable status lines such as STEP_STATUS|step=....
- Authentication: reads PATHOLOGY_USERNAME and PATHOLOGY_PASSWORD; if a valid token already exists, it prints skipped.
- Upload and records: fetches temporary COS credentials, uploads WSI files under SLIDES/chunked_uploads/{YYYYMMDD}/{organization}/{file MD5}/{filename}{extension}, then creates the file-record callback and WSI record.
- Diagnosis lookup: waits 30 seconds by default, queries the diagnosis status for the returned slide_id, and outputs modified_ai_diagnosis_result_map.value.

Boundaries

It targets an internal environment with an existing account, COS permissions, and pathology AI service access. Users must select a diagnosis type: 6 for general tissue slices or 14 for digestive biopsy AI. Any 401 response should trigger re-login, and statuses other than 4 should be retried after the suggested delay.

Use Cases

  • Upload WSI slides to COS and create the file-record callback without manual path assembly.
  • Fetch temporary COS credentials after login, then upload the slide and create a WSI record.
  • Select general tissue slice or digestive biopsy, poll AI status, and extract the result value.
  • Re-login on any 401 to refresh the token, then continue querying the WSI diagnosis result.

Best For

  • Backend engineer integrating pathology platform APIs, needing a stable login, upload, record, and query flow.
  • Lab information manager for WSI ingestion, wanting fewer manual COS path and callback field errors.
  • Clinical engineer deploying digestive biopsy AI, needing status-based retry and diagnosis result extraction.
  • Platform engineer maintaining medical automation scripts, handling 401 refresh and machine-readable status.