agentleFS
AWSKnown publisheraws/aws-graviton-getting-started/tools/skills/languages/dotnet-x86-to-graviton/SKILL.md

dotnet-x86-to-graviton

Skill1.1k starsChanged 11 days agoLicence not identifiedView on GitHub

Validates .NET application compatibility with AWS Graviton (ARM64) architecture by checking, by content, that every resolved NuGet package (including transitive) ships an aarch64 native file for each target runtime identifier and the target's C library, glibc, libstdc++ and page size, and by checking committed native files, P/Invoke loads, x86 intrinsics, x64 project settings, Dockerfiles, Lambda descriptors and Windows-only APIs. Performs static analysis, applies ARM64-required package, code and build fixes (including the move from Windows or .NET Framework to modern .NET on Linux, after approval), documents Graviton runtime recommendations, and validates builds, publish outputs, tests and startup on ARM64. Supports PackageReference, central package management, lock files, packages.config and Paket. Use whenever a .NET workload is to run on Graviton (arm64), to assess or migrate it, even if the skill is not named; also for diagnosing DllNotFoundException and other native-library failures on arm64.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 1 mentionOct 2026: 8 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the aws/aws-graviton-getting-started repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about aws/aws-graviton-getting-started

The biggest 5 of 38 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 38

Talked about on GitHub, Hacker News and Stack Overflow (38 times).

On GitHub · 36

31 more on GitHub

On Hacker News · 1

On Stack Overflow · 1

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 10 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.