global-invoicing-research
生成全球开票系统的国家调研报告,输出结构化的 .docx 文档,同时服务产品经理、研发、售前三类角色。 当用户提到以下任意场景时,务必使用本 Skill: - "调研 XX 国家的开票/发票/电子发票要求" - "我要做全球开票系统,帮我调研某个国家" - "帮我生成 XX 国家的开票调研报告" - "开票合规调研"、"e-invoicing research"、"VAT invoice research" - 用户提到 KSeF、Peppol、CFDI、NF-e、GST 等具体的国家电子发票标准 即使用户没有明确说"生成报告",只要涉及对某个国家的开票要求进行结构化调研,就应使用本 Skill。
Best use case
global-invoicing-research is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
生成全球开票系统的国家调研报告,输出结构化的 .docx 文档,同时服务产品经理、研发、售前三类角色。 当用户提到以下任意场景时,务必使用本 Skill: - "调研 XX 国家的开票/发票/电子发票要求" - "我要做全球开票系统,帮我调研某个国家" - "帮我生成 XX 国家的开票调研报告" - "开票合规调研"、"e-invoicing research"、"VAT invoice research" - 用户提到 KSeF、Peppol、CFDI、NF-e、GST 等具体的国家电子发票标准 即使用户没有明确说"生成报告",只要涉及对某个国家的开票要求进行结构化调研,就应使用本 Skill。
Teams using global-invoicing-research should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/global-invoicing-research/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How global-invoicing-research Compares
| Feature / Agent | global-invoicing-research | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
生成全球开票系统的国家调研报告,输出结构化的 .docx 文档,同时服务产品经理、研发、售前三类角色。 当用户提到以下任意场景时,务必使用本 Skill: - "调研 XX 国家的开票/发票/电子发票要求" - "我要做全球开票系统,帮我调研某个国家" - "帮我生成 XX 国家的开票调研报告" - "开票合规调研"、"e-invoicing research"、"VAT invoice research" - 用户提到 KSeF、Peppol、CFDI、NF-e、GST 等具体的国家电子发票标准 即使用户没有明确说"生成报告",只要涉及对某个国家的开票要求进行结构化调研,就应使用本 Skill。
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for ChatGPT
Find the best AI skills to adapt into ChatGPT workflows for research, writing, summarization, planning, and repeatable assistant tasks.
SKILL.md Source
# 全球开票系统 · 国家调研报告生成 Skill
## 概述
本 Skill 帮助团队为任意目标国家生成一份**三端通用的开票合规调研报告**(.docx 格式),覆盖:
- **售前 / 管理层**:市场背景、合规风险、强制时间表、违规处罚
- **产品经理**:发票类型矩阵、字段清单、业务流程、功能需求
- **研发团队**:API接口、数据格式、错误处理、本地化细节
报告所有待填项以 `【待填写】` 标注,团队对照官方文档和顾问访谈逐项填入。
---
## 使用流程
### Step 1:确认目标国家与背景
向用户确认(如对话中已有则直接提取):
1. **目标国家**:中文名 + 英文名(如:波兰 / Poland)
2. **优先角色**:是否有某个角色特别需要详细内容(默认三端均输出)
3. **已知背景**:用户是否已了解该国的电子发票系统名称(如 KSeF、SDI、Factur-X 等)及监管模式
如果用户没有提供,直接用默认配置生成通用报告即可,无需反复追问。
---
### Step 2:读取生成脚本参考
参考 `references/docx-template-structure.md` 了解文档的完整结构和各模块内容。
生成脚本时遵循 `references/docx-coding-rules.md` 中的编码规范。
---
### Step 3:生成 .docx 报告
使用 `docx` npm 包(`npm install -g docx`)编写 JavaScript 脚本生成文档。
**文档结构(固定,适用所有国家):**
```
封面页
├── 国家名、调研负责人、日期、版本号
└── 文档使用说明(三端分工说明)
结论
├── 电子发票进展总结
└── 对接建议
第一部分:市场与合规概览
├── 1.1 核心影响摘要
├── 1.2 国家税务体系概览(表格)
├── 1.3 电子发票发展阶段(时间线表格)
├── 1.4 电子发票监管模式 ← Clearance / Post Audit / Hybrid
├── 1.5 合规违规风险与处罚(表格 + 售前话术框)
└── 1.6 市场情况(竞争格局、客户画像、服务商情况)
第二部分:产品需求分析
├── 2.1 产品影响摘要
├── 2.2 发票类型矩阵(B2B/B2C/B2G 差异)
├── 2.3 发票必填字段清单(逐字段,含校验规则)
├── 2.4 核心业务流程与状态机(发票生命周期,含正向流程/逆向流程,含可修改/取消/重开矩阵)
├── 2.5 税率计算规则(税率表 + 精度要求)
├── 2.6 B2G 特殊要求
├── 2.7 发票归档与合规存储要求
├── 2.8 产品功能需求清单(含优先级 P0/P1/P2)
├── 2.9 发票编号与序列规则 ← 编号连续性、多序列、税局生成
└── 2.10 跨境交易与 VAT 规则 ← B2B/B2C/Export/Import 场景
第三部分:技术对接规范
├── 3.1 研发影响摘要
├── 3.2 发票数据格式(Schema 版本、编码、命名空间)
├── 3.3 API 接口清单(Endpoint、方法、说明)
├── 3.4 认证与数字签名(证书类型、Token 机制)
├── 3.5 错误码与异常处理(含离线降级方案)
├── 3.6 性能与限制(QPS、超时、重试)
├── 3.7 本地化技术细节(语言、日期、字符集、税号校验算法)
├── 3.8 客户接入流程(Onboarding) ← 税号验证→注册→证书→授权→沙盒→启用
└── 3.9 网络协议支持(PEPPOL / EDI)
附录
├── 附录 A:调研信息来源
├── 附录 B:待确认问题清单(含负责人 / 状态跟踪)
├── 附录 C:术语表
├── 附录 D:发票票样示例
├── 附录 E:全球国家能力矩阵
└── 附录 F:版本更新记录
```
**视觉规范:**
- 配色:蓝色主色(`#1E4D8C`)、橙色警示(`#C55A11`)、绿色提示(`#375623`)
- 每个部分开头有**"角色快速阅读"信息框**
- 表格使用交替行颜色(白色 + 浅蓝 `#E8F0FB`)
- 表头深蓝背景白字
**国家定制化要点:**
根据目标国家,替换以下内容:
- 封面国家名称
- 税务体系(VAT / GST / 消费税等)
- 电子发票系统名称(KSeF / SDI / Chorus Pro / CFDI 等)
- 税号字段名称(NIP / GSTIN / RFC / P.IVA 等)
- 货币与语言
- 时间线中的强制节点
- XML Schema 名称(FA / FatturaPA / CFDI / UBL 等)
- 术语表中的本地术语
**输出文件命名:**`{国家名}开票调研报告.docx`,保存至 `/mnt/user-data/outputs/`
---
### Step 4:输出与交付
生成完成后:
1. 调用 `present_files` 工具将文件呈现给用户
2. 简短说明三部分结构和填写方式
3. 提示用户:所有 `【待填写】` 项需结合官方文档和当地税务顾问填入
---
## 常见国家速查
调研时可参考以下国家的电子发票系统名称,在报告中替换对应术语:
| 国家 | 电子发票系统 | 税号字段 | 标准格式 | 当前阶段 |
|------|-------------|----------|----------|----------|
| 波兰 | KSeF | NIP | FA XML (FA2) | 强制推进中 |
| 意大利 | SDI / FatturaPA | P.IVA | FatturaPA XML | 已全面强制 |
| 法国 | Chorus Pro / PPF | SIREN/SIRET | Factur-X / UBL | 2026年起强制 |
| 德国 | — / ZUGFeRD | USt-IdNr | ZUGFeRD / XRechnung | B2G已强制 |
| 印度 | IRP (GSTN) | GSTIN | JSON (e-Invoice) | 按营收分批强制 |
| 墨西哥 | SAT | RFC | CFDI XML | 已全面强制 |
| 巴西 | SEFAZ | CNPJ/CPF | NF-e XML | 已全面强制(最复杂) |
| 韩国 | NTS | 事业者登录番号 | 标准세금계산서 | 已强制 |
| 马来西亚 | MyInvois (LHDN) | TIN | UBL / JSON | 2024年起分批强制 |
| 澳大利亚 | ATO / PEPPOL | ABN | UBL (PEPPOL) | 自愿,推进中 |
| 英国 | HMRC MTD | UTR/VAT No. | UBL / 自定义 | Making Tax Digital |
| 欧盟跨境 | PEPPOL 网络 | EU VAT No. | UBL / PEPPOL BIS | B2G已广泛要求 |
---
## 注意事项
- **合规时间表频繁变动**:所有强制日期必须以调研时官方公告为准,报告中的时间节点仅作占位
- **不可替代专业顾问**:报告是调研框架,具体合规解读需配合当地税务律师/会计师确认
- **数据本地化风险**:部分国家(印度、中国等)对发票数据存储有境内要求,技术方案需特别关注
- **多租户 SaaS 注意**:B2B SaaS 场景下,证书管理、数据隔离、报送主体身份需专项设计Related Skills
autoresearch-pro
Automatically improve OpenClaw skills, prompts, or articles through iterative mutation-testing loops. Inspired by Karpathy's autoresearch. Use when user says 'optimize [skill]', 'autoresearch [skill]', 'improve my skill', 'optimize this prompt', 'improve my prompt', 'polish this article', 'improve this article', or explicitly requests quality improvement for any text-based content. Supports three modes: skill (SKILL.md files), prompt (any prompt text), and article (any document).
X/Twitter Research Skill
Research trending topics, ideas, and conversations on X (Twitter) using twitterapi.io.
token-research
Comprehensive token research for EVM chains (Base, ETH, Arbitrum) and Solana. Use this skill when you want to research crypto tokens, deep-dive projects or monitor tokens.
topic-research
Run a second-hop deep research pass through the Tavily CLI after an initial scan, then normalize the result into a local `research.md` contract. Use when Codex needs cited follow-up research for a chosen topic from `news-collect`, or wants a reusable research report saved into `content-production/inbox/`.
tavily-research
Conduct comprehensive AI-powered research with citations via the Tavily CLI. Use this skill when the user wants deep research, a detailed report, a comparison, market analysis, literature review, or says "research", "investigate", "analyze in depth", "compare X vs Y", "what does the market look like for", or needs multi-source synthesis with explicit citations. Returns a structured report grounded in web sources. Takes 30-120 seconds. For quick fact-finding, use tavily-search instead.
brand-prospect-researcher
Find brands actively spending on influencer and creator campaigns. Scans trade press, Instagram, job boards, and news for active-spender signals, then outputs a scored, prioritized prospect list with contacts. Use when you need to find brands to pitch, identify active advertisers, build a prospect list, research which brands are hiring influencer marketers, or find companies launching creator campaigns. Triggers on: 'find brands to pitch,' 'prospect list,' 'who's spending on influencers,' 'brand prospects,' 'active advertisers,' 'campaign activity,' or any request to identify brands actively investing in creator/influencer marketing.
two-sample-mr-research-planner
Generates complete two-sample Mendelian randomization (MR) research designs from a user-provided research direction. Use when users want to design, plan, or build a study using two-sample MR to test causal relationships. Triggers: "design a two-sample MR study", "build a publishable MR paper", "test whether this biomarker causally affects this disease", "generate Lite/Standard/Advanced MR plans", "screen multiple exposures with MR", "bidirectional MR design", "causal inference using GWAS summary statistics", or "I want to study X and Y using MR". Always outputs four workload configurations (Lite / Standard / Advanced / Publication+) with a recommended primary plan, step-by-step workflow, figure plan, validation strategy, minimal executable version, and publication upgrade path.
network-tox-docking-research-planner
Generates complete network toxicology + molecular docking research designs from a user-provided toxicant and disease/phenotype. Always use this skill when users want to investigate how an environmental toxicant, endocrine disruptor, heavy metal, food contaminant, pharmaceutical residue, or consumer product chemical may contribute to a disease through shared molecular targets, hub genes, pathways, and docking evidence. Trigger for: "network toxicology study", "toxicology mechanism paper", "target prediction + PPI + docking", "environmental pollutant and disease mechanism", "hub genes and docking for toxicant", "Lite/Standard/Advanced toxicology plan", "CTD + SwissTargetPrediction + GeneCards + STRING", "CB-Dock2 docking study", "triclosan/BPA/cadmium/PFAS + disease". Also triggers for Chinese phrasings: "网络毒理学研究设计"、"毒物机制论文"、"靶点预测+PPI+对接"、"环境污染物与疾病机制". Trigger even for casual phrasings like "I want to study how chemical X affects disease Y" or "help me design a toxicology paper". Always output four workload configurations (Lite / Standard / Advanced / Publication+) with a recommended primary plan, step-by-step workflow, figure plan, validation strategy, minimal executable version, and publication upgrade path.
pendle-pt-research
Research Pendle PT (principal token) markets, including unlevered hold-to-par ideas, near-expiry rotations, and looped PT strategies across money markets like Morpho and Euler. Use when evaluating Pendle PT opportunities, comparing natural PT APY versus practical loopability, ranking PTs by time to par / implied APY / liquidity / underlying risk, assessing PT collateral support, or comparing manual-only loops against easier execution paths such as Contango.
autoresearch-loop
Apply Karpathy's autoresearch methodology to autonomously iterate and improve anything measurable — Claude skills, n8n workflows, system prompts, business processes, or any artifact with a clear quality metric. Inspired by github.com/karpathy/autoresearch (56k stars). The loop: propose a change → test it → measure against the target metric → keep if better, discard if not → repeat indefinitely. ALWAYS trigger this skill when the user says things like: "improve this skill automatically", "iterate on this workflow", "run autoresearch on", "autonomous improvement loop", "overnight experiments", "keep iterating until it's better", "run experiments on this", "optimize this automatically", or any request to have Claude autonomously make and test changes to something measurable. Also trigger for requests to "set up an improvement loop", "run the autoresearch method", or anything involving iterative autonomous experimentation.
authenticated-web-research
Use stronger lawful workflows for sites the user is authorized to access, including local browser login, session-aware browsing, JS-heavy pages, and post-login extraction. Do not bypass access controls.
youtube-shorts-research
Find viral YouTube Shorts channels that started recently and are doing really well. Use when Abdullah asks to find shorts niches, find channels, research YouTube Shorts, or find me channels. Runs the youtube-research.js script with criteria (≤60 days old, ≥15M total views) and returns qualifying channels with links. Uses a subagent (2.5-flash-lite) to process results.