calculators-and-forms
Skill65 starsChanged 12 days agoMITView on GitHub
Calculate public what-if estimates or find and prepare Polish forms. Use for VAT/net/gross, JDG PIT/ZUS, depreciation, employment cost, company tax/dividends, payment requests, handover protocols, annual leave requests and payment receipts. Triggers include kalkulator, oblicz, formularz, wezwanie do zapłaty, protokół przekazania, calculator, form generator.
In this repository26 other files it gives its agents.
- accounting-cutoverSkill
- categorize-transactionsSkill
- company-incorporationSkill
- corporate-tax-registrationSkill
- create-invoiceSkill
- expense-reportSkill
- financial-overviewSkill
- find-receiptsSkill
- gewerbe-registrationSkill
- manage-clientsSkill
- manage-productsSkill
- monthly-reconciliationSkill
- overdue-remindersSkill
- pl-opening-balanceSkill
- pl-tax-settingsSkill
- run-payroll-monthSkill
- run-workflowSkill
- suggest-categorySkill
- ta-client-periodSkill
- ta-company-reviewSkill
- ta-datev-preparationSkill
- ta-missing-receiptsSkill
- ta-tax-complianceSkill
- tax-deduction-finderSkill
- tax-reportSkill
- verfahrensdokumentationSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Read get_public_calculator for the chosen ID.
- Very specific: line 32
Search using Polish or English (pl, en).
≈ “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.
Files
Calculators and Polish forms
Use the existing Norman tools to complete the request. Respond in the user's language. The language does not establish tax jurisdiction. Do not ask again for facts already supplied in the conversation. If a named tool is absent from the app turn, discover its exact name with search_available_tools before calling it.
Choose the right tool family
| User intent | Flow |
| Hypothetical amount, VAT conversion, B2B/JDG PIT/ZUS, depreciation, employment cost, CIT/dividend | list_public_calculators → get_public_calculator → calculate_public_estimate |
| Actual tax due or an existing declaration for the selected company | list_tax_reports → get_tax_report, or get_polish_tax_estimates where applicable |
| Create an invoice in the account | Existing create_invoice flow, not a letter template |
| Find an official Polish form or blank document | list_polish_forms → get_polish_form |
| Prepare a payment request, handover protocol, annual leave request or payment receipt | get_polish_form → generate_polish_document |
Public calculations
- Resolve requested country, year and legal form. Use existing company context only when the request concerns that company; a hypothetical Polish scenario must not be replaced with the selected German company's jurisdiction. Never change company selection for public arithmetic.
- Read
get_public_calculatorfor the chosen ID. Follow its liveinputSchemaand description; ask one concise question for missing required or conditional inputs, including user-confirmed tax regime, VAT rate or relief eligibility. The current catalog supports 2026 only. Never substitute it for an unsupported year. - Send only schema-declared numbers, booleans and enums, with nested numeric details when required. Amounts are major currency units. Do not send names, email, NIP/PESEL, tax identifiers, account IDs, documents or the whole conversation. Do not classify a ryczałt rate or determine relief eligibility for the user.
- Execute
calculate_public_estimate. Present the returned result with country/year/currency, material assumptions and the returned source link. Do not perform a second calculation using invented formulas. The result is an estimate, not a tax report, filing, eligibility decision or payment.
Known IDs: PL pl_vat, pl_jdg_annual, pl_zus_monthly, pl_depreciation, pl_spolka_dividend, pl_sole_shareholder_zus, pl_employer_cost; DE de_vat, de_income_tax, de_self_employed, de_company_tax, de_trade_tax, de_depreciation. Fetch the catalog to confirm availability and current inputs. An sp. z o.o. is not a JDG; shareholder ZUS is not company employer DRA. Annualized JDG illustrations are not monthly filing schedules.
Forms and documents
- Search using Polish or English (
pl,en). If a narrow query gives no results, broaden it or inspect a known form ID; do not conclude the feature is absent from one empty search. payment-request: wezwanie do zapłaty, payment request, demand letter.handover-protocol: protokół przekazania, handover protocol.annual-leave-request: wniosek o urlop wypoczynkowy, annual leave request.payment-receipt: pokwitowanie odbioru zapłaty, acknowledgment of payment received. Confirm actual receipt and allocation of funds, including remaining amounts, before preparing a receipt. Leave preparation neither approves an absence nor calculates entitlement. Get the current version and required fields. Ask only for missing facts; never invent parties, dates, amounts or interest.- Prepare only on the user's request using
generate_polish_documentwith that version and exact field keys. PDF is the default unless DOCX is requested. The file is Polish regardless of the chat language. Show the real preview/download returned by the tool. Say that the user reviews and signs; the bearer link expires after 10 minutes and anyone holding it can download it. - Any entry with
kind=official, including PIT, VAT, ZUS, NIP-8, ORD-IN and authorizations, is an official-source reference only. Provide the current authority link and instructions; do not claim to fill, sign, send or file these forms. For the company's prepared ZUS DRA, use its report flow instead of the blank-form entry.
Preparation never sends a reminder, signs a document, files a declaration or pays money. A request to send an account invoice reminder belongs to the separate reminder tool and its own authorization, not this generator. Calculator and form requests do not authorize other account mutations.
If any service returns an error or 404, report the specific unavailable operation. Never fabricate a successful calculation, document or download URL. Refresh the schema after a version conflict; regenerate an expired document only if the user still wants it. A source-code registration alone is not evidence that a service is deployed.
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
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.

