agentsclimarketplace
Sign in

Arab einvoicing tax

Skill ArabAgentSkills/Skills/skills/arab-einvoicing-tax

Use this skill when working with Arab tax, e-invoicing, e-receipt, QR, clearance, reporting, and government tax APIs including Egypt ETA, Saudi ZATCA/Fatoora, Jordan JoFotara, UAE e-invoicing, Bahrain NBR, Oman Tax Authority, and provider integrations.From its SKILL.md

Install
npx -y skills add ArabAgentSkills/Skills --skill arab-einvoicing-tax

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 1 command, including `scripts/list-vendors.mjs`.

SKILL.md

4.3 KB, 886 tokens by cl100k_base, as published. Nobody here has run it

Arab E-Invoicing and Tax

When To Use

Use this skill for tax work in Arab/MENA contexts, especially when the prompt includes: e-invoice, e-receipt, tax, ZATCA, Fatoora, ETA, JoFotara, QR.

When Not To Use

  • Do not submit live tax documents.
  • Do not provide legal advice or fabricate compliance rules.

Required Inputs

  • Country or market.
  • Target vendor, if already selected.
  • Desired workflow: vendor selection, implementation, review/debugging, launch readiness, or source research.
  • Sandbox vs production state.
  • Whether live customer, payment, tax, identity, bank, or payroll data is involved.

Common Workflows

  • Identify jurisdiction, taxpayer role, and invoice lifecycle stage.
  • Read government or official provider references first.
  • Separate sandbox, onboarding, clearance/reporting, signing, QR, and production submission.
  • Return compliance caveats and manual validation requirements.

Default Workflow

  1. Read sources.yml to see available vendors and confidence.
  2. If a vendor is named, read only vendors/<vendor-id>.md for that vendor.
  3. If choosing vendors, compare only vendors in this skill's registry: bahrain-national-bureau-for-revenue, egypt-eta-e-invoicing, egypt-eta-e-receipt, egyptian-tax-authority-einvoicing-ereceipt-sdk, jordan-jofotara, saudi-zatca-fatoora, uae-einvoicing-framework, uae-fta-e-invoicing, wafeq-zatca-api, zatca-fatoora-developer-portal.
  4. Load references/integration-checklist.md only for implementation, review, or launch-readiness work.
  5. Use scripts/list-vendors.mjs for a deterministic vendor list when needed.
  6. Answer with source-backed facts, explicit unknowns, and validation steps.

Decision Tree

  • Named vendor: read that vendor file, then answer narrowly.
  • Vendor selection: filter by country, docs access, maturity, and source quality before recommending.
  • Implementation: include auth, sandbox, webhook/callback, retries, idempotency, logging, and error handling only where source-backed.
  • Review/debugging: compare the user's plan or code against the vendor file, sources.yml, and references/integration-checklist.md.
  • Source research: update facts only when an official source, developer portal, GitHub repo, OpenAPI/Postman asset, or government source supports the claim.
  • Missing docs: say Needs vendor access or Unknown from public docs.

Response Contract

  • Start by naming the skill file and vendor/reference files used.
  • Give a short recommendation or implementation path before details.
  • Separate source-backed facts from assumptions and unknowns.
  • Include country/market fit, docs access, docs confidence, and source-quality caveats when selecting vendors.
  • Include a validation checklist with sandbox/test steps, rollback or retry notes, and manual approval gates for high-risk work.
  • Never provide live-action instructions that move money, tax documents, bank data, identity data, payroll data, or outbound messages without explicit human approval.

Files To Read

  • Routing and process: SKILL.md.
  • Vendor facts: vendors/*.md.
  • Source map: sources.yml.
  • Implementation review: references/integration-checklist.md.
  • Example response style: examples/source-backed-answer.md.

Safety Rules

  • Treat tax submissions and identity certificates as high-risk.
  • Use official sandbox/test environments before production.
  • Do not alter live invoices or tax data without explicit approval.
  • Keep certificates, private keys, and OTPs out of the repo.

Validation Checklist

  • Vendor facts map back to source_urls.
  • Unknowns are labeled instead of guessed.
  • Sandbox and production are separated.
  • Secrets are not printed or committed.
  • High-risk live actions require explicit human approval.
  • Evals in evals/prompts.yml still cover the changed workflow.

Done Criteria

  • The answer names the files read or source-backed references used.
  • The implementation plan includes tests and rollback/verification steps.
  • No unsupported regional, API, compliance, pricing, or endpoint claims are included.

What ships with it: 17 files

23.8 KB alongside SKILL.md, 1 of them executable

evals/

examples/

references/

scripts/

vendors/

Gives 0 of the 12 instructions most finance skills give in 886 tokens

Counted across 469 of the 469 authors here whose files we hold, read 2026-08-07

  • Extract date vendor amount and descriptionin 15 of 469, across 3 files
  • Scan folder for invoice filesin 14 of 469, across 2 files
  • Rename files to standard formatin 14 of 469, across 2 files
  • Show organization plan before movingin 14 of 469, across 2 files
  • Generate summary CSVin 14 of 469, across 2 files
  • Organize files by categoryin 13 of 469, across 1 file
  • Preserve original filesin 13 of 469, across 1 file
  • Flag files missing critical infoin 13 of 469, across 1 file
  • Produce the requested output filein 9 of 469, across 4 files
  • Build best, base, and worst case scenariosin 9 of 469, across 5 files
  • Implement backoff if rate limit errors occurin 8 of 469, across 3 files
  • Determine the weighted average cost of capitalin 8 of 469, across 4 files

Said here and by no other author read

  • compare only vendors in registry
  • read only matching vendor file
  • give short recommendation before details
  • separate sandbox and production environments
  • name the skill and reference files used
  • Read sources.yml to see available vendors

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.