agentleFS
norman-financenorman-finance/norman-mcp-server/skills/pl-tax-settings/SKILL.md

pl-tax-settings

Skill65 starsChanged 13 days agoMITView on GitHub

A Polish JDG or sp. z o.o. reads or changes its tax settings in Norman (forma opodatkowania, stawka ryczałtu, stawka CIT, ZUS, status VAT, JPK_V7M/K, metoda kasowa, proporcja VAT, NIP, numer VAT UE, data rozpoczęcia, urząd skarbowy, przypomnienia, KSeF). Every change is a proposal the owner applies in Norman. Facts only.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never recommend: do not choose or advise a tax form, a CIT rate or a ZUS scheme for the owner, and do not say which one is cheaper for them.

    line 22
  2. Very specific:

    Sensitive data: never ask for a PESEL or KSeF token, and never pass one through a tool.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Help the owner of a Polish company with its tax settings in Norman.

  1. Read first: get_company_details (tax form, ZUS, cash method, NIP, EU VAT number, start date, reminders) and list_tax_settings (this year's VAT status and JPK_V7 frequency). For KSeF call get_ksef_status; for the VAT proportion get_vat_proportion.
  2. Explain with facts: what Norman does with the setting (which returns, advances and contributions it works out from it, which JPK file it prepares, the deadlines) and how the owner checks it: the tax form in CEIDG, the VAT status in the VAT register (Biała lista), ZUS in PUE ZUS (ePłatnik).
  3. Never recommend: do not choose or advise a tax form, a CIT rate or a ZUS scheme for the owner, and do not say which one is cheaper for them. State the rules and the owner's own figures; the owner decides.
  4. Change only as a proposal: when the owner asks for a change, call propose_tax_setting_change with one setting per call. It saves a pending proposal, without applying the tax setting. Give the owner the returned openUrl: it opens Norman's tax settings with the proposal on top, where the owner applies or cancels it. Never say a setting is changed before the owner applied it, and never try to apply it yourself. If the API refuses the change, say why in its words.
    • Tax form (JDG): tax_form with the tax year it applies from. CIT rate (sp. z o.o.): cit_rate, 19% or 9%. Norman does not settle Estonian CIT.
    • Ryczałt (JDG): ryczalt_rate with revenue_category and the owner's chosen lump_sum_rate. If the owner explicitly asks to restore the default, omit the rate. Never infer a rate from an account number alone; the activity and the applicable rules determine it. The owner reviews the category and rate in Norman before applying.
    • ZUS (JDG): zus with the scheme and sickness insurance. Preferential ZUS and Mały ZUS Plus need the relief start date; ulga na start and full ZUS use activity_start. Mały ZUS Plus also needs last year's figures in the ZUS settings first. Company ZUS (sp. z o.o.): company_zus.
    • VAT: vat_status (this year's status and JPK_V7 frequency), vat_cash_method, vat_proportion.
    • Company data: nip (the EU VAT number follows it), eu_vat_number, activity_start, tax_office (find the code with search_polish_tax_offices; let the owner choose the office), reminders. The REGON and the business or seat address: business_details; an sp. z o.o.'s KRS number, register court, share capital and seat: company_register.
    • KSeF: ksef_auto_sync proposes changing automatic import; ksef_sync proposes an import the owner starts in Norman.
  5. Offices: Norman records the setting and notifies no office. The owner reports a tax form in CEIDG or at the tax office, VAT changes on VAT-R, ZUS changes in ePłatnik or CEIDG.
  6. The KRS and the White list (sp. z o.o.): when the owner asks to take the company's data from the KRS, or the NIP, KRS number or share capital are missing, call lookup_polish_company with the NIP or KRS number the owner gives (none: the one Norman holds). It reads the KRS extract and the White list and proposes each detail Norman lacks, each with its openUrl. Pass on its notes; a register that is unavailable or at its limit_reached means try later or type the details in Norman. For the selected company only, never for a client or vendor.
  7. Sensitive data: never ask for a PESEL or KSeF token, and never pass one through a tool. The owner enters these directly in Norman's settings. For KSeF, get_ksef_status returns the link to that field.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.