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

77%

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

Fix and improve this skill with Tessl

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

Quality

Content

80%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 well-structured, lean skill body that defers detail appropriately and gives concrete API-level guidance, with the main gap being a missing post-fix verification step in the workflow.

Suggestions

Add an explicit verification step after applying fixes — e.g. run typecheck/build, confirm the page renders inside the new Suspense boundary, and verify deep links still resolve — to lift workflow_clarity above the batch-operation cap of 3.

Include one minimal inline example of a co-located search-params.ts and the useQueryState wiring so the common case is copy-paste ready, closing the actionability gap.

Add a short feedback loop for the fix=false path (e.g. 'review proposed diffs against the decision table before presenting') so both branches have a checkpoint.

Dimension	Reasoning	Score
Conciseness	Lean body that assumes Claude's competence, defers detail to references, and earns its tokens — the parenthetical carve-outs encode essential 'don't touch this' nuance rather than padding.	5 / 5
Actionability	Names exact APIs and concrete fix steps (co-locate search-params.ts, wire useQueryState, createSortParams + useUrlSort, add Suspense), but defers actual code patterns to the referenced rules file with no inline copy-paste example.	4 / 5
Workflow Clarity	Four steps are clearly sequenced with a decision-table gate, but applying fixes across a scope is a batch operation with no explicit verification step (typecheck/build/render check), capping this at 3.	3 / 5
Progressive Disclosure	Clear overview with a well-signaled one-level-deep References section (rules file + nuqs docs); anti-patterns and steps are appropriately inline, making navigation easy.	5 / 5
	Total	17 / 20 Passed

Description

75%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 specific, well-targeted description with concrete anti-patterns and low conflict risk, weakened only by the absence of an explicit 'Use when' trigger clause and slightly thin synonym coverage.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases, e.g. 'Use when refactoring URL/query-param state, deep-linking view state, or migrating useState filters/tabs/sort/pagination to the URL'.

Broaden trigger terms with synonyms users actually say — 'query string', 'search params', 'URL parameters', 'deep linking' — to lift trigger term quality from 4 to 5.

Consider adding 'filters', 'tabs', 'sort', or 'pagination' as concrete shareable view-state examples to reinforce the trigger scenarios.

Dimension	Reasoning	Score
Specificity	Enumerates four concrete anti-patterns (manual useSearchParams reads, hand-built query mutations, useState-trapped view-state, objects in the URL) alongside analyze/fix verbs, giving comprehensive concrete coverage of its niche.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Good keyword coverage (URL, query-param, useSearchParams, useState), but missing common synonyms users would say like 'query string', 'search params', 'URL parameters', or 'deep linking'.	4 / 5
Distinctiveness Conflict Risk	A clear, narrow niche (URL/query-param state management) with distinct, API-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: 7945b29

Reviewed: 3 days 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.