AI Agent Hub
Back to skills
PathClaw Pathology Assistant icon

PathClaw Pathology Assistant

Professional Updated 2026.08.30

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

Please follow https://skillhub.cn/install/skillhub.md and install @user_ef14ddb2/pathclaw into your AI assistant.

About this skill

Problem

In pathology slide workflows, an agent often needs to map colloquial anatomical terms to the service-side alg_id, then securely upload .svs files, poll task status, and explain results. If name normalization, API parameters, and error handling are left ad hoc, the agent may choose the wrong tissue type, expose tokens, or treat 4xx errors as retriable.

How the skill works

  • Name confirmation: Before login, upload, or diagnosis, it requires the user to select a canonical name; it normalizes short terms like “lung” or “breast,” and pauses when terms such as “cervix” or “thyroid” are ambiguous.
  • alg_id mapping: It selects the internal integer alg_id from the supported names and submits it with the .svs file to /api/v1/diagnosis/run, without exposing it to the user.
  • Task submission and polling: It validates that the file exists, is readable, is non-empty, and uses the .svs extension; then it logs in, uploads the slide, records slide_id, and interprets data.status for queued, running, successful, or failed states.
  • Safety and error boundaries: Full tokens, Authorization headers, and raw login responses are not displayed by default; 401/403 terminate, 4xx parameter errors terminate, and 5xx retries are limited to two attempts.

Boundaries

The skill targets the .svs pathology diagnosis API and does not replace physician interpretation. It does not support tissue or cytology names outside the provided list, and continued querying requires an existing slide_id in context.

Use Cases

  • A path engineer receives a .svs slide called “lung,” normalizes it to lung tissue, and submits it to PathClaw.
  • A service integrator uploads .svs slides to PathClaw and polls data.status until the result succeeds or fails.
  • A clinical information specialist rechecks a pending slide by slide_id and explains the current analysis status.
  • An app developer validates that a .svs file is readable, non-empty, and correctly named before calling the API.

Best For

  • Pathology engineers who need to map slide names to alg_id and submit PathClaw analyses.
  • Backend engineers integrating .svs upload, status polling, and error handling into diagnosis workflows.
  • Clinical information specialists who need to retrieve pending pathology results by slide_id.
  • Application owners who need name confirmation, secure token output, and retry rules for pathology agents.