name-generator Skill
Generate approved person names for examples, demos, quests, tests, docs, and sample data. Use when a task needs fictional person names, customer names, employee names, patient names, student names, instructor names, or other human names. Published by microsoft in Ontology-Playground.
Decision snapshot
Is this a fit?
Testing, Documentation, Data analysis, Includes SKILL.md
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
3 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is name-generator Skill?
Generate approved person names for examples, demos, quests, tests, docs, and sample data. Use when a task needs fictional person names, customer names, employee names, patient names, student names, instructor names, or other human names. Published by microsoft in Ontology-Playground. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Documentation
- Data analysis
- Testing use cases
- Documentation use cases
Declared skill metadata
- Source file: .github/skills/name-generator/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use name-generator Skill
- Use it for testing.
- Use it for documentation.
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/Ontology-Playground
- Skill file: .github/skills/name-generator/SKILL.md
What it does
Generate approved person names for examples, demos, quests, tests, docs, and sample data. Use when a task needs fictional person names, customer names, employee names, patient names, student names, instructor names, or other human names.
Skill instructions
Name Generator Skill Goal Generate person names for this repository from the approved local name fixture: text data/reference/FNF-2026-06-01-01002-0268.csv Do not invent person names. Every person name used in examples, sample data, quests, tests, demos, docs, or generated ontology content must come from the CSV FullName column. Source File CSV columns: text FirstName,LastName,FullName,FirstNameNative,LastNameNative,FullNameNative,Gender,Language Use FullName by default. Use FullNameNative only when the user explicitly asks for native-script names or locale-specific display text. Workflow 1. Decide how many names are needed Identify the role and quantity from the task, for example: - sample customers - employees or managers - patients or clinicians - students or instructors - reviewers, approvers, assignees, or contributors If the task does not specify quantity, use the minimum number needed for the example or test. 2. Read names from the CSV Use the CSV fixture as the only source. A q
Verified compatibility and discovery
Frequently asked questions
What is name-generator?
name-generator is a open-source AI agent skill with Copy skill directory. Generate approved person names for examples, demos, quests, tests, docs, and sample data.
Who is name-generator best for?
name-generator is best for reusing agent instructions, scripts, and references, testing workflows, documentation workflows, data analysis workflows.
How do I install name-generator?
Install or run name-generator using Copy skill directory. Check name-generator for the latest setup command.
Is name-generator actively maintained?
name-generator may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
