brreg

aradotso/trending-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/aradotso/trending-skills --skill brreg
0 commentsdiscussion
summary

Skill by ara.so — Daily 2026 Skills collection

skill.md

Norwegian Business Registry (Brreg)

Skill by ara.so — Daily 2026 Skills collection

Access the official open API from Brønnøysundregistrene to search and retrieve data about all registered companies in Norway.

When to Use

  • When the user asks about Norwegian companies
  • When searching for company information in Norway
  • When looking up organization numbers (organisasjonsnummer)
  • When finding companies by name, location, industry, or other criteria
  • When checking company status (bankruptcy, dissolution, etc.)

API Base URL

https://data.brreg.no/enhetsregisteret/api

Key Endpoints

Search Companies (Enheter)

curl "https://data.brreg.no/enhetsregisteret/api/enheter?navn=SEARCH_TERM&size=20"

Common parameters:

Parameter Description
navn Company name (partial match)
organisasjonsnummer 9-digit org number (comma-separated for multiple)
organisasjonsform Organization type: AS, ENK, NUF, ANS, DA, etc.
naeringskode Industry code (NACE)
kommunenummer 4-digit municipality code
postadresse.postnummer Postal code
forretningsadresse.postnummer Business address postal code
konkurs true/false - bankruptcy status
underAvvikling true/false - dissolution status
registrertIMvaregisteret true/false - VAT registered
fraAntallAnsatte Minimum employees
tilAntallAnsatte Maximum employees
fraRegistreringsdatoEnhetsregisteret Registration date from (YYYY-MM-DD)
tilRegistreringsdatoEnhetsregisteret Registration date to (YYYY-MM-DD)
size Results per page (default: 20, max depth: 10000)
page Page number (0-indexed)

Get Company by Org Number

curl "https://data.brreg.no/enhetsregisteret/api/enheter/123456789"

Search Sub-entities (Underenheter)

Branch offices and departments:

curl "https://data.brreg.no/enhetsregisteret/api/underenheter?overordnetEnhet=123456789"

Get Organization Forms

List all valid organization types:

curl "https://data.brreg.no/enhetsregisteret/api/organisasjonsformer"

Common organization forms:

Code Description
AS Aksjeselskap (Private limited company)
ASA Allmennaksjeselskap (Public limited company)
ENK Enkeltpersonforetak (Sole proprietorship)
NUF Norskregistrert utenlandsk foretak (Foreign enterprise)
ANS Ansvarlig selskap (General partnership)
DA Selskap med delt ansvar (Shared liability partnership)
SA Samvirkeforetak (Cooperative)
STI Stiftelse (Foundation)

Get Recent Updates

Track new registrations and changes:

curl "https://data.brreg.no/enhetsregisteret/api/oppdateringer/enheter?dato=2024-01-01T00:00:00.000Z"

Bulk Downloads

Complete datasets (updated nightly ~05:00 AM):

Format URL
JSON (gzipped) https://data.brreg.no/enhetsregisteret/api/enheter/lastned
CSV https://data.brreg.no/enhetsregisteret/api/enheter/lastned/csv
Excel https://data.brreg.no/enhetsregisteret/api/enheter/lastned/regneark

Example Queries

Find all AS companies in Oslo with 50+ employees

curl "https://data.brreg.no/enhetsregisteret/api/enheter?organisasjonsform=AS&kommunenummer=0301&fraAntallAnsatte=50&size=100"

Search for tech companies

curl "https://data.brreg.no/enhetsregisteret/api/enheter?navn=tech&size=50"

Find companies registered this year

curl "https://data.brreg.no/enhetsregisteret/api/enheter?fraRegistreringsdatoEnhetsregisteret=2024-01-01&size=100"

Get all subsidiaries of a company

curl "https://data.brreg.no/enhetsregisteret/api/underenheter?overordnetEnhet=923609016"

Response Format

Responses are in HAL+JSON format with _embedded containing results and page containing pagination info:

{
  "_embedded": {
    "enheter": [
      {
        "organisasjonsnummer": "123456789",
        "navn": "Company Name AS",
        "organisasjonsform": {
          "kode": "AS",
          "beskrivelse": "Aksjeselskap"
        },
        "antallAnsatte": 50,
        "forretningsadresse": {
          "adresse": ["Street 1"],
          "postnummer": "0150",
          "poststed": "OSLO",
          "kommune": "OSLO",
          "kommunenummer": "0301"
        },
        "naeringskode1": {
          "kode": "62.010",
          "beskrivelse": "Programmeringstjenester"
        }
      }
    ]
  },
  "page": {
    "size": 20,
    "totalElements": 150,
    "totalPages": 8,
    "number": 0
  }
}

Notes

  • API is free and open (NLOD license)
  • No authentication required for public data
  • Rate limiting may apply for heavy usage
  • Results limited to 10,000 per query (use bulk downloads for complete data)
  • Data updated continuously during business hours

Documentation

how to use brreg

How to use brreg on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add brreg
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/aradotso/trending-skills --skill brreg

The skills CLI fetches brreg from GitHub repository aradotso/trending-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/brreg

Reload or restart Cursor to activate brreg. Access the skill through slash commands (e.g., /brreg) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.555 reviews
  • Hassan Rao· Dec 20, 2024

    brreg has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Evelyn Wang· Dec 16, 2024

    Registry listing for brreg matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Kabir Kim· Dec 16, 2024

    brreg fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Isabella Chawla· Dec 12, 2024

    brreg is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Maya White· Dec 4, 2024

    Useful defaults in brreg — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Maya Jain· Nov 11, 2024

    brreg reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kabir Flores· Nov 7, 2024

    We added brreg from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Diya Flores· Nov 3, 2024

    Keeps context tight: brreg is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Yusuf Okafor· Oct 26, 2024

    brreg reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Michael Chen· Oct 22, 2024

    I recommend brreg for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 55

1 / 6