CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-state-management

Jotai state management patterns — atoms, globalAtom, contextAtom, and persistence.

54

Quality

61%

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 ./.skillshare/skills/1k-state-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

The content is well-structured and actionable with concrete code examples, and it efficiently avoids re-teaching Jotai basics. Its main weakness is the absence of an explicit multi-step workflow with validation checkpoints for adding a new atom end-to-end.

Suggestions

Add a short numbered 'Adding a new feature atom' workflow (decide global vs context -> create file in the correct location -> export hook -> verify import resolves) with an explicit validation step.

Replace the placeholder initial-state and type examples with a minimal concrete example so snippets are copy-paste ready.

Trim the repeated 'only two patterns' emphasis and the redundant 'Located in' lines in the selection guidelines, since the locations are already stated in the organization section.

DimensionReasoningScore

Conciseness

The body is mostly lean: short TypeScript snippets, bullet lists, and minimal concept re-explanation, with only minor redundancy such as the 'Located in' lines and the 'ONLY two atom patterns' note restating earlier guidance.

4 / 5

Actionability

Concrete, near-executable TypeScript examples cover creating global/context atoms and using them in components with real import paths and signatures, but placeholders like '{ /* initial state */ }' and MyFeatureState leave minor gaps versus copy-paste-ready code.

4 / 5

Workflow Clarity

The atom-selection criteria (use globalAtom when... / use contextAtom when...) are clear, but this is reference-style guidance rather than a sequenced multi-step process with validation checkpoints, so it sits at 'steps listed but no checkpoints' rather than 4.

3 / 5

Progressive Disclosure

A single self-contained file organized into well-labeled sections (organization, forbidden patterns, selection guidelines, common patterns) with no nested references; slightly above the simple-skill threshold and with no obvious content needing to be split out, so just short of 5.

4 / 5

Total

15

/

20

Passed

Description

53%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.

The description is specific to a clear niche and lists concrete APIs, but it is a noun-phrase list with no action verbs and no 'Use when...' trigger guidance. Adding an explicit trigger clause would raise both completeness and trigger-term quality.

Suggestions

Add a 'Use when ...' clause naming concrete triggers (e.g., 'Use when adding or refactoring Jotai atoms, choosing between globalAtom and contextAtom, or wiring up persistent state').

Lead with action verbs rather than a noun list (e.g., 'Create and organize Jotai atoms, choose between globalAtom and contextAtom, and configure persistence').

Include a natural synonym or file/extension cue a user might say ('state atoms', 'Jotai store') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('Jotai state management patterns') and several concrete named concepts (atoms, globalAtom, contextAtom, persistence), but presents them as a noun list with no action verbs, so it does not reach the 'several specific actions' bar of 4.

3 / 5

Completeness

It has a clear 'what' (Jotai state management patterns and the listed APIs) but no 'Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('Jotai', 'state management', 'atoms') alongside API-specific jargon (globalAtom, contextAtom), but misses common variations or synonyms; it sits at 'some relevant keywords' rather than comprehensive coverage.

3 / 5

Distinctiveness Conflict Risk

The Jotai-specific framing plus named project APIs (globalAtom, contextAtom) carves a clear niche with minimal conflict risk, though it could still lightly overlap with a generic state-management skill, keeping it just below 5.

4 / 5

Total

13

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
OneKeyHQ/app-monorepo
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.