agentleFS
Sign inStart free
AterDevAterDev/Perigon.CLI/.agents/skills/cli/SKILL.md

cli

Skill54 starsChanged 2 months agoApache-2.0View on GitHub

Use for .NET command-line tool development with Spectre.Console/Spectre.Console.Cli, Microsoft.Extensions.Hosting, dependency injection, localized help text, command settings, aliases, examples, terminal output, exit codes, and stdio-safe command paths.

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use desktop, api and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • zjl4616Skill

    desktop

    桌面操控。让 CC 看屏幕、动鼠标、点按钮、输文字。基于 macOS 原生 OCR 触觉反馈，不截全屏传 AI，极致省 token。触发词："/desktop"、"帮我操作桌面"、"点一下那个按钮"、"看看屏幕上有什么

    Also in 4 projects that use this

  • VercelSkill

    api

    Publish HTTP handlers for external webhooks and callbacks on this agent's subdomain.

    Also in 5 projects that use this

  • VercelSkill

    mcp

    MCP Apps integration for json-render. Use when building MCP servers that render interactive UIs in Claude, ChatGPT, Cursor, or VS Code, or when integrating json-render with the Model Context Protocol.

    Also in 5 projects that use this

  • NVIDIASkill

    testing

    Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read command registration in src/Apps/CommandLine/Program.cs.

    line 11
  2. Distinctive:

    Read the invoked service before changing command behavior.

    line 12
  3. Distinctive:

    Keep command classes thin: parse settings, validate input, set context, call services, and format output.

    line 13
  4. Distinctive:

    Put reusable behavior in CoreMod services, CodeGenerator, or Share instead of command classes.

    line 18
  5. Very specific:

    Use CommandSolutionHelper.TrySetSolutionAsync when the command needs a current solution.

    line 19
  6. Very specific:

    Use OutputHelper or AnsiConsole consistently with nearby commands.

    line 20
  7. Very specific:

    Add user-facing command text to both src/Share/Localizer.zh-CN.resx and src/Share/Localizer.en-US.resx.

    line 28
  8. Very specific:

    Add focused tests under tests/StudioMod.Tests/Commands for command behavior, config output, or error handling.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “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
SKILL.md

CLI Development

Workflow

  1. Identify the command surface under src/Apps/CommandLine.
  2. Read command registration in src/Apps/CommandLine/Program.cs.
  3. Read the invoked service before changing command behavior.
  4. Keep command classes thin: parse settings, validate input, set context, call services, and format output.

Conventions

  • Inherit from AsyncCommand<TSettings> or AsyncCommand.
  • Put reusable behavior in CoreMod services, CodeGenerator, or Share instead of command classes.
  • Use CommandSolutionHelper.TrySetSolutionAsync when the command needs a current solution.
  • Use OutputHelper or AnsiConsole consistently with nearby commands.
  • Escape dynamic Spectre markup with Markup.Escape.
  • Return 0 for success and 1 for expected validation or operation failures.
  • Register new commands in DI and CommandApp.Configure, including aliases, examples, and localized descriptions.
  • Preserve raw MCP/stdio command paths. Do not add logos, logs, or human-readable output that can break protocol clients.

Localization And Tests

  • Add user-facing command text to both src/Share/Localizer.zh-CN.resx and src/Share/Localizer.en-US.resx.
  • Add focused tests under tests/StudioMod.Tests/Commands for command behavior, config output, or error handling.

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.

Check your setup, free