CtrlK
BlogDocsLog inGet started
Tessl Logo

pwsh

在 Windows PowerShell 5.1 与 PowerShell 7 中编写和执行稳定命令,重点处理引号、管道符、原生命令参数传递与跨版本兼容。遇到 `--jq`/过滤表达式被 PowerShell 误解析、同一命令在 pwsh5 与 pwsh7 行为不一致、或需要为 pwsh7.3+ 增加参数传递适配时使用此 skill。

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-organized, concise overview with a clear versioned workflow, error-recovery loop, and exemplary progressive disclosure to real reference files. Its main gap is actionability: the body instructs with named constructs but ships no inline runnable examples, deferring all executable code to the references.

Suggestions

Add one or two short inline code blocks to the body (e.g. the $PSVersionTable version check and a single-quoted --jq example) so the most common fixes are copy-paste ready without opening a reference.

In the Workflow or Baseline Rules, show the canonical single-quote pattern for passing a '|'-containing --jq expression inline, since that is the skill's flagship trigger.

Optionally inline the $PSNativeCommandArgumentPassing Legacy save/restore try/finally snippet, as it is the single most concrete pwsh7 adaptation and currently lives only in a reference.

DimensionReasoningScore

Conciseness

The ~45-line body is lean, assumes Claude's PowerShell competence, and avoids explaining concepts Claude already knows; every section earns its tokens.

3 / 3

Actionability

Guidance names concrete constructs ($PSVersionTable.PSVersion, $PSNativeCommandArgumentPassing, --%, ??/||/&&) but the body contains no inline executable code blocks — all copy-paste examples are deferred to the reference files, so it is concrete yet not copy-paste ready.

2 / 3

Workflow Clarity

A clear 5-step sequence opens with a version-confirmation checkpoint (read $PSVersionTable.PSVersion), and the Failure Handling section provides an explicit detect→inspect→rewrite feedback loop for error recovery.

3 / 3

Progressive Disclosure

The Reference section signals three one-level-deep files with per-file descriptions and an explicit 'load on demand' instruction; all referenced paths exist under references/ and content is appropriately split.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it concisely states the capability and gives explicit, concrete use-when triggers tied to recognizable failure scenarios, all in third person. It is specific enough to avoid overlap with generic shell skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '编写和执行稳定命令' plus explicit focus on quotes, pipes, native-command argument passing, and cross-version compatibility — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (write/execute stable cross-version commands) and when ('遇到...时使用此 skill' enumerates concrete trigger scenarios), matching the what+when anchor.

3 / 3

Trigger Term Quality

Covers natural domain terms a user would say — 'PowerShell', '--jq', 'pwsh5'/'pwsh7', mis-parsed filter expressions, and version-inconsistent behavior — giving good trigger coverage.

3 / 3

Distinctiveness Conflict Risk

The niche is narrow and distinctive — pwsh5↔pwsh7 compatibility, --jq mis-parsing, 7.3+ argument-passing adaptation — with triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
BiFangKNT/mtga
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.