本文へ移動
cccskills
無料GitHub で公開

fantasy-name-generator

Generate fantasy character names in zh-TW with original spelling and etymology, across human, elf, dwarf, orc/beastfolk, and halfling naming traditions. Use when the user needs a name for a character, NPC, party member, villain, shopkeeper, or monster, asks to think of, suggest, or rename such a character, names entities for a MUD/TRPG/game world or worldbuilding document, or writes lore, quests, presets, or seed data that require in-world personal names.

インストール方法を見る

含まれるファイル(10)

  • SKILL.md7.3 KB
  • assets/corpus/packs/fantasy-dwarf.json35.5 KB
  • assets/corpus/packs/fantasy-elf.json28.6 KB
  • assets/corpus/packs/fantasy-halfling.json34.7 KB
  • assets/corpus/packs/fantasy-human.json27.0 KB
  • assets/corpus/packs/fantasy-orc.json29.4 KB
  • assets/corpus/regions/fantasy.json3.1 KB
  • assets/corpus/THIRD_PARTY_NOTICES.md895 B
  • assets/corpus/translit/fantasy.json33.6 KB
  • scripts/namegen.py14.8 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Fantasy Name Generator

Roll character names from a curated corpus of 174 surnames and 1,100 given names across five fantasy races. Every entry ships with its original spelling, a zh-TW rendering, and an etymology note, so a chosen name can be justified rather than merely produced.

This skill is self-contained: scripts/namegen.py is pure standard-library Python and reads only assets/corpus/. Copy the whole directory anywhere and it keeps working.

Generate

python3 scripts/namegen.py --race elf --sex female -n 8

Paths are relative to this skill's directory — use the skill's absolute path when your working directory is elsewhere.

Default output gives the display name, the original spelling, which pool it came from, and the etymology of both halves:

奇幻‧精靈(fantasy-elf)
命名慣例:精靈壽命長、氏族觀念淡薄,正式場合常用「本名、家族/棲居地複合詞」…

1. 戴莉爾‧威爾德布瑞亞爾  (Daeliel Wildbriar)  〔女性〕
   名:Daeliel — 霞光+…之女 — 詞根 Dael(霞光)接陰性後綴 -iel
   姓:Wildbriar — 野薔薇

Options

FlagValuesNotes
-r, --racehuman, elf, dwarf, orc (beastfolk, half-orc), halfling (hobbit), randomDefault random. Resolved once per run, so -n 8 gives eight names for one character, not one name each from eight races. An unknown race is an error, never a silent fallback.
-s, --sexfemale, male, neutralOmit it and each name rolls its own pool — useful when the character's gender is still open.
-n, --countintegerDefault 5. Ask for more than you need; picking is the cheap part.
--seedany stringReproduces a run exactly. Use it when a name must be re-derivable later.
-f, --formatfull (default), plain, jsonplain is one display name per line; json carries every part and is what you want when feeding another script or writing data files.
--allow-duplicatesflagCollisions are re-rolled by default.
--list-packsflagPrints each pack's pool sizes, naming conventions, and style notes.

Run --list-packs first when you are unsure which race fits, or when you need the in-world naming conventions to write surrounding lore consistently.

Pick

Generating is one command; the value you add is the choice. Roll roughly three times as many candidates as you need, then narrow using what you know about the character:

Match the etymology to the character, not just the sound. The corpus annotates what each part means. A stoic frontier guard reads better as 寒水 (Coldwater, 冷冽水源的地景取姓) than as a name that merely sounds harsh. When you present a name, say why it fits — that is the part a person cannot get from the raw roller.

Honour the pack's naming conventions. They differ in kind, not just in sound, and a name that ignores them reads as a worldbuilding mistake:

  • Human — hereditary surnames; bastards take landscape surnames (Snow, Rivers, Stone) that mark them apart from trueborn siblings. If the character is a bastard, choose deliberately from those.
  • Elf — no fixed hereditary surname; the second element is a clan-or-dwelling compound that can change with relocation or a coming-of-age rite. Useful when a character's backstory involves exile or migration.
  • Dwarf — patronymic and clan name run in parallel; clan names carry forge/mining imagery passed down for craft lineage rather than blood title.
  • Orc / beastfolk — the clan name is a tribal totem or war honour that must be earned. An unproven character should carry the given name alone; drop the surname rather than award it for free.
  • Halfling — hereditary surnames reflecting family trade or an inherited physical or temperament nickname; neighbours tease each other with them.

Read the note field when it appears. Some given names carry a note that they are gender-open, or that they derive from a particular morphological pattern. That is exactly the detail that makes a name choice defensible.

Watch the rendering, not only the spelling. Only the human pack renders surnames semantically (Snow → 雪原, Coldwater → 寒水), averaging just 2 characters. The other four packs transliterate phonetically and run around 5 characters, up to 8 (Duskwalker → 杜斯克瓦爾克爾, Skullcrusher → 斯庫爾克魯斯赫爾). So an elf or orc display name is routinely twice the length of a human one. If it has to fit somewhere narrow — a UI label, a combat log line, a name field with a length cap — check the rendered length before committing, and re-roll for a shorter surname rather than truncating.

Present the shortlist with reasoning, then let the person choose. Offering a single name without alternatives wastes the corpus's breadth.

Inside the MUD project

This skill is an authoring tool: use it while writing lore, presets, quest text, or seed data. The runtime path is separate and already exists — world/rules/namegen.py rolls over world/lore/names.py, which parses the same corpus from third_party/fantasy-namegen/. Never wire game code to this skill's copy, and never edit one copy expecting the other to follow.

The project binds three playable races to packs: human → fantasy-human, elf → fantasy-elf, beastfolk → fantasy-orc. dwarf and halfling are registry-only spares with no playable race bound to them, so a name rolled from either belongs to background lore, not a player character — unless the person says otherwise.

Attribution

The corpus is CC BY 4.0 by 弄墨 Inknomu (https://inknomu.com/namegen/fantasy). Published or derived content must credit the source; see assets/corpus/THIRD_PARTY_NOTICES.md for the full notice and the upstream source list. Do not re-fetch the corpus in CI or builds — it is a deliberate one-time static vendoring.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Add SLSA build-provenance attestations to existing GitHub Actions workflows. Use when the user wants to add artifact attestations, build provenance, or SLSA attestations to Docker container image builds in GitHub Actions CI/CD pipelines.

日本語の概要は準備中です。原文の説明を表示しています。

jim60105/copilot-prompt212026年10月9日 更新

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

日本語の概要は準備中です。原文の説明を表示しています。

jim60105/copilot-prompt212026年10月9日 更新

Guideline for designing, implementing, and verifying secure APIs following OWASP API Security Top 10 (2023) best practices. Use when the user wants to: (1) review API code or design for security vulnerabilities, (2) design a secure REST, GraphQL, or gRPC API architecture, (3) implement API authentication and authorization (OAuth2, JWT, API keys, mTLS), (4) configure rate limiting, input validation, or CORS, (5) audit API endpoints for BOLA, BFLA, or mass assignment vulnerabilities, (6) create API security checklists or verification plans, (7) fix API security bugs or harden existing APIs, (8) set up API security testing (OWASP ZAP, Schemathesis, Burp Suite), or (9) handle any API security concern including SSRF prevention, resource consumption limits, business flow protection, API inventory management, and secure third-party API consumption.

日本語の概要は準備中です。原文の説明を表示しています。

jim60105/copilot-prompt212026年10月9日 更新

Write, review, and optionally test Bash and Zsh shell scripts following project coding standards. Use for ANY shell scripting task: (1) creating a new Bash or Zsh script, (2) editing, fixing, or reviewing an existing .sh, .bash, or .zsh file, (3) adding error handling, dependency checks, or cleanup traps to shell scripts, (4) implementing API integration or file processing in shell, (5) writing or fixing ShellSpec tests (spec/*_spec.sh), or (6) deciding whether a script should be written in Bash or Zsh. Defaults to Bash; Zsh-specific guidance lives in a reference file that is loaded only when writing Zsh.

日本語の概要は準備中です。原文の説明を表示しています。

jim60105/copilot-prompt212026年10月9日 更新

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

日本語の概要は準備中です。原文の説明を表示しています。

jim60105/copilot-prompt212026年10月9日 更新

Create, run, and maintain API test collections using Bruno (OpenCollection YAML format and legacy Bru format). Use when the user wants to: (1) create a Bruno API test collection from scratch or from OpenAPI/Swagger specs, (2) write API request files with tests and assertions, (3) run API tests using bru CLI, (4) generate test reports (HTML, JUnit, JSON), (5) set up CI/CD pipelines (GitHub Actions) for automated API testing, (6) debug or fix failing Bruno API tests, (7) add environment configurations for API testing, (8) chain API requests with data extraction, or (9) work with any .yml/.bru Bruno collection files. Triggers on mentions of 'Bruno', 'bru CLI', 'API testing collection', 'OpenCollection', or requests to automate API testing with file-based collections.

日本語の概要は準備中です。原文の説明を表示しています。

jim60105/copilot-prompt212026年10月9日 更新

jim60105 のスキルをすべて見る

このスキルの問題を報告する