agentleFS
glennawatsonglennawatson/CSharpAgentSkills/AGENTS.md

CSharpAgentSkills

AGENTS.md2 starsChanged 42 days agoMITView on GitHub

This repository holds agent skills for C# and .NET work. It contains no buildable solution.

The file

We split this AGENTS.md into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep skills agent-agnostic.

    line 13
  2. Distinctive:

    Keep instructions concise and direct.

    line 16
  3. Distinctive:

    Add a new skill to the table in README.md.

    line 20
  4. Very specific:

    Commit messages follow Conventional Commits (see skills/commit-messages).

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Repository guide

This repository holds agent skills for C# and .NET work. It contains no buildable solution.

Layout

  • skills/<name>/SKILL.md: one skill per folder. The folder name must match the name in the frontmatter.
  • Companion files (helpers, examples, targets) live beside the SKILL.md that references them.

Writing skills

  • Frontmatter has name (lowercase, hyphenated) and description. The description says when to use the skill; agents choose skills from it.
  • Keep skills agent-agnostic. Do not name agent-specific tools, paths or products; describe the action instead.
  • Refer to other skills by name in backticks, for example csharp-tunit. Only reference skills that exist in this repository.
  • Example .cs files are single-file apps (dotnet run file.cs). Keep them runnable on the current .NET SDK.
  • Keep instructions concise and direct.

Changes

  • Add a new skill to the table in README.md.
  • Commit messages follow Conventional Commits (see skills/commit-messages).

Download now (ZIP)

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.