Real Skill packageSource verifiedClawHub registry

jp-company-verify

Verify Japanese companies against official registries with JPVerify: identify a Japanese company from an English or romanized name, postal code, T-number, LEI or securities code with English output; corporate number (法人番号) lookup by number or company name, active/closed status, registered address, a company pre-check report with risk flags, company profile (capital, employees, website), listing, EDINET filings, Financial Services Agency licences and former names. Use when a task involves confirming that a Japanese…

Identity and source

Publisher attributionJPVerifyregistry owner unverified by skillvetai
Functional categoryBrowser Automation & RPAautomatically inferred · 57% rule confidence
Package forminstruction bundle4 recorded files
Canonical sourceClawHub registryclawhub:japanverify:jp-company-verify
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 11/10/2026.claude/skills/jp-company-verify

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 11/10/2026.agents/skills/jp-company-verify

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 11/10/2026skills/jp-company-verify

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.

clawhub install @japanverify/jp-company-verify
clawhub inspect @japanverify/jp-company-verify --version 1.3.0

Security evidence

SkillVetAI static result: no findings detected

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
4 / 4 inspected as text
Checked
11/10/2026, 7:16:58 AM
Scanner
0.1.3
Policy
1.0.3
4 inferred permission indicators
  • network access — automatically inferred
  • filesystem write — automatically inferred
  • credential access — automatically inferred
  • external write action — automatically inferred
3 dependency and API indicators
  • api: api.jpverify.com
  • api: clawhub.ai
  • api: www.jpverify.com
External clawhub result: clean

This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.

Evidence checked
11/10/2026, 4:57:48 AM
Release binding
Matches this record
  • skillspector: suspicious
  • llm: clean

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:2f3b7fa8bf563fe8cc54175c147c29236efa547230eeecd5ee8cc159bfc11c51
Show up to 4 recorded paths
  • references/endpoints.md
  • references/examples.md
  • skill-card.md
  • SKILL.md

Source changelog

1.3.0: business-specific postal codes and parcel (番地) addresses; brand names (au, MOS Burger) find the owning company as candidates; ranking signals wikidata_sitelinks and company_size; company report profile falls back to a dated gBizINFO snapshot. No field removed, prices unchanged.

Release security diff

mediumCompared fixed releases 1.0.9 and 1.3.0; 0 finding and 0 permission indicators were added.

Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.

Change reasons and limitations
  • content hash changed

Observed release history

These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.

1.0.911/8/2026sha256:6e66c944ea87f0a8fbf6cfa58c0f84dc10b3e389bc234dd74c68b5a9059c8fa5
1.0.711/8/2026sha256:702384864ca7187f7ca384da59c0b1dfdb939eec72b472d7eb46e8ec64d5b7e8