agentleFS
pnppnp/powershell/.claude/skills/new-cmdlet/SKILL.md

new-cmdlet

Skill906 starsChanged 2 months agoMITView on GitHub

The conventions a PnP PowerShell cmdlet must satisfy - base class selection, permission attributes, PipeBinds, parameter validation, Graph and CSOM call patterns, and the documentation plus changelog artefacts that make a cmdlet complete. Use when writing, modifying or reviewing cmdlet code, or when deciding which base class or permission attribute applies.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Follow .agents/skills/new-cmdlet/SKILL.md — read it now and apply it.

    line 8

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

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

PnP PowerShell cmdlet conventions

Follow .agents/skills/new-cmdlet/SKILL.md — read it now and apply it.

The playbook is the single source shared with Codex and Copilot. Do not duplicate its content here; changes belong in the playbook.

Supporting references:

  • .agents/skills/dotnet-standards/SKILL.md — C# 12 / .NET 8 and PowerShell cmdlet design rules
  • .agents/skills/cmdlet-scaffolder/SKILL.md — the step-by-step procedure for creating a new cmdlet
  • .agents/skills/permissions-auditor/SKILL.md — how the permission attributes are interpreted, and how a typo'd resource prefix silently becomes a SharePoint scope
  • AGENTS.md — repository context

Never commit, push, or open a PR — leave the work in the tree and hand it over. See Human in the loop.

Remember the constraint: you cannot run these cmdlets. Anything calling an API you have not invoked is a draft — list what you inferred rather than verified.

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.