Unicode Escape Skill

Overview

The `escape` action walks the input by code point and writes every character, including plain ASCII letters and spaces, as `\u` followed by four upper-case hex digits. A character above U+FFFF, such as most emoji, is written as its UTF-16 surrogate pair, two `\uXXXX` sequences in a row, so 😀 becomes `\uD83D\uDE00`. `character_count` counts code points, so that emoji counts as one. `unicode_points` lists each character with `char`, its escape in `unicode` (the full pair for astral characters) and its `codepoint` in `U+` form, such as `U+1F600`.

The `unescape` action recognises three forms: `\uXXXX` with exactly four hex digits, the braced `\u{1F600}` form with one to six digits, and `\xXX` with two. Anything else, including other backslash escapes like `\n`, is left as literal text. A braced value above U+10FFFF returns a 400. Surrogate pairs written as two `\uXXXX` sequences recombine into the original character. The response holds the result in `unescaped`, and `character_count` there is the JavaScript string length, which counts an emoji as two.

Any `action` other than `escape` is treated as unescape. The `unicode_points` breakdown is only produced by escape, and it is null on the Free plan.

Live Test Unicode Escape Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as UnicodeEscapeSkill. 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.

{
  "name": "UnicodeEscapeSkill",
  "arguments": {
    "text": "Hello 👋"
  }
}

You do not name the tool yourself; the model picks it. Asking about Hello 👋 in the terms this skill covers is enough for it to reach for UnicodeEscapeSkill 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"
    }
  }
}

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.

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.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

{
  "status": "ok",
  "error": null,
  "data": {
    "action": "escape",
    "original": "Hello World",
    "escaped": "\\u0048\\u0065\\u006C\\u006C\\u006F\\u0020\\u0057\\u006F\\u0072\\u006C\\u0064",
    "character_count": 11,
    "unicode_points": [
      {
        "char": "H",
        "unicode": "\\u0048",
        "codepoint": "U+0048"
      },
      {
        "char": "e",
        "unicode": "\\u0065",
        "codepoint": "U+0065"
      },
      {
        "char": "l",
        "unicode": "\\u006C",
        "codepoint": "U+006C"
      },
      {
        "char": "l",
        "unicode": "\\u006C",
        "codepoint": "U+006C"
      },
      {
        "char": "o",
        "unicode": "\\u006F",
        "codepoint": "U+006F"
      },
      {
        "char": " ",
        "unicode": "\\u0020",
        "codepoint": "U+0020"
      },
      {
        "char": "W",
        "unicode": "\\u0057",
        "codepoint": "U+0057"
      },
      {
        "char": "o",
        "unicode": "\\u006F",
        "codepoint": "U+006F"
      },
      {
        "char": "r",
        "unicode": "\\u0072",
        "codepoint": "U+0072"
      },
      {
        "char": "l",
        "unicode": "\\u006C",
        "codepoint": "U+006C"
      },
      {
        "char": "d",
        "unicode": "\\u0064",
        "codepoint": "U+0064"
      }
    ]
  }
}

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.

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.

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

JSON Processing

Escape Unicode characters in JSON strings for safe transmission and storage

Code Generation

Generate Unicode escape sequences for use in source code, configuration files, or string literals

Data Migration

Convert Unicode characters to escape sequences when migrating between systems with different encoding support

Debugging

View Unicode escape sequences of characters to debug encoding issues and identify problematic characters

Other ways to use Unicode Escape Skill

Set up Unicode Escape 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.

Related

More in Data Conversion: