inclusive-names

Generate diverse human names with configurable counts, regional constraints, and edge-case forms.

5|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/hereinthehive/gotrino-inclusion --skill inclusive-names
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inclusive-names
Source: https://github.com/hereinthehive/gotrino-inclusion/tree/main/skills/inclusive-names
Command: npx skills add https://github.com/hereinthehive/gotrino-inclusion --skill inclusive-names

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Homogeneous or region-locked test data leads to biased tests and missed bugs. This skill generates culturally diverse names for use in examples, mock data, and test fixtures, including edge-case forms that reveal encoding or parsing issues.

Core Features & Use Cases

  • Diversity-focused name generation across regions, languages, and gender presentations.
  • Edge-case coverage including apostrophes, diacritics, long names, non-Latin scripts, and hyphenations.
  • Use Case: supply ready-to-use name lists for fixtures, documentation samples, or UI testing.

Quick Start

Provide a diverse list of names for fixtures and examples.

Frequently Asked Questions about inclusive-names

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

FAQPage Schema
How do I generate diverse test data with international names for my mock fixtures?

To generate diverse test data, this skill produces human names spanning multiple regions, genders, and scripts. It outputs simple lists and structured objects specifically designed for mock data fixtures and UI testing.

Why does homogeneous test data cause parsing bugs and how do edge-case names help?

Homogeneous test data causes biased tests and missed bugs because it lacks encoding variations. Edge-case names containing apostrophes, diacritics, hyphenations, and non-Latin scripts stress-test systems to reveal these hidden parsing issues.

Can I configure regional constraints and specific counts when generating mock names?

Yes, you can configure specific counts and regional constraints when generating mock names. The skill supports configurable parameters to target specific regions and produce the exact volume of diverse name lists required.

What's the best way to include diacritics and non-Latin scripts in test fixtures?

The best way to include diacritics and non-Latin scripts in test fixtures is using a diversity-focused name generator. This skill automatically incorporates edge-case forms like hyphenations and long names into ready-to-use structured outputs.

Does this name generation approach output structured objects or only simple lists?

This name generation approach outputs both simple lists and structured objects. You can use these formats directly in test fixtures, documentation samples, or UI testing environments depending on your system requirements.