# Check Japan's Active Typhoon Information

Missing typhoon information and failed retrievals can look similar. This skill checks the public JMA feed, explains response status, and includes verification times and official safety references.

## Install

```bash
npx skillstore add tahodev/bosai-typhoon
```

## Metadata

- Status: approved
- Slug: tahodev-bosai-typhoon
- Skillstore revision: r1
- Version status: missing
- Tree hash: 2e7787b4b10c6f0ded528bc4500c944e0da07e4c85485792e4fa1dbb7c83810f
- Author: tahodev
- GitHub username: tahodev
- License: MIT
- Repository: https://github.com/tahodev/kurashi-skill/tree/09cb7f9eac85f0c85633cce08328a1a57854a94f/bosai-typhoon
- Ref: 7f17813fb6af1acc7d8fd3fb5f05480f5be52783
- 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-bosai-typhoon
- Manifest: https://skillstore.pages.dev/api/skills/tahodev-bosai-typhoon/manifest

## Capabilities

- Retrieve the public JMA typhoon list without an API key or login.
- Read an HTTP 200 array response and report the available typhoon information.
- Treat HTTP 404 as no active typhoon information, following the documented September 11, 2026 observation.
- Distinguish retrieval failures from reported absence and retry failures once or twice.
- Include the check time and refer users to JMA and municipal announcements for safety decisions.

## Use Cases

- Check Before Household Preparations: Check whether the JMA feed reports typhoon information, then consult official announcements before making household safety decisions.
- Verify Information Before Travel: Request a timestamped typhoon information check and an official JMA reference before reviewing travel plans.
- Prepare a Status Brief: Summarize the feed status while clearly separating unavailable data from reported absence.

## Prompt Templates

### Check Current Information

```
Check whether JMA currently reports active typhoon information. Include the check time and a link to official announcements.
```

### Report Available Typhoon Data

```
Retrieve the JMA typhoon list and summarize only fields present in the response. Do not invent storm numbers, tracks, or local impacts.
```

### Explain a Failed Check

```
Check the JMA typhoon feed. Retry retrieval failures once or twice, then report the failure clearly without claiming that no typhoon exists.
```

### Draft an Operations Brief

```
Prepare a timestamped JMA typhoon status brief. Separate observed data from unknown details and cite official announcements for safety decisions.
```

## Limitations

- Active-typhoon fields, detailed payload structure, and tropical depression coverage were not verified when the skill was recorded.
- The HTTP 404 absence interpretation rests on a September 11, 2026 observation, not a documented availability guarantee.
- The skill requires network access and curl execution capability; earthquake alerts, forecasts, and rain radar are outside its scope.
- The referenced shared response checklist is not included in the reviewed single-file package.

## Best Practices

- Include the check time in every status report.
- Keep HTTP status, retrieval failures, and reported absence distinct.
- Consult JMA and municipal announcements before making evacuation or other safety decisions.

## Anti Patterns

- Reporting no typhoon after a timeout or server failure.
- Inventing typhoon numbers, tracks, field meanings, or local impacts.
- Using this feed check as the sole basis for a safety decision.

## Security Audit

- Audited at: 2026-10-13T03:19:24.64\+00:00
- Summary: All six static findings are false positives in the reviewed SKILL.md. They concern Markdown fences, public JMA URLs, a documentation link, and readable Japanese text, not dangerous execution or obfuscation. No evidence found of prompt injection, credential access, data exfiltration, or destructive filesystem operations.

## Stats

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