Superhero Name Skill

Overview

Each call picks a style, then one of that style's templates, then fills the template's named placeholders with random words. Every placeholder is replaced by a random entry from the style's word list for that placeholder type. If the style has no words for a placeholder, the shared common word list is used instead. Templates and word lists are loaded from a data file and cached in memory.

`style` is lowercased before use and must be one of dark, cosmic, elemental, tech, heroic or mystic; other values are rejected by validation. With no `style`, one is drawn at random from the available styles.

`name` is the finished name. `style` in the response is the style you requested, or the literal string `random` when you sent none, even though a specific style was used internally to build the name. If you need to know which style produced a name, pass the style explicitly.

Names are not checked for uniqueness or against existing characters and trademarks, and the same name can come back on separate calls, more often within a single style. If you need distinct names across calls, keep a record of the ones you have already issued and request again on a repeat. Both fields are returned on every plan.

Live Test Superhero Name Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as SuperheroNameSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call

{
  "name": "SuperheroNameSkill",
  "arguments": {}
}

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

Argument	Type	Description
`style`Optional	string	Name style `darkcosmicelementaltechheroicmystic`

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "name": "Lord Stalker",
    "style": "dark"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`name`	string	`Lord Stalker`	Generated superhero name
`style`	string	`dark`	Style used for name generation

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

A call costs 1 credit each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Game Development: Generate hero names for RPGs and superhero games
Creative Writing: Find names for comic book or novel characters
Team Building: Create fun superhero personas for team activities
Entertainment: Generate amusing hero names for party games

Other ways to use Superhero Name Skill

Set up Superhero Name Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →