Real Skill packageSource verifiedClawHub registry

jp-pint-invoice-validation

Validate Japanese Peppol e-invoices (JP PINT 1.1.3 UBL Invoice XML) with JPVerify against the official OASIS UBL 2.1 XSD and OpenPeppol JP PINT Schematron, optionally checking the seller's qualified-invoice T-number in the National Tax Agency registry. Use when a task involves checking a JP PINT / Peppol (デジタルインボイス) XML invoice before sending it, accepting it into accounting, or paying it. Paid per call (API key credits or x402).

Identity and source

Publisher attributionJPVerifyregistry owner unverified by skillvetai
Functional categoryEnterprise Functionsautomatically inferred · 60% rule confidence
Package forminstruction bundle4 recorded files
Canonical sourceClawHub registryclawhub:japanverify:jp-pint-invoice-validation
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-pint-invoice-validation

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-pint-invoice-validation

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-pint-invoice-validation

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-pint-invoice-validation
clawhub inspect @japanverify/jp-pint-invoice-validation --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
5 inferred permission indicators
  • network access — automatically inferred
  • filesystem read — 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: suspicious

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:58:20 AM
Release binding
Matches this record
  • skillspector: suspicious
  • llm: suspicious

Recorded files

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

Package content hashsha256:1da82b97e83373d862cb03a75022e744457c6d264790358d40aa50e9f22279d6
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:170e63101d5de0ede1d9324afbc94a1342f9f2e818bfab5ce9c699836bc954a6
1.0.711/8/2026sha256:bf3ebf0feea19473778726d8ca39c2926494e260f74c342fe480c834aaba125a