altinn-terminologisjekker

Scan Altinn documentation repos for inconsistent terminology and generate recommendations files.

15|57|Updated Sep 27, 2018
One-click install
npx skills add https://github.com/Altinn/altinn-studio-docs --skill altinn-terminologisjekker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: altinn-terminologisjekker
Source: https://github.com/Altinn/altinn-studio-docs/tree/main/.claude/skills/altinn-terminologisjekker
Command: npx skills add https://github.com/Altinn/altinn-studio-docs --skill altinn-terminologisjekker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill scans Altinn documentation across repositories to identify inconsistent terminology and establish a unified terminology baseline.

Core Features & Use Cases

  • Scan multiple Altinn repos for terms used differently across products or within a product.
  • Create a temporary working file terminologi-arbeidsfil.md with a term table (Begrep, Repositorium, Kilde).
  • Generate a final recommendations file terminologianbefalinger.md detailing term variances, file references, and manual check URLs (Begrepskatalogen).

Quick Start

Clone the Altinn doc repos, scan for terminology use, and generate terminologi-arbeidsfil.md and terminologianbefalinger.md with sources and check URLs.

Frequently Asked Questions about altinn-terminologisjekker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify terminology inconsistencies across multiple documentation repositories?

You can identify terminology inconsistencies by scanning multiple Altinn repositories for terms used differently across products, collecting variances, and generating structured guidance artifacts with precise sources and line references.

What is the best way to standardize terminology across Altinn documentation?

Standardizing terminology across Altinn documentation involves generating a final recommendations file that details term variances, file references, and manual check URLs to Begrepskatalogen for governance.

How do I generate a terminology working file with sources and line references?

Generate a terminology working file by scanning cloned Altinn doc repos to produce a term table containing the concept, repository, and source fields, serving as a temporary baseline for harmonization.

Can I scan multiple Altinn repositories for divergent term usage at once?

Yes, you can scan multiple Altinn repositories at once to collect terms with divergent usage across products and generate structured guidance artifacts to standardize terminology.

Does the terminology standardization process include manual check URLs for governance?

Yes, the terminology standardization process includes manual check URLs referencing Begrepskatalogen within the final recommendations file to support governance and consistent documentation standards.