CtrlK
BlogDocsLog inGet started
Tessl Logo

migrate-to-shoehorn

将测试文件从 `as` 类型断言迁移到 @total-typescript/shoehorn。适用于用户提到 shoehorn、想替换测试中的 `as`,或需要局部测试数据时。

68

Quality

81%

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

87%

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

The content is concise, highly actionable, and well-organized with executable before/after examples and a clear workflow. The only gap is the batch-refactor workflow's validation step, which states 'run type check' but provides no explicit fix-and-retry loop.

Suggestions

Turn the final verification step into an explicit feedback loop: 'Run `tsc --noEmit`; if errors remain, fix the remaining `as` assertions and re-run until it passes.'

Add a brief note on how to verify a specific migrated test file (e.g. run that single test) so the validation is per-file rather than only project-wide.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with no padding about what `as` or libraries are; the brief 'Why shoehorn?' rationale is justified rather than filler, so every token earns its place.

3 / 3

Actionability

It provides exact install and grep commands, three concrete before/after code patterns, and a function-selection table — all copy-paste ready and executable.

3 / 3

Workflow Clarity

The workflow is a clearly sequenced numbered list with a final '运行 type check 验证' checkpoint, but as a batch refactor across multiple test files it lacks an explicit fix→retry feedback loop, capping it at 2.

2 / 3

Progressive Disclosure

The skill is a single self-contained file with well-organized sections (Why, Install, Patterns, When to use, Workflow) and no nested references, so progressive disclosure is well handled without bundle files.

3 / 3

Total

11

/

12

Passed

Description

75%

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

The description clearly communicates a narrow, distinctive purpose with an explicit use-when clause and natural trigger phrasing. Its main weakness is that it names one core action rather than enumerating multiple concrete capabilities.

Suggestions

Broaden specificity by listing concrete actions, e.g. 'replace `as Type` with fromPartial(), `as unknown as Type` with fromAny(), and generate partial test fixtures'.

Add common trigger variations such as 'type assertions', 'test fixtures', or 'mock/partial test data' to improve keyword coverage.

DimensionReasoningScore

Specificity

Names a concrete action (migrate `as` assertions to a specific library) plus variants like replacing `as` and producing partial test data, but it is one core action rather than a comprehensive list of distinct concrete actions.

2 / 3

Completeness

It states both what it does (migrate `as` assertions to @total-typescript/shoehorn) and when to use it via an explicit '适用于…时' trigger clause, satisfying the what-and-when requirement.

3 / 3

Trigger Term Quality

Phrases like '用户提到 shoehorn', '想替换测试中的 `as`', and '需要局部测试数据' are natural user utterances, but common variations such as 'type assertions', 'test fixtures', or 'mock data' are missing.

2 / 3

Distinctiveness Conflict Risk

The niche (replacing `as` assertions in test code with shoehorn) is narrow with distinctive triggers, making it unlikely to activate for unrelated skills.

3 / 3

Total

10

/

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
vinvcn/mattpocock-skills-zh-CN
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.