CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

you-might-not-need-url-state

Analyze and fix URL/query-param state anti-patterns — manual useSearchParams reads, hand-built query mutations, view-state trapped in useState, and objects in the URL

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/you-might-not-need-url-state/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%Scale 1-5

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

A tight, expert-level instruction skill that wastes no tokens and gives concrete, named-API guidance for detection and remediation. The two gaps are the absence of a verification step after batch fix application and the reliance on an out-of-bundle rules file for essential detail. Both are addressable with a small validation step and an inline canonical example.

Suggestions

Add a verification step after applying fixes, e.g. "5. Run typecheck/lint (and tests if present) over the changed files; fix any breakages before finishing" — this removes the batch-operation cap on workflow clarity.

Inline a minimal canonical search-params.ts example (one parseAsString + one createSortParams entry) so the key artifact is copy-paste ready without leaving the skill.

Either bundle the decision table/debounce pattern as a references/ file inside the skill, or note explicitly what to do if .claude/rules/sim-url-state.md is absent.

DimensionReasoningScore

Conciseness

The body is lean and dense: it assumes competence with nuqs, React Query, Zustand, and Next.js Suspense without explaining any of them, and every parenthetical carries a substantive exception or carve-out rather than padding. Not 4: there is no over-explanation anywhere that could be trimmed.

5 / 5

Actionability

Guidance is concrete and executable in the main: named APIs ("useQueryState/useQueryStates", "createSortParams + useUrlSort", "useDebouncedSearchSetter"), per-anti-pattern replace-with mappings, and specific fix wiring in step 4. As an instruction-only skill code absence is not penalized, but a minimal search-params.ts example inline would remove the remaining gap, keeping it below the 5 anchor.

4 / 5

Workflow Clarity

Four clearly sequenced steps (read rules → analyze scope → classify via decision table → apply/propose fixes), but the default mode applies fixes across a whole scope (a batch edit operation) with no verification checkpoint such as typecheck/lint/test after applying. Per the scoring notes, a batch operation without validation is capped at 3. Not 2: the sequence itself is complete and well-defined, not gappy.

3 / 5

Progressive Disclosure

Well-organized sections (Context, References, Anti-patterns, Steps) with one-level-deep, clearly signaled references that each describe their contents. It falls short of 5 because the source-of-truth detail (decision table, debounce pattern, sort convention) is deferred to `.claude/rules/sim-url-state.md`, which is not part of the skill bundle and cannot be navigated from the skill itself.

4 / 5

Total

16

/

20

Passed

Description

71%Weight 40%Scale 1-5

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 highly specific, distinctive description that clearly names the capability domain and enumerates concrete anti-patterns. Its main weakness is the missing "Use when..." trigger clause, which caps completeness, and slightly incomplete natural-keyword coverage. Adding explicit trigger guidance and common synonyms would lift it to top marks.

Suggestions

Add an explicit trigger clause, e.g. "Use when reviewing or refactoring URL/search-param state in Next.js/React apps, or when view-state should be shareable via links."

Include common natural synonyms users would say — "search params", "query string", "deep link" — alongside "URL/query-param".

Clarify the context (Next.js + nuqs) so the description is more distinguishable from generic React state-management skills.

DimensionReasoningScore

Specificity

"Analyze and fix" plus four enumerated concrete anti-patterns ("manual useSearchParams reads, hand-built query mutations, view-state trapped in useState, and objects in the URL") gives multiple specific actions with comprehensive coverage of the skill's niche. Not 4: the anti-pattern list is exhaustive for this domain rather than having minor gaps.

5 / 5

Completeness

The "what" is clear (analyze and fix URL/query-param state anti-patterns), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2: the "what" is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Good natural keywords — "URL", "query-param", "useSearchParams" — that users would plausibly say. A few common variations are missing ("search params", "query string", "deep link"/"shareable link"), so it falls short of the comprehensive synonym coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The URL/query-param state niche is clear and distinctive with specific technical triggers (useSearchParams, query mutations, objects in the URL), but phrases like "view-state trapped in useState" and "Analyze and fix" create minor overlap risk with general React state-management or refactoring skills. Not 5: the overlap with closely related React state skills is non-trivial.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

simstudioai/sim

Path

.agents/skills/you-might-not-need-url-state/SKILL.md

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.