Name: robius-state-management
Rating: 55.2 (1 reviews)
Author: administrakt0r

robius-state-management

CRITICAL: Use for Robius state management patterns. Triggers on: AppState, persistence, theme switch, 状态管理, Scope::with_data, save state, load state, serde, 状态持久化, 主题切换

Quality

63%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/robius-state-management/SKILL.md

The canonical home for this skill is robius-state-management in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

57%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 body is a rich, actionable catalog of real Robius/Moly state-management code with sensible sections, but it is longer than necessary, lacks explicit validation checkpoints in its persistence workflow, and advertises reference files that are absent from the bundle.

Suggestions

Move the full AppState/SelectedRoom and persistence-layer code listings into the referenced references/*.md files (and actually include those files) so SKILL.md stays a lean overview.

Add an explicit validation checkpoint to the persistence workflow (e.g., 'After save, reload and deserialize to confirm the file round-trips before considering state persisted').

Tighten inlined impls to the minimal illustrative snippet and define or stub the referenced undefined types (RoomNameId, WindowGeomState) so examples are self-contained.

Dimension	Reasoning	Score
Conciseness	The body is code-heavy with minimal prose padding and little explanation of concepts Claude already knows, but it inlines many full implementations (entire AppState/SelectedRoom impls, save/load/window-geom blocks) that could be condensed or moved to references.	3 / 5
Actionability	It supplies extensive concrete, largely copy-paste-ready Rust for state structs, Scope propagation, and the persistence layer; minor gaps exist where referenced types (RoomNameId, WindowGeomState, CachedData) are used but not defined.	4 / 5
Workflow Clarity	The save/load/startup/shutdown lifecycle is sequenced with error handling and a graceful deserialization fallback, but there is no explicit validation checkpoint or validate->fix->retry loop for the state-overwrite operations, which the rubric caps at 3 for destructive/batch-style work.	3 / 5
Progressive Disclosure	Sections are organized and a 'Reference Files' list plus a '_base/' pattern table signal one-level-deep navigation, but the referenced references/*.md and _base/ paths do not exist in the bundle, and the bulk of the patterns remain inlined rather than split out.	3 / 5
	Total	13 / 20 Passed

Description

70%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 a compact, bilingual trigger-heavy declaration that clearly signals its Robius niche and when to fire. Its main weakness is that it leans on trigger keywords rather than stating concrete capabilities, leaving the 'what' somewhat thin.

Suggestions

Lead with 2-3 concrete capabilities (e.g., 'Design AppState structs, implement serde persistence, propagate state via Scope') before the trigger list to strengthen the 'what'.

Trim the most technical jargon ('Scope::with_data', 'serde') from the user-facing trigger line or pair it with a natural-language synonym so non-expert phrasing also matches.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Robius state management patterns') and a few concrete items ('save state', 'load state', 'theme switch', 'persistence') but does not enumerate a comprehensive set of concrete actions, listing triggers instead of capabilities.	3 / 5
Completeness	Both 'what' ('Use for Robius state management patterns') and 'when' ('Triggers on: ...') are present, with the 'when' made explicit via a concrete trigger list; the 'what' is somewhat thin (no enumerated actions) which keeps it just below a 5.	4 / 5
Trigger Term Quality	It provides good keyword coverage including natural phrases ('save state', 'load state', 'persistence', 'theme switch') plus bilingual synonyms ('状态管理', '主题切换'), though some terms like 'Scope::with_data' and 'serde' are technical jargon a user may not naturally say.	4 / 5
Distinctiveness Conflict Risk	The Robius framing plus Robius-specific triggers ('AppState', 'Scope::with_data') carve a clear niche with minimal conflict risk, though generic terms like 'persistence' and 'save state' leave minor overlap with general state-management skills.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/robius-state-management/SKILL.md
Commit: 57c135b

Reviewed: 2 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.