Skip to content
TrustedSkillsbeta
Back to all skills

Serialization

Checked
aaronontheweb·vlatest·backend·MIT

This skill converts data structures into strings for storage or transmission, ensuring data integrity and enabling persistence across sessions.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add aaronontheweb/dotnet-skills --skill serialization -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

aaronontheweb

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned aaronontheweb/dotnet-skills at e426ed93a9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
e426ed93a9
Manifest
skills/serialization/SKILL.md
Scanned
1 file, 382 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides serialization capabilities within a .NET environment, converting data structures into strings for storage or transmission. It facilitates data persistence across sessions and enables the design of wire formats for distributed systems. The skill highlights considerations between schema-based (e.g., Protobuf, MessagePack) and reflection-based (e.g., Newtonsoft.Json) serialization approaches, recommending schema-based methods when crossing process boundaries.

When to use it

This skill is useful in the following scenarios:

  • Choosing a serialization format for APIs, messaging, or data persistence.
  • Migrating from Newtonsoft.Json to System.Text.Json.
  • Implementing serialization compatible with Ahead-of-Time (AOT) compilation.
  • Designing communication formats for distributed systems.
  • Optimizing the performance of serialization processes.

Key capabilities

  • Supports both schema-based and reflection-based serialization approaches.
  • Provides recommendations for various use cases, including REST APIs, gRPC, actor messaging, event sourcing, caching, configuration, and logging.
  • Highlights formats to avoid (BinaryFormatter, Newtonsoft.Json default, DataContractSerializer, XML) due to security vulnerabilities, versioning issues, or performance concerns.
  • Offers guidance on using System.Text.Json with source generators for AOT compatibility and improved performance.

Example prompts

Here are some example prompts that could be used with an AI agent equipped with this skill:

  • "What's the best serialization format for a gRPC service?"
  • "How do I migrate from Newtonsoft.Json to System.Text.Json in my .NET application?"
  • "Explain the difference between schema-based and reflection-based serialization."

Tips & gotchas

  • For optimal performance and AOT compatibility, prioritize using System.Text.Json with source generators when working with JSON data.
  • Be aware that reflection-based serialization can be slower than schema-based approaches due to runtime reflection overhead.
  • Avoid using BinaryFormatter due to known security vulnerabilities.