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

gewerbe-registration

Skill65 starsChanged 12 days agoMITView on GitHub

Prepare a German trade-office registration (Gewerbeanmeldung, form GewA 1) through a guided chat. Use when the user wants to register a trade/business with the Gewerbeamt, file a Gewerbeanmeldung, or asks what to do after founding a GmbH/UG or finishing the tax registration (Fragebogen). Germany only.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 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.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call get_gewerbe_registration.

    line 35
  2. Very specific:

    If the user is founding a GmbH/UG and has an incorporation, pass its publicId to create_gewerbe_registration so company, address, activity …

    line 37
  3. Very specific:

    Use get_gewerbe_registration_choices for the valid enum values.

    line 41
  4. Very specific:

    Start of activity (activityStartDate, no more than ~14 days in the future) and whether it's a head office or a branch (establishmentType).

    line 45
  5. Very specific:

    Call generate_gewerbe_document (400 + missing if a section is incomplete).

    line 67
  6. Very specific:

    Call get_gewerbe_trade_office and tell the user which Gewerbeamt is responsible.

    line 71

≈ “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

Guide the user through preparing their Gewerbeanmeldung (German trade-office registration, official form GewA 1, § 14 GewO): collect the data across three sections and generate a pre-filled PDF they submit themselves to their local Gewerbeamt.

Ground rules

  • Who needs one: Gewerbetreibende (a trade) and GmbH/UG founders. Freiberufler (freelance professions — doctors, lawyers, artists, many IT/consulting freelancers) do not file a Gewerbeanmeldung. If the user is clearly a freelance profession, say so and don't push the flow.
  • Never present anything as legal advice. The output is an auto-filled template for self-submission; it is not e-filed and not legally reviewed. Say this when the document comes up.
  • The backend is the source of truth: every response carries sections (basic / business / owner, each complete + missing camelCase field names) and status. 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_gewerbe_registration. If one exists, resume from the first incomplete section. A non-empty documents list means it's already generated. If not found, offer to start one.
  2. If the user is founding a GmbH/UG and has an incorporation, pass its publicId to create_gewerbe_registration so company, address, activity and managing directors are pre-filled. For self-employed users the tax-registration (Fragebogen) answers are carried over automatically. Mention that personal data (name, DOB, address) is collected for the form.
  3. Use get_gewerbe_registration_choices for the valid enum values.

Section 1 — Basics (update_gewerbe_basic)

Start of activity (activityStartDate, no more than ~14 days in the future) and whether it's a head office or a branch (establishmentType).

Section 2 — Business (update_gewerbe_business)

Legal form, registered/business name, and — for legal entities (GmbH/UG/AG/…) — the commercial register number. Type of business (any of industry/trade/craft/other), the Betriebsstätte address + email, and a precise activity description (Feld 15). Offer suggest_gewerbe_activity to sharpen the wording — show the suggestion and only apply it if the user accepts. Then the conditionals: whether a licence/permit is required (+ authority and date), public-sector participation, and employees (+ full-/part-time counts).

Section 3 — Owner / representative (update_gewerbe_owner)

Personal data of the owner (sole proprietor) or the managing director (GmbH/UG): names, birth name, DOB (≥18), place/country of birth, nationality, gender. Whether the home address is the business address (ownerAddressSameAsBusiness) — if not, the residence address. Main vs secondary occupation (activityType).

Generate (generate_gewerbe_document)

  1. Summarize all collected data and get explicit confirmation.
  2. Call generate_gewerbe_document (400 + missing if a section is incomplete). Share the download link; use get_gewerbe_document_preview to show the first page.
  3. Say clearly: this is a pre-filled template for self-submission — not legal advice. The PDF has a blank signature line to sign on paper (or sign it in the Norman product).
  4. Call get_gewerbe_trade_office and tell the user which Gewerbeamt is responsible; if it returns {"office": null}, tell them to search for "<their city> Gewerbeamt". Remind them they'll need their ID and any required permits to submit.

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.