agentleFS
norman-financenorman-finance/norman-mcp-server/skills/corporate-tax-registration/SKILL.md

corporate-tax-registration

Skill65 starsChanged 14 days agoMITView on GitHub

Prepare the corporate tax registration (Fragebogen zur steuerlichen Erfassung for a GmbH/UG) through a guided chat. Use when a newly founded GmbH/UG needs its Steuernummer, the user asks what to do after the notary appointment, or wants to register the company with the Finanzamt. Final submission happens in the Norman app, not in chat. Germany only.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Who needs one: every newly founded GmbH/UG must file it with its Finanzamt to receive a Steuernummer.

    line 21
  2. Very specific:

    Call get_corporate_tax_registration.

    line 38
  3. Distinctive:

    If not found, offer to start one.

    line 40
  4. Very specific:

    If the company was founded through Norman, pass the incorporation publicId to create_corporate_tax_registration — company, notary date, …

    line 41
  5. Very specific:

    Use get_corporate_tax_registration_choices for the valid enum values.

    line 44
  6. Very specific:

    When sections.missing is empty everywhere, summarize the collected data briefly.

    line 92
  7. Very specific:

    Call get_corporate_submission_link.

    line 93

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Guide the user through the corporate Fragebogen zur steuerlichen Erfassung (tax registration of a newly founded GmbH/UG, e-filed via ELSTER as FsE KapG): collect the data across six sections, then hand over to the Norman app for the final submission.

Ground rules

  • Who needs one: every newly founded GmbH/UG must file it with its Finanzamt to receive a Steuernummer. Self-employed users (Einzelunternehmer, Freiberufler) use the regular tax-registration flow instead — do not mix the two.
  • The final submission happens in the Norman app, never in chat. The e-filing to the Finanzamt is a binding legal act: when the data is complete, call get_corporate_submission_link and hand the user the link — they review the rendered ELSTER preview in the app and press Submit themselves. There is deliberately no submit tool.
  • Never present anything as legal or tax advice. You help fill a form; the user is responsible for the content they submit.
  • The backend is the source of truth: every response carries sections (company / registration / representatives / shareholders / financials / vatAndBank, each complete + missing camelCase field names) and status (data_collection → data_complete → submitted). Navigate by sections.missing; never track progress yourself.
  • Collect conversationally — a few related fields at a time, not a wall of questions.

Before you start

  1. Call get_corporate_tax_registration. If one exists, resume from the first incomplete section; status == 'submitted' means it's already e-filed (reportUrl has the protocol). If not found, offer to start one.
  2. If the company was founded through Norman, pass the incorporation publicId to create_corporate_tax_registration — company, notary date, capital, shareholders and managing directors are prefilled; only ask for what sections.missing still lists.
  3. Use get_corporate_tax_registration_choices for the valid enum values.
  4. In the Norman app the user can also upload their founding documents (notarized Satzung, Gesellschafterliste, HR excerpt) to prefill the form with AI — mention it when they have the papers at hand but no Norman incorporation.

Section 1 — Company (update_corporate_company)

Firma exactly as notarized, legal form, Sitz, Geschäftsanschrift (+ separate management address when managementAddressSame is false), contact data, Gegenstand des Unternehmens and the responsible Finanzamt (4-digit BuFa number).

Find the Finanzamt with suggest_tax_office from the management address. If it returns several candidates, let the user choose; get_tax_offices searches by name, town or postcode.

Section 2 — Registration (update_corporate_registration_details)

Notarization date and the Handelsregister state: application filed / registered with dates, Registergericht and the bare register number ('254739 B', without the HRB prefix).

Sections 3+4 — People (set_corporate_people)

Managing directors (max 9) and shareholders (max 99, natural persons or legal entities with nominal amounts; percents must sum to 100). Both lists use replace-all semantics: send the complete list every time, or omit the parameter to leave it unchanged.

Personal tax IDs, passport numbers and other personal government identifiers must be entered in the authenticated Norman form. Never ask for them in chat, copy them from another source, or pass them to set_corporate_people. Use get_corporate_submission_link to open the form for the people sections, especially when existing people may already have identifiers stored. Tool responses omit those values; omission does not mean the stored identifiers are missing.

Section 5 — Financials (update_corporate_financials)

Stammkapital (GmbH ≥ 25.000 €, UG 1–24.999 €), start of activity, divergent fiscal year and expected profits for the founding and following year.

Section 6 — VAT & bank (update_corporate_vat_and_bank)

Revenue forecast, the § 19 UStG Kleinunternehmer decision (waiving it binds for 5 years — make sure the user understands before setting it), Soll-/Istversteuerung, whether to request a USt-IdNr, and the refund bank account.

The company is eligible when its founding-year revenue is at most 25.000 €. Since 2025 the founding-year revenue counts as it is; do not extrapolate it to twelve months.

Finish (get_corporate_submission_link)

  1. When sections.missing is empty everywhere, summarize the collected data briefly.
  2. Call get_corporate_submission_link; if readyToSubmit is false, finish the listed missing fields first.
  3. Hand over the link and say explicitly: the final review and the Submit button are in the Norman app — after submitting there, the Steuernummer arrives from the Finanzamt by post, typically within 2–6 weeks.

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.