agentleFS
alexderzalexderz/agentic-toolbox/skills/lang-powershell/SKILL.md

lang-powershell

Skill5 starsChanged 46 days agoMITView on GitHub

use this when writing or reviewing PowerShell — *.ps1, *.psm1. do not use for bash (load lang-shell / shell-safety).

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Use -WhatIf when the cmdlet supports it.

    line 24
  2. Distinctive:

    No unsigned remote scripts as the default path.

    line 51

≈ “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.

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

PowerShell

No scripts/. Process skills that may load with this one: language-router Load-with list.

Iron law

Stop on error. Quote. No Invoke-Expression.

Tooling / verify

Set-StrictMode -Version Latest
$ErrorActionPreference = 'Stop'
# run the script in a throwaway session
# Pester if the repo already has it

Use -WhatIf when the cmdlet supports it.

Idioms a linter misses

  • Named parameters. Splat hashtables. No concatenated command strings.
  • -LiteralPath when the path is data.
  • Approved verbs on exported functions.
  • cmdletbinding + process when the file is already that style.

Errors

  • $ErrorActionPreference = 'Stop' in scripts.
  • Catch specific exceptions. No empty catch.

Testing

  • Pester if present. Otherwise run in a throwaway session and read errors.

PR review

  • No iex. No download-and-execute.
  • Secrets not on the command line (they land in history).

Security

  • No Invoke-Expression / iex of data or model text.
  • No unsigned remote scripts as the default path.
  • Paths stay inside an allowlisted root.

Always

  • Strict mode. Stop on error. Named params.

Ask first

  • Running unsigned remote scripts.
  • Changing execution policy.

Never

  • Invoke-Expression of untrusted text.
  • Downloading and executing in one pipeline.
  • Secrets on the command line.

Red flags

  • "iex is fine, I wrote the string"
  • "Set-ExecutionPolicy Unrestricted just this once"

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.