CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

swift-actor-persistence

Thread-safe data persistence in Swift using actors — in-memory cache with file-backed storage, eliminating data races by design.

Quality

80%

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

Quality

Content

82%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 strong, code-first skill: the core pattern is fully executable with concrete usage and design rationale, and structure is clear throughout. The main weaknesses are redundant overlapping sections ('When to Activate' vs 'When to Use', best practices vs the design-decisions table) that could be consolidated.

DimensionReasoningScore

Conciseness

Largely lean and code-first, but 'When to Activate' and 'When to Use' are redundant duplicate sections, and 'The actor model guarantees serialized access — no data races, enforced by the compiler' restates the description — minor trims available, matching anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Fully executable, copy-paste-ready Swift: a complete generic actor repository with save/delete/find/loadAll, concrete usage calls, and an @Observable ViewModel integration covering the common case, matching anchor 5.

5 / 5

Workflow Clarity

As a pattern skill there is no multi-step workflow to sequence, and the guidance is unambiguous with complete code and no destructive/batch operations needing validation; the duplicated when-to-use sections and lack of any ordering guidance keep it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

A single-file skill with no bundle files and well-organized sections (core pattern, usage, design decisions, best practices, anti-patterns) and no external references; at ~140 lines it exceeds the under-50-line simple-skill threshold, so well-organized inline content earns anchor 4 rather than an automatic 5.

4 / 5

Total

17

/

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.

A specific, well-targeted description with a clear niche, but it lacks any 'when to use' trigger guidance, which caps its completeness and limits its discoverability. Adding an explicit activation clause would resolve the main weakness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when building a persistence layer in Swift with async/await, or when replacing DispatchQueue/NSLock-based thread safety with Swift actors.'

Phrase capabilities as concrete actions users would recognize (e.g. 'saves, deletes, and queries Codable models') rather than only architectural features like 'in-memory cache with file-backed storage'.

Include natural synonyms users might say — 'Swift concurrency', 'async/await', 'locking', 'thread safety' — to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names several concrete capabilities — 'in-memory cache', 'file-backed storage', 'eliminating data races' — alongside a clear domain (Swift actors), though capabilities are stated as architecture features rather than actions (no save/load/encode verbs), keeping it below anchor 5.

4 / 5

Completeness

The 'what' is clear and specific, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'Swift', 'actors', 'thread-safe', 'data persistence', 'data races' are natural phrases users would say in this domain, but common variations like 'Swift concurrency', 'async/await', or 'locking' are missing, matching anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Swift using actors' carves out a clear niche with distinct triggers (actor model, data races, Swift concurrency) and minimal overlap risk with general persistence or database skills, matching anchor 5.

5 / 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

affaan-m/ECC

Path

.kiro/skills/swift-actor-persistence/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.