Variable Name Converter Skill

Overview

Perfect for code refactoring, style guide enforcement, and converting between different programming language naming standards.

Live Test Variable Name Converter Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as VariableNameConverterSkill. 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": "VariableNameConverterSkill",
  "arguments": {
    "variables": "[\"myVariable\",\"another_var\"]",
    "to": "camelCase"
  }
}

You do not name the tool yourself; the model picks it. Asking about ["myVariable","another_var"] in the terms this skill covers is enough for it to reach for VariableNameConverterSkill on its own — naming it explicitly also works, and is the way to force the call.

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
`variables`Required	array	Array of variable names to convert (max 100). Every entry must be a string.
`to`Required	string	Target naming convention `camelCasePascalCasesnake_casekebab-caseCONSTANT_CASE`

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": {
    "results": [
      {
        "original": "myVariableName",
        "converted": "my_variable_name"
      },
      {
        "original": "another_var_name",
        "converted": "another_var_name"
      },
      {
        "original": "SomeClassName",
        "converted": "some_class_name"
      },
      {
        "original": "kebab-case-name",
        "converted": "kebab_case_name"
      },
      {
        "original": "CONSTANT_VALUE",
        "converted": "c_o_n_s_t_a_n_t__v_a_l_u_e"
      }
    ],
    "count": 5,
    "targetFormat": "snake_case"
  }
}

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
`results`Premium	array[5]		Array of converted variable names with original and converted values
`results.0.original`Premium	string	`myVariableName`	Original variable name before conversion
`results.0.converted`Premium	string	`my_variable_name`	Variable name after conversion to target format
`count`	number	`5`	Number of variables converted in the request
`targetFormat`	string	`snake_case`	Target naming convention used for conversion

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 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Code Refactoring: Convert variable names when refactoring code between different style guides
Language Migration: Migrate variable naming between programming languages with different conventions
Style Enforcement: Enforce consistent naming conventions across codebases
Bulk Conversion: Convert multiple variable names simultaneously for large-scale refactoring

Other ways to use Variable Name Converter Skill

Set up Variable Name Converter 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 →