スキル nex-einvoice-pl
📦
nex-einvoice-pl
v1.0 コンテンツリビジョン r1 安全 🌐 ネットワークアクセス
Plan Polish KSeF E-Invoice Integrations
Polish KSeF integration requires coordinated invoice mapping, authentication, and contingency planning. This written guide frames those tasks around FA(3), KSeF onboarding, and offline24 considerations.
対応: Claude Codex Code(CC)
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
エージェントリクエスト
Review the Skillstore skill "nex-einvoice-pl" from https://skillstore.io/skills/nexaiguy-nex-einvoice-pl.md and its manifest at https://skillstore.io/api/skills/nexaiguy-nex-einvoice-pl/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「nex-einvoice-pl」を使用しています。 What should we collect before mapping ERP invoices to FA(3)?
期待される結果:
- Identify the invoice types: standard, correction, or advance.
- Inventory source fields using anonymized invoice examples.
- Obtain the official FA(3) schema before accepting field mappings.
- Record unresolved correction-reference and attachment requirements.
「nex-einvoice-pl」を使用しています。 Can this package implement our offline24 workflow?
期待される結果:
- The package provides written guidance, not an executable offline24 implementation.
- Review certificate access, QR code requirements, submission windows, and recovery handling.
- Confirm technical rules against current official documentation before implementation.
- Plan separate implementation and testing for the missing integration components.
「nex-einvoice-pl」を使用しています。 How should we review a correction-invoice mapping?
期待される結果:
- The guide includes a correction example referencing the original invoice.
- Treat its field names and values as proposals requiring official schema verification.
- Validate the resulting document before using it in a production workflow.
セキュリティ監査
安全v1 • 2026/11/2 バージョン別レポートを開く
All three static findings are false positives: the URLs are attribution links, and the footer contains no reconnaissance instructions. No evidence found of credential collection, data exfiltration, executable commands, or prompt injection in the reviewed SKILL.md. The package contains a written guide rather than executable integration tooling.
1
スキャンされたファイル
86
解析済み行数
0
レビュー項目
0
誤検知を無視
リスク要因
🌐 ネットワークアクセス (2)
最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。
監査者: codex
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/nexaiguy-nex-einvoice-pl/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/nexaiguy-nex-einvoice-pl?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/nexaiguy-nex-einvoice-pl?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/nexaiguy-nex-einvoice-pl/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/nexaiguy-nex-einvoice-pl.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
nexaiguy. (2026). nex-einvoice-pl security audit report (audit version 1) [Author version 1.0]. Skillstore. https://skillstore.io/skills/nexaiguy-nex-einvoice-pl/audits/1BibTeX形式の引用
@techreport{nexaiguy-nexaiguy-nex-einvoice-pl-2026,
author = {nexaiguy},
title = {nex-einvoice-pl security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/nexaiguy-nex-einvoice-pl/audits/1},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nex-einvoice-pl security audit report (audit version 1)"
version: "1.0"
type: report
authors:
- name: "nexaiguy"
date-released: "2026-11-02"
url: "https://skillstore.io/skills/nexaiguy-nex-einvoice-pl/audits/1"
identifiers:
- type: other
value: "skillstore:nexaiguy-nex-einvoice-pl:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中 55
アーキテクチャ
85
保守性
87
コンテンツ
65
コミュニティ
83
仕様準拠
作成できるもの
Scope an ERP Mapping Project
Identify invoice types, source fields, and unresolved FA(3) mapping questions before implementation.
Prepare an Onboarding Review
Organize environment, authentication, and certificate questions for a KSeF integration review.
Review Contingency Requirements
List offline24 operational questions, attachment constraints, and official documentation needed for a finance workflow review.
これらのプロンプトを試す
Understand the Integration Scope
Summarize the KSeF integration topics in this guide. Separate documented guidance from details requiring official verification.
Plan Invoice Field Mapping
Review these anonymized ERP fields: [fields]. Draft FA(3) mapping questions for [invoice type]. Mark unknown mappings and request the official schema.
Outline API Onboarding
Draft an onboarding checklist for [environment] using the guide. Identify authentication decisions, certificate dependencies, and missing documentation. Do not request credentials.
Review an Offline24 Design
Review this offline24 design: [design]. Flag certificate, QR code, submission, and recovery questions. Verify requirements against [official documentation] and label unsupported assumptions.
ベストプラクティス
- Verify all field values, legal dates, and certificate requirements against current official KSeF documentation.
- Use anonymized invoice samples and keep private keys, tokens, and certificates outside prompts.
- Validate mappings and recovery behavior in an appropriate test environment before production use.
回避
- Treating the brief guide as a complete, validated KSeF implementation.
- Copying example field values into production without checking the official FA(3) schema.
- Assuming scripts, templates, update notifications, or production access are included in this folder.
よくある質問
What does this skill include?
It includes one written guide covering KSeF integration topics and one correction-invoice example. Scripts, extension source, and templates are absent.
Does it generate validated FA(3) invoices?
No validator or schema file is included. Any proposed mapping or XML output requires verification against the official FA(3) schema.
Can it connect directly to KSeF?
No API client or connection tooling is included. The guide identifies onboarding and authentication topics for implementation planning.
Does it implement offline24 QR codes?
It highlights offline24 certificate and QR code considerations, but includes no QR generator or executable contingency workflow.
Which assistants can use this guide?
Claude, Codex, and Claude Code can use the text as context. Actual implementation depends on the assistant environment and supplied documentation.
Are its deadlines and compliance statements authoritative?
No. Verify legal requirements, dates, and technical details with current official sources and qualified advisers before relying on them.