path-to-regexp-v8-migration

Migrate @data-client/rest path strings from path-to-regexp v6 to v8 syntax. Use when upgrading path-to-regexp, updating RestEndpoint.path or resource path strings, or when seeing errors about unexpected ?, +, (, or ) in paths.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%

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

A concise, highly actionable migration reference with concrete before→after transformations and clean section organization. Its only real gap is the absence of an explicit verification step for what is effectively a batch source rewrite.

Suggestions

Add a final verification checkpoint to the workflow: after rewriting paths, run `tsc` and/or the `typescript-tests/` suite (or call `compile()` on each path) to confirm no `Unexpected ?` / `+` / `(` / `)` errors remain.

Make the implicit locate→rewrite→validate sequence explicit with a short numbered "Migration process" section so the batch operation has a clear order and a feedback loop (fix and re-validate on failure).

Call out ordering hazards in the workflow — e.g. resolve optional `?` → `{...}` and repeating `+`/`*` → `*name` first, then re-check literal `?` escaping last, since a rewritten optional segment can reintroduce an unescaped `?`.

Dimension	Reasoning	Score
Conciseness	Lean migration reference that assumes domain competence — it never explains what path-to-regexp or path strings are, and lets before→after examples carry the weight; the few prose notes target non-obvious gotchas (literal vs optional `?`) rather than padding.	3 / 3
Actionability	Each rule is given as concrete, copy-paste-ready transformations (e.g. "/:id? → {/:id}", "/:path+ → /*path", "/(literal) → /\\(literal\\)") with executable before/after pairs and a combined-examples section.	3 / 3
Workflow Clarity	Rules and a "Where to Find Paths" locate step are present, but the batch migration across a codebase has no explicit validation/verification checkpoint (e.g. run `typescript-tests/`, `tsc`, or `compile()` to confirm no `Unexpected ?` errors), which caps a destructive/batch workflow at 2.	2 / 3
Progressive Disclosure	A single, well-organized file with clearly delineated sections (Migration Rules, Combined Examples, Where to Find Paths, Type System) and one appropriately-signaled external reference; no nested/indirect references, so the simple-skill exception applies.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 tight, third-person description that states a concrete capability and gives explicit, natural trigger guidance for a well-scoped niche. It answers both what and when without padding or over-claiming.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Migrate ... path strings from path-to-regexp v6 to v8 syntax", "updating RestEndpoint.path or resource path strings", and reacting to "errors about unexpected ?, +, (, or )" — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ("Migrate ... path strings from path-to-regexp v6 to v8 syntax") and when via a clear "Use when ..." clause with concrete triggers.	3 / 3
Trigger Term Quality	Natural trigger terms a developer would actually say are well covered: "upgrading path-to-regexp", "updating RestEndpoint.path", and "seeing errors about unexpected ?, +, (, or ) in paths".	3 / 3
Distinctiveness Conflict Risk	Occupies a very specific niche (path-to-regexp v6→v8 migration for @data-client/rest) with distinct, package-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: reactive/data-client
Path: .cursor/skills/path-to-regexp-v8-migration/SKILL.md
Commit: e823560

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.