# Find and Retrieve Japanese Government Statistics

Japanese statistical tables use table identifiers and dimension codes that can be difficult to navigate. This skill guides table search, metadata inspection, and filtered retrieval through the official e-Stat API.

## Install

```bash
npx skillstore add tahodev/estat-stats
```

## Metadata

- Status: approved
- Slug: tahodev-estat-stats
- Skillstore revision: r1
- Version status: missing
- Tree hash: a60891bfaf7702e262af1e56b17cdefb25806c901399627652ae73b23a4ab04f
- Author: tahodev
- GitHub username: tahodev
- License: MIT
- Repository: https://github.com/tahodev/kurashi-skill/tree/09cb7f9eac85f0c85633cce08328a1a57854a94f/estat-stats
- 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: 74
- Public page: https://skillstore.pages.dev/skills/tahodev-estat-stats
- Manifest: https://skillstore.pages.dev/api/skills/tahodev-estat-stats/manifest

## Capabilities

- Guides keyword searches with getStatsList and identifies table IDs, titles, survey names, and responsible agencies.
- Explains getMetaInfo responses to identify dimensions and map classification codes to labels.
- Provides getStatsData examples with metadata-derived filters for population totals.
- Describes paginated retrieval using limit, startPosition, and response counters.
- Distinguishes authentication errors, parameter errors, empty results, timeouts, and service failures.
- Explains appId setup, environment-variable storage, source attribution, bounded retries, and request pacing.

## Use Cases

- Locate Population Tables: Find relevant population tables and inspect their dimensions before retrieving research data.
- Check Official Economic Sources: Search for GDP or CPI tables and identify official sources for a report.
- Retrieve Filtered Statistical Values: Use metadata-derived codes and pagination to collect public statistics for a data workflow.

## Prompt Templates

### Find a Statistical Table

```
Find up to five e-Stat population tables. Show their IDs, titles, and responsible agencies. Use my configured appId without displaying it.
```

### Inspect Table Dimensions

```
Inspect metadata for e-Stat table [table ID]. Explain its dimensions and available region, time, and category codes before requesting values.
```

### Retrieve Filtered Values

```
Retrieve [measure] from table [table ID] for [region] and [period]. Verify filter codes using metadata. Report labels, units, and source attribution.
```

### Retrieve Multiple Pages Reliably

```
Retrieve all matching values from [table ID] using [filters]. Paginate with response counters, pace requests, check application status, and report incomplete retrieval.
```

## Limitations

- Live retrieval requires an e-Stat appId, network access, and an assistant with shell or HTTP tools.
- The package contains instructions and curl examples, not a standalone client, analysis engine, or visualization tool.
- Example table IDs and classification codes require verification against current metadata; statistical coverage depends on e-Stat.
- The linked shared response checklist is not included in the package.

## Best Practices

- Keep the appId out of chat, commits, process arguments, and logs; use a credential-safe request method.
- Inspect metadata before choosing filters, map codes to labels, and include official source attribution.
- Check application status, apply timeouts, pace paginated requests, reuse results, and limit retries.

## Anti Patterns

- Assuming HTTP 200 means the statistical request succeeded.
- Reusing classification codes across tables without checking metadata.
- Treating one limited response page as a complete dataset.

## Security Audit

- Audited at: 2026-10-13T03:35:03.602\+00:00
- Summary: All 30 static findings are false positives involving Markdown formatting, official e-Stat URLs, a documentation link, and readable Japanese text. No evidence found of prompt injection, malicious execution, or unauthorized data exfiltration. One separate concern remains: expanded API keys enter curl process arguments and may be visible to local process inspection or monitoring.

## Stats

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