Use Sep for high-performance separated-value parsing and writing in .NET, including delimiter inference, explicit parser/writer options, and low-allocation row/column workflows.

MITAuto-check passedAgent Workflows

Install Sep

skills CLI
$ npx skills add managedcode/dotnet-skills --skill sep -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install managedcode/dotnet-skills sep --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/managedcode/dotnet-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/catalog/Libraries/Sep/skills/sep .claude/skills/sep && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sep
GitHub stars
486
Token cost
~1.4k tokens
SKILL.md length
430 words
Files
3 (incl. references)
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Use Sep for high-performance separated-value parsing and writing in .NET, including delimiter inference, explicit parser/writer options, and low-allocation row/column workflows.

  • Works in 7 steps: Decide schema shape → Build reader with Sep.Reader(...) and… → Read rows and map columns as… → …
  • : delimited data needs are performance-sensitive and allocation-aware
  • SKILL.md covers Trigger On, Install, Workflow and Best practices, plus 4 more sections
  • Calls dotnet

What it does

Sep is an agent skill from managedcode/dotnet-skills. Use Sep for high-performance separated-value parsing and writing in .NET, including delimiter inference, explicit parser/writer options, and low-allocation row/column workflows. USE FOR: delimited data needs are performance-sensitive and allocation-aware; project needs explicit control over separator inference, escaping, trimming, and header behavior;. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `manifest.json` and `references/overview.md`). Compatibility notes: Requires a .NET project that can reference the Sep package and accept span/ref-struct row/column APIs for row-by-row processing.

It sits in Agent Workflows, covering Codebase knowledge for agents. It works with .NET. The repository describes itself as: Installable .NET skill catalog and CLI for Codex, Claude Code, GitHub Copilot, and Gemini. The licence is MIT.

When your agent uses it

  • : delimited data needs are performance-sensitive and allocation-aware
  • Project needs explicit control over separator inference
  • Header behavior
  • : unrelated stacks

Example prompts

  • “/sep”

Requirements

  • Compatibility (from SKILL.md): Requires a .NET project that can reference the `Sep` package and accept span/ref-struct row/column APIs for row-by-row processing.

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Decide schema shape
  2. Build reader with Sep.Reader(...) and explicit options only where needed
  3. Read rows and map columns as ReadOnlySpan first, convert only when needed.
  4. For output, use reader.Spec.Writer() when you need the same separator/culture as input.
  5. Control writer behavior with Sep.Writer(...) and SepWriterOptions (WriteHeader, Escape, DisableColCountCheck).
  6. Add async only where it brings value and your runtime is C# 13 / .NET 9+ for await foreach over async reader rows.
  7. Use ParallelEnumerate for CPU-heavy transformations only after benchmarking single-threaded baseline.

What it can do on your machine

Read from SKILL.md and the folder at commit 535dd55. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • dotnet

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • nuget.org
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires a .NET project that can reference the `Sep` package and accept span/ref-struct row/column APIs for row-by-row processing.

    From compatibility in the SKILL.md frontmatter.

Context cost

Sep loads about 1.4k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 148 tokens; SKILL.md has 430 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~148
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from managedcode/dotnet-skills at commit 535dd55, republished under its MIT licence (© managedcode). 430 words, ~1,388 tokens.

Download SKILL.mdSave it as .claude/skills/sep/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
sep
description
Use Sep for high-performance separated-value parsing and writing in .NET, including delimiter inference, explicit parser/writer options, and low-allocation row/column workflows. USE FOR: delimited data needs are performance-sensitive and allocation-aware; project needs explicit control over separator inference, escaping, trimming, and header behavior;. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
compatibility
Requires a .NET project that can reference the `Sep` package and accept span/ref-struct row/column APIs for row-by-row processing.

Sep for .NET separated values

Trigger On

  • delimited data needs are performance-sensitive and allocation-aware
  • project needs explicit control over separator inference, escaping, trimming, and header behavior
  • reading/writing large or long-lived file pipelines in ML, ETL, or analytics workloads
  • startup/perf tests require AOT/trimming-friendly CSV/TSV processing

Install

  • NuGet:
    • dotnet add package Sep
    • dotnet add package Sep --version <version>
  • XML package reference:
    • <PackageReference Include="Sep" Version="x.y.z" />
  • Verify baseline support by checking the package page:
  • Source:

Workflow

mermaid
flowchart LR
  A[Input source: file/text/stream] --> B[Sep.Reader or Sep.New(...).Reader]
  B --> C[SepReaderOptions]
  C --> D[Rows -> Cols -> Span/Parse]
  D --> E[Transform and validate]
  E --> F[SepWriter via SepWriterOptions]
  F --> G[To file/text output]
  1. Decide schema shape
    • header present or no header
    • separator known (;, ,, tab, custom) or infer from first row
    • row/column quoting rules
  2. Build reader with Sep.Reader(...) and explicit options only where needed:
    • Sep.Reader() for inferred separator from header-like first row
    • Sep.New(',').Reader(...) for explicit separator mode
    • Sep.Reader(o => o with { HasHeader = false }) if header is absent
  3. Read rows and map columns as ReadOnlySpan<char> first, convert only when needed.
  4. For output, use reader.Spec.Writer() when you need the same separator/culture as input.
  5. Control writer behavior with Sep.Writer(...) and SepWriterOptions (WriteHeader, Escape, DisableColCountCheck).
  6. Add async only where it brings value and your runtime is C# 13 / .NET 9+ for await foreach over async reader rows.
  7. Use ParallelEnumerate for CPU-heavy transformations only after benchmarking single-threaded baseline.
Install and read patterns
csharp
using var reader = Sep.Reader(o => o with
{
    HasHeader = true,
    Unescape = true,
    Trim = SepTrim.Both
}).FromText(data);

foreach (var row in reader)
{
    var id = row["Id"].Parse<int>();
    var name = row[1].ToString();
    // process row
}
Write patterns
csharp
using var reader = Sep.Reader().FromFile("input.csv");
using var writer = reader.Spec.Writer().ToFile("output.csv");

foreach (var row in reader)
{
    using var writeRow = writer.NewRow(row);
    writeRow["Amount"].Format(row["Amount"].Parse<double>() * 1.2);
}
Async reading and writing
csharp
var text = "A;B\n1;hello\n";

using var reader = await Sep.Reader().FromTextAsync(text);
await using var writer = reader.Spec.Writer().ToText();

await foreach (var row in reader)
{
    await using var writeRow = writer.NewRow(row);
    var normalized = row["B"].ToString().ToUpperInvariant();
    writeRow["B"].Set(normalized);
}
Common configuration patterns
  • Header-driven read
    • default HasHeader = true
    • query by name: row["ColName"]
  • Headerless pipelines
    • HasHeader = false
    • use index-based access: row[0], row[1]
  • Round-trip output
    • start writer with reader.Spec.Writer() to preserve inference and formatting contract
  • Speed-first processing
    • keep default buffer + culture unless profiling proves a need to tune
Show full SKILL.md (173 more words)Show less

Best practices

  • Parse to primitive types with Parse<T> in hot paths to avoid extra allocations.
  • Keep ToString/format conversions at the edge (presentational layers), not in inner loops.
  • Prefer Unescape, Trim, and DisableQuotesParsing settings deliberately and test with realistic samples.
  • For large transforms, isolate heavy CPU work after enumeration and then apply ParallelEnumerate where appropriate.

Limitations to check before production

  • SepReader.Row and SepWriter.Row are ref structs:
    • avoid patterns that store rows beyond immediate scope
    • materialize if you truly need random async/LINQ-style buffering
  • SepReader row iteration is row-by-row by design; it is intentionally not the same as a classic collection model.

Deliver

  • installation and usage guide that is ready to copy into a .NET repo
  • practical reader/writer configuration patterns
  • clear notes on defaults, tradeoffs, and constraints

Validate

  • dotnet add package Sep installs correctly and project compiles
  • one file-read sample and one file-write sample execute successfully
  • header/no-header and explicit-separator cases are covered
  • at least one validation sample for quoting/unescaping or async path exists if required by task

Load References

© managedcode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in catalog/Libraries/Sep/skills/sep of managedcode/dotnet-skills.

  • SKILL.md
  • manifest.json
  • references/overview.md

Open the folder on GitHubat commit 535dd55

Compare with similar skills

Sep next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sep compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sep this skillmanagedcode/dotnet-skills486—~1.4kAutomated safety check: PassMIT
Microsoft Skill CreatorMicrosoftDocs/mcp1.9k3 repos~2.1kAutomated safety check: PassCC-BY-4.0
Copilot Session Failure Analysisdotnet/maui23k—~3.4kAutomated safety check: PassMIT
ccc Semantic Code Searchcocoindex-io/cocoindex-code2.7k—~938Automated safety check: PassApache-2.0
Context Engineeringabashev/vfs-s31069 repos~2.6kAutomated safety check: NotesApache-2.0
Repomix Codebase Packeryamadashy/repomix29k—~1.3kAutomated safety check: NotesMIT

Similar skills

  • Microsoft Skill Creator

    MicrosoftDocs/mcp

    Official

    Create agent skills for Microsoft technologies using official documentation.

    1.9k GitHub starsUsed in 3 repos~2.1k tokens
    Agent WorkflowsAuto-check passed
  • Mines local Copilot CLI session logs for dotnet/maui to rank costly or failing runs, tag recurring failure modes, propose repo edits and emit guard evals.

    23k GitHub stars~3.4k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • ccc Semantic Code Search

    cocoindex-io/cocoindex-code

    Semantic code search and index management with the ccc CLI: the agent initializes, indexes and queries the project by concept, filtering by language or path.

    2.7k GitHub stars~938 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Context Engineering

    abashev/vfs-s3

    Optimizes agent context setup. An agent skill from abashev/vfs-s3.

    106 GitHub starsUsed in 9 repos~2.6k tokens
    Agent WorkflowsAuto-check: notes
  • Repomix Codebase Packer

    yamadashy/repomix

    Packs a local directory or remote GitHub repository into one AI-friendly file with Repomix, then searches it to explore structure, find patterns and count tokens.

    29k GitHub stars~1.3k tokensUpdated 4 days ago
    Agent WorkflowsAuto-check: notes
  • Microsoft Docs

    MicrosoftDocs/mcp

    Official

    Understand Microsoft technologies by querying official documentation.

    1.9k GitHub starsUsed in 1 repo~723 tokens
    Agent WorkflowsAuto-check passed

More from managedcode/dotnet-skills

All 81 skills in this repo
  • Analyzer Config

    managedcode/dotnet-skills

    Use a repo-root .editorconfig to configure free .NET analyzer and style rules.

    486 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Archunitnet

    managedcode/dotnet-skills

    Use the open-source free ArchUnitNET library for architecture rules in .NET tests.

    486 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Aspire

    managedcode/dotnet-skills

    Build, upgrade, and operate Aspire 13.5.x C or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for…

    486 GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Aspnet Core

    managedcode/dotnet-skills

    Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.

    486 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Asynkron Profiler

    managedcode/dotnet-skills

    Use the open-source free Asynkron.Profiler dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts.

    486 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Azure Functions

    managedcode/dotnet-skills

    Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns.

    486 GitHub stars~2.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Sep

What does Sep do?

Use Sep for high-performance separated-value parsing and writing in .NET, including delimiter inference, explicit parser/writer options, and low-allocation row/column workflows. Sep is an agent skill from managedcode/dotnet-skills.NET, including delimiter inference, explicit parser/writer options, and low-allocation row/column workflows.

When should I use Sep?

Sep fits situations like: : delimited data needs are performance-sensitive and allocation-aware; project needs explicit control over separator inference; header behavior; : unrelated stacks.

How do I install Sep in Claude Code?

Run `npx skills add managedcode/dotnet-skills --skill sep -a claude-code`. Or copy the skill folder (catalog/Libraries/Sep/skills/sep in managedcode/dotnet-skills) into .claude/skills/sep in your project. Claude Code loads it when a task matches its description.

How do I install Sep in Codex?

Run `npx skills add managedcode/dotnet-skills --skill sep -a codex`. Or copy the skill folder (catalog/Libraries/Sep/skills/sep in managedcode/dotnet-skills) into .agents/skills/sep in your project. Codex loads it when a task matches its description.

Can I use Sep in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add managedcode/dotnet-skills --skill sep -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sep, .gemini/skills/sep, .github/skills/sep and .opencode/skills/sep in your project.

What does Sep need to run?

Going by SKILL.md and its folder, Sep needs the command-line tools its instructions call (dotnet). Compatibility (from SKILL.md): Requires a .NET project that can reference the `Sep` package and accept span/ref-struct row/column APIs for row-by-row processing..

Does Sep access the network?

SKILL.md names 2 domains. As links in the text: nuget.org and github.com. This is read from the text; nothing was executed.

Is Sep safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sep use?

Sep is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sep use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 297 tokens, read only when the agent opens those files.

What are the alternatives to Sep?

Skills that share tags, products or a category with Sep: Microsoft Skill Creator (MicrosoftDocs/mcp, 1.9k stars), Copilot Session Failure Analysis (dotnet/maui, 23k stars), ccc Semantic Code Search (cocoindex-io/cocoindex-code, 2.7k stars) and Context Engineering (abashev/vfs-s3, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sep?

managedcode (a GitHub organization) maintains it in managedcode/dotnet-skills, which has 486 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 7, 2026.

Source: managedcode/dotnet-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.