CtrlK
BlogDocsLog inGet started
Tessl Logo

swift-actor-persistence

Swift 中使用 actor 实现的线程安全数据持久化 —— 结合内存缓存与文件存储,从设计上消除数据竞争。

56

Quality

64%

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 ./skills/swift-actor-persistence/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is highly actionable with complete, executable Swift code and clean organization, but it loses conciseness to duplicated when-to-use sections, bilingual label padding, and restated concepts, and lacks validation checkpoints for its destructive file writes.

Suggestions

Merge the overlapping '何时启用' and '适用场景' sections into a single when-to-use list to remove redundancy.

Drop bilingual parenthetical glosses and restated actor-model explanations that Claude already knows, keeping only the pattern-specific guidance.

Add a brief verify step after .atomic writes (e.g. re-read or round-trip decode) to give the persistence workflow an explicit validation checkpoint.

DimensionReasoningScore

Conciseness

Mostly efficient with complete code, but it carries redundancy: the intro repeats the frontmatter, the '何时启用' and '适用场景' sections overlap, bilingual parenthetical labels double many terms, and lines like 'Actor 模型保证了序列化访问...由编译器强制执行' restate concepts Claude already knows.

2 / 3

Actionability

Provides fully executable, copy-paste-ready Swift: a complete generic LocalRepository actor with save/delete/find/loadAll, persistence, synchronous load, plus usage and @Observable ViewModel examples.

3 / 3

Workflow Clarity

The usage section shows read/write calls clearly, but there is no explicit sequence or validation/feedback loop; the .atomic file overwrite is a destructive operation with no verify step, so it sits at anchor 2.

2 / 3

Progressive Disclosure

A single self-contained SKILL.md with no bundle files and no nested references, organized into clear sections (when to enable, core pattern, usage, design decisions, best practices, anti-patterns); per the guideline, well-organized single-file skills with no need for external references score 3.

3 / 3

Total

10

/

12

Passed

Description

57%

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 and distinct, clearly conveying a Swift actor-based persistence niche, but it answers only 'what' and omits explicit 'when to use' trigger guidance, which caps completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause naming the situations that should trigger this skill (e.g. building offline-first apps, replacing DispatchQueue-based synchronization, needing thread-safe local storage).

Enumerate concrete operations (save, delete, find, loadAll) so the description lists multiple specific actions rather than only the mechanism.

Include natural user-language variations such as 'thread-safe storage', 'actor repository', or 'eliminate data races' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain and approach ('使用 actor 实现的线程安全数据持久化', '结合内存缓存与文件存储', '消除数据竞争') but does not enumerate multiple concrete operations like save/load/delete; closer to anchor 2 than the multi-action anchor 3.

2 / 3

Completeness

It clearly answers 'what' the skill does but provides no 'when' guidance; per the guideline a missing 'Use when...' clause caps completeness at 2.

2 / 3

Trigger Term Quality

Relevant terms are present (Swift, actor, 线程安全, 数据持久化, 内存缓存, 文件存储, 数据竞争) but common variations are limited and there is no natural 'Use when...' trigger phrasing, matching anchor 2.

2 / 3

Distinctiveness Conflict Risk

'Swift actor thread-safe persistence' is a clear, narrow niche with distinct triggers that is unlikely to conflict with other skills.

3 / 3

Total

9

/

12

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
xu-xiang/everything-claude-code-zh
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.