# Find Taiwan Hospitals and Clinics

Finding reliable contact details for Taiwan medical providers can require searching multiple sources. This skill guides searches using the public NHI-contracted provider directory.

## Install

```bash
npx skillstore add tahodev/taiwan-hospital
```

## Metadata

- Status: approved
- Slug: tahodev-taiwan-hospital
- Skillstore revision: r1
- Version status: missing
- Tree hash: 497b49168d118cfac56bc2184014fe3cd0d2dbca2ba4ac5515b0b6b5b6ec716e
- Author: tahodev
- GitHub username: tahodev
- License: MIT
- Repository: https://github.com/tahodev/baodao-skill/tree/3ce4b58e4525f5a66390e1236b6d38702790225a/taiwan-hospital
- Ref: 2aab20a3878daa05021884e089a7dd7739e08581
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/tahodev-taiwan-hospital
- Manifest: https://skillstore.pages.dev/api/skills/tahodev-taiwan-hospital/manifest

## Capabilities

- Retrieve public NHI-contracted provider records without an API key or login.
- Download directory records through offset pagination with up to 1,000 records per request.
- Filter providers by name, address prefix, and provider type.
- Report provider names, addresses, telephone numbers, and directory classifications.
- Guide related service-hour and department lookups using provider identifiers and the dataset catalog.
- Explain source failures and distinguish directory records from real-time clinical information.

## Use Cases

- Find a clinic contact: Search a district or provider name and obtain directory contact details before calling.
- Prepare a provider list: Collect providers by city and type for a contact list, while preserving source addresses and directory classifications.
- Research provider coverage: Retrieve paginated public records and compare provider categories across cities without treating directory counts as real-time availability.

## Prompt Templates

### Look up one provider

```
Find the NHI directory contact details for [provider name]. Report its name, address, telephone number, and source.
```

### Filter a local directory

```
List [provider type] providers in [city or district] using NHI directory records. Include contact details and preserve original addresses.
```

### Check listed service hours

```
Find [provider name], then use its HOSP_ID to check listed Saturday service hours. Distinguish fixed hours from temporary closures.
```

### Validate a complete directory extract

```
Retrieve all NHI provider records using offset pagination. Use a private temporary directory, compare fetched counts with result.total, and summarize [city] providers by type.
```

## Limitations

- Cannot provide live queue progress, appointment booking, doctor schedules, or temporary closure updates.
- Directory updates can lag openings and closures; representative addresses may not identify every branch.
- Address filtering does not calculate distances or guarantee the nearest provider.
- Requires network access and local command execution; related datasets and query filters require verification.

## Best Practices

- Preserve full-width address characters and representative-address labels when reporting source records.
- Check pagination totals and query-filter behavior before claiming a result list is complete.
- Use a private temporary directory and confirm important visit details directly with the provider.

## Anti Patterns

- Treating directory entries or fixed service hours as proof of current availability.
- Assuming one large limit request returns the complete directory.
- Inventing provider contact details when the source request fails.

## Security Audit

- Audited at: 2026-10-13T03:18:02.188\+00:00
- Summary: Twenty alerts are false positives involving Markdown backticks, readable multilingual text, public HTTPS requests, a comment, and provider identifier matching. Five filesystem alerts reflect predictable shared temporary files that permit symlink overwrites or cache tampering when another local user can pre-create them. No evidence found of prompt injection, credential access, or data exfiltration.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0