Agent skill

Mcaf Dotnet Features

by managedcode in managedcode/Storage

Write modern, version-aware C for .NET repositories. An agent skill from managedcode/Storage.

MITAuto-check passedAgent Workflows

Install Mcaf Dotnet Features

skills CLI
$ npx skills add managedcode/Storage --skill mcaf-dotnet-features -a claude-code

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

GitHub CLI
$ gh skill install managedcode/Storage mcaf-dotnet-features --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/Storage.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/mcaf-dotnet-features .claude/skills/mcaf-dotnet-features && 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
mcaf-dotnet-features
GitHub stars
138
Token cost
~1.3k tokens
SKILL.md length
680 words
Files
2 (incl. references)
Skills in repo
41
Repo updated
First seen
Licence
MIT

At a glance

Write modern, version-aware C for .NET repositories. An agent skill from managedcode/Storage.

  • Works in 3 steps: Read the nearest AGENTS.md and confirm… → Run this skill's Workflow through the… → Return the Required Result Format with…
  • Choosing language features across C versions
  • SKILL.md covers Trigger On, Value, Do Not Use For and Inputs, plus 8 more sections
  • Calls dotnet and rg

What it does

Mcaf Dotnet Features is an agent skill from managedcode/Storage. Write modern, version-aware C for .NET repositories. Use when choosing language features across C versions, especially C 13 and C 14, while staying compatible with the repo's target framework and LangVersion.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/csharp-modern-features.md`). Compatibility notes: Requires a C or .NET repository; respects explicit LangVersion and target framework settings.

It sits in Agent Workflows. It works with .NET and C#. The repository describes itself as: Storage library provides a universal interface for accessing and manipulating data in different cloud blob storage providers. The licence is MIT.

When your agent uses it

  • Choosing language features across C versions
  • Especially C 13 and C 14
  • While staying compatible with the repos target framework and LangVersion

Example prompts

  • “/mcaf-dotnet-features”

Requirements

  • Compatibility (from SKILL.md): Requires a C# or .NET repository; respects explicit `LangVersion` and target framework settings.

Workflow steps

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

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

What it can do on your machine

Read from SKILL.md and the folder at commit 5d32121. 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
    • rg

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

  • Network

    No URLs in SKILL.md.

    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 C# or .NET repository; respects explicit `LangVersion` and target framework settings.

    From compatibility in the SKILL.md frontmatter.

Context cost

Mcaf Dotnet Features loads about 1.3k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 680 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.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/Storage at commit 5d32121, republished under its MIT licence (© managedcode). 680 words, ~1,291 tokens.

Download SKILL.mdSave it as .claude/skills/mcaf-dotnet-features/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
mcaf-dotnet-features
description
Write modern, version-aware C# for .NET repositories. Use when choosing language features across C# versions, especially C# 13 and C# 14, while staying compatible with the repo's target framework and `LangVersion`.
compatibility
Requires a C# or .NET repository; respects explicit `LangVersion` and target framework settings.

MCAF: .NET Features

Trigger On

  • the repo wants more modern idiomatic C# code
  • a change depends on language-version compatibility
  • the team is upgrading or reviewing C# feature usage across versions
  • you need to know whether a C# 13 or C# 14 feature is safe to use

Value

  • produce a concrete project delta: code, docs, config, tests, CI, or review artifact
  • reduce ambiguity through explicit planning, verification, and final validation skills
  • leave reusable project context so future tasks are faster and safer

Do Not Use For

  • non-C# .NET languages such as F# or VB
  • analyzer-only or formatter-only setup with no language feature choice

Inputs

  • target TFM or TFMs
  • explicit LangVersion, if any
  • current SDK version
  • team style rules in .editorconfig and AGENTS.md

Quick Start

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

  1. Detect the real language ceiling from the repo's target framework and explicit LangVersion.
  2. Prefer stable features that the current repo actually supports.
  3. Use modern syntax when it reduces ceremony, improves correctness, or makes invariants clearer.
  4. Do not mass-rewrite a codebase into newer syntax unless the repo wants that churn.
  5. Treat preview features as opt-in only. Never assume preview because the current machine has a newer SDK.
  6. Pay special attention to C# 13 and C# 14:
    • C# 13 is the stable language for .NET 9
    • C# 14 is the stable language for .NET 10
  7. When feature selection changes architecture, style rules, or generated-code patterns, coordinate with:
    • mcaf-dotnet
    • mcaf-dotnet-analyzer-config
    • mcaf-solid-maintainability
  8. After feature-driven refactors, run the repo's .NET quality pass through mcaf-dotnet.

Bootstrap When Missing

If the requested C# feature depends on SDK or language support the repo does not have yet:

  1. Detect current state:
    • dotnet --list-sdks
    • rg -n "TargetFramework|LangVersion|TargetFrameworks" -g '*.csproj' -g 'Directory.Build.*' .
  2. Confirm whether the repo wants to stay on the current stable language level or intentionally upgrade.
  3. If the feature requires a newer supported SDK or target framework, upgrade the repo toolchain deliberately instead of relying on the local machine by accident.
  4. If the repo needs explicit LangVersion, record it in project or shared MSBuild config.
  5. Run dotnet build SOLUTION_OR_PROJECT after the feature or toolchain change and return status: configured or status: improved.
  6. If the repo intentionally stays below the required language level, return status: not_applicable.
Show full SKILL.md (271 more words)Show less

Deliver

  • modern C# code that fits the repo's real language version
  • fewer obsolete patterns when a newer stable feature is clearer
  • no accidental preview or unsupported-language drift

Validate

  • the chosen syntax is supported by the repo's TFM and LangVersion
  • the feature improves clarity, correctness, or maintainability
  • preview-only features are used only when the repo explicitly opted in
  • style and analyzer rules still agree with the new syntax

Ralph Loop

Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.

  1. Plan first (mandatory):
    • analyze current state
    • define target outcome, constraints, and risks
    • write a detailed execution plan
    • list final validation skills to run at the end, with order and reason
  2. Execute one planned step and produce a concrete delta.
  3. Review the result and capture findings with actionable next fixes.
  4. Apply fixes in small batches and rerun the relevant checks or review steps.
  5. Update the plan after each iteration.
  6. Repeat until outcomes are acceptable or only explicit exceptions remain.
  7. If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.
Required Result Format
  • status: complete | clean | improved | configured | not_applicable | blocked
  • plan: concise plan and current iteration step
  • actions_taken: concrete changes made
  • validation_skills: final skills run, or skipped with reasons
  • verification: commands, checks, or review evidence summary
  • remaining: top unresolved items or none

For setup-only requests with no execution, return status: configured and exact next commands.

Load References

  • read references/csharp-modern-features.md first

Example Requests

  • "Make this C# code more modern."
  • "Which features can we use on .NET 9?"
  • "Review this repo for C# 13 or C# 14 opportunities."

© 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 1 other file (references) in .codex/skills/mcaf-dotnet-features of managedcode/Storage.

  • SKILL.md
  • references/csharp-modern-features.md

Open the folder on GitHubat commit 5d32121

Compare with similar skills

Mcaf Dotnet Features 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.

Mcaf Dotnet Features compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mcaf Dotnet Features this skillmanagedcode/Storage138—~1.3kAutomated safety check: PassMIT
Init My ProjectMCSLTeam/MCServerLauncher-Future121—~2.1kAutomated safety check: PassGPL-3.0
MCP Csharpatherio-danp/cde-dotnetcc109—~1.2kAutomated safety check: NotesNone
Csharp MCP Server GeneratorILoveDotNet/ilovedotnet155—~560Automated safety check: PassCC0-1.0
Dotnet MCP Builderboshi-xixixi/TraeSkill274—~1.7kAutomated safety check: PassMIT
Blazormanagedcode/dotnet-skills486—~2.1kAutomated safety check: PassMIT

Similar skills

  • Init My Project

    MCSLTeam/MCServerLauncher-Future

    Bootstrap reusable project governance for a new or existing repo.

    121 GitHub stars~2.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • MCP Csharp

    atherio-danp/cde-dotnetcc

    Create, debug, test, and publish MCP (Model Context Protocol) servers in C using the official ModelContextProtocol SDK — tools/prompts/resources, stdio vs HTTP transport, MapMcp hosting.

    109 GitHub stars~1.2k tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check: notes
  • Csharp MCP Server Generator

    ILoveDotNet/ilovedotnet

    Generate a complete MCP server project in C with tools, prompts, and proper configuration

    155 GitHub stars~560 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Dotnet MCP Builder

    boshi-xixixi/TraeSkill

    Build Model Context Protocol (MCP) servers in C/.NET against the current ModelContextProtocol 1.x NuGet packages.

    274 GitHub stars~1.7k tokensUpdated 4 mo ago
    Agent WorkflowsAuto-check passed
  • Blazor

    managedcode/dotnet-skills

    Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices.

    486 GitHub stars~2.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Marketplace Publishing

    Aaronontheweb/dotnet-skills

    Workflow for publishing skills and agents to the dotnet-skills Claude Code marketplace.

    1.2k GitHub starsUsed in 1 repo~1.5k tokens
    Agent WorkflowsAuto-check passed

More from managedcode/Storage

All 41 skills in this repo
  • Mcaf Adr Writing

    managedcode/Storage

    Create or update an ADR under docs/ADR/ for architectural decisions, dependency changes, data-model changes, or cross-cutting policy shifts.

    138 GitHub stars~951 tokensUpdated today
    Auto-check passed
  • Mcaf Agile Delivery

    managedcode/Storage

    Shape delivery workflow around backlog quality, roles, ceremonies, and engineering feedback.

    138 GitHub stars~883 tokensUpdated today
    Auto-check passed
  • Mcaf Architecture Overview

    managedcode/Storage

    Create or update docs/Architecture.md as the global architecture map for a solution.

    138 GitHub stars~950 tokensUpdated today
    Auto-check passed
  • Mcaf CI CD

    managedcode/Storage

    Design or refine CI/CD workflows, quality gates, release flow, and safe AI-assisted pipeline authoring.

    138 GitHub stars~981 tokensUpdated today
    Auto-check passed
  • Mcaf Code Review

    managedcode/Storage

    Prepare for, perform, or tighten code review workflow: PR scope, review checklist, reviewer expectations, and merge hygiene.

    138 GitHub stars~957 tokensUpdated today
    Auto-check passed
  • Mcaf Devex

    managedcode/Storage

    Improve developer experience for multi-component solutions: onboarding, F5 contract, cross-platform tasks, local inner loop, and reproducible setup.

    138 GitHub stars~911 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Mcaf Dotnet Features

What does Mcaf Dotnet Features do?

Write modern, version-aware C for .NET repositories. An agent skill from managedcode/Storage. Mcaf Dotnet Features is an agent skill from managedcode/Storage.NET repositories.

When should I use Mcaf Dotnet Features?

Mcaf Dotnet Features fits situations like: choosing language features across C versions; especially C 13 and C 14; while staying compatible with the repos target framework and LangVersion.

How do I install Mcaf Dotnet Features in Claude Code?

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

How do I install Mcaf Dotnet Features in Codex?

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

Can I use Mcaf Dotnet Features 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/Storage --skill mcaf-dotnet-features -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcaf-dotnet-features, .gemini/skills/mcaf-dotnet-features, .github/skills/mcaf-dotnet-features and .opencode/skills/mcaf-dotnet-features in your project.

What does Mcaf Dotnet Features need to run?

Going by SKILL.md and its folder, Mcaf Dotnet Features needs the command-line tools its instructions call (dotnet and rg). Compatibility (from SKILL.md): Requires a C# or .NET repository; respects explicit `LangVersion` and target framework settings..

Does Mcaf Dotnet Features access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Mcaf Dotnet Features 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 Mcaf Dotnet Features use?

Mcaf Dotnet Features 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 Mcaf Dotnet Features use?

About 1.3k tokens (SKILL.md is roughly 5.2k 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 1.4k tokens, read only when the agent opens those files.

What are the alternatives to Mcaf Dotnet Features?

Skills that share tags, products or a category with Mcaf Dotnet Features: Init My Project (MCSLTeam/MCServerLauncher-Future, 121 stars), MCP Csharp (atherio-danp/cde-dotnetcc, 109 stars), Csharp MCP Server Generator (ILoveDotNet/ilovedotnet, 155 stars) and Dotnet MCP Builder (boshi-xixixi/TraeSkill, 274 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mcaf Dotnet Features?

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

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