CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

akka-hosting-actor-patterns

Patterns for building entity actors with Akka.Hosting - GenericChildPerEntityParent, message extractors, cluster sharding abstraction, akka-reminders, and ITimeProvider. Supports both local testing and clustered production modes.

Quality

76%

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/akka-hosting-actor-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 highly actionable pattern catalog with complete, copy-paste-ready code and well-organized sections, weakened only by missing validation checkpoints and a fully inlined structure with some duplicated DI/marker-type content. It teaches non-obvious, project-specific patterns without padding.

Suggestions

Add explicit verification steps, e.g. after registering actors: 'Run a LocalTest-mode smoke test (Tell a test message, assert the reply) before enabling clustered mode.'

Split reference-grade sections (RememberEntities configuration, DI scope management) into references/ files and keep SKILL.md as an overview with clearly signaled links.

Remove the duplicated scope-per-message code (the GOOD example in 'Common Mistake' repeats 'Pattern: Scope Per Message') by showing only the contrasting BAD snippet and pointing back to the full pattern.

DimensionReasoningScore

Conciseness

The body is code-first and assumes Akka competence (no 'what is an actor' padding), and each section delivers patterns rather than concept explanations. It falls short of 5 due to duplicated material: the scope-per-message DI pattern is fully coded twice ('Pattern: Scope Per Message' and the GOOD example under 'Common Mistake'), and marker-type registration is covered in two separate sections.

4 / 5

Actionability

Nearly every section contains complete, executable C# (GenericChildPerEntityParent, OrderMessageExtractor, WithOrderActor/WithShardRegion extensions, Postgres and in-memory reminder configs, DI scope code). The examples are copy-paste ready and cover the common cases (LocalTest vs Clustered, durable vs test storage).

5 / 5

Workflow Clarity

Sections follow a logical build order (execution mode enum -> parent actor -> extractor -> hosting extension -> composition) and decision tables guide choices (e.g., the RememberEntities entity-type table), but there are no explicit validation or verification checkpoints (no 'verify registration' or 'smoke-test in LocalTest mode first' steps). Checkpoints are absent, not merely gapped, so it cannot reach 4.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so the entire ~610-line catalog is inlined in SKILL.md. Section headers make it navigable, but reference-grade material (RememberEntities configuration tables, DI scope management) would serve better in split-out files, and the lone external pointer ('see `microsoft-extensions/dependency-injection` skill') is plain text rather than a clearly signaled link.

3 / 5

Total

15

/

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 distinctive, specific description that clearly communicates the skill's niche (Akka.Hosting entity actor patterns) with strong trigger terms, but it lacks any 'Use when...' trigger guidance, capping completeness. Adding an explicit usage clause would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building entity actors in Akka.NET, configuring cluster sharding, or setting up akka-reminders scheduled tasks.'

Lead with concrete action verbs ('Build', 'Configure', 'Register') instead of relying on component names to imply capabilities.

Include common synonyms such as 'Akka.NET', 'shard region', and 'scheduled messages/timers' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Patterns for building entity actors with Akka.Hosting - GenericChildPerEntityParent, message extractors, cluster sharding abstraction, akka-reminders, and ITimeProvider" lists several specific concrete capabilities with comprehensive coverage of the skill's scope. It stops short of a 5 because it names components rather than explicit parallel actions ('building', 'Supports' are the only verbs).

4 / 5

Completeness

The 'what' is clear and concrete (patterns and named components for entity actors), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

Natural domain terms users would say are present: 'entity actors', 'Akka.Hosting', 'cluster sharding', 'akka-reminders', 'local testing', 'clustered production'. Missing common variations and synonyms like 'Akka.NET', 'shard region', or general scheduling terms, so it falls just short of comprehensive (5).

4 / 5

Distinctiveness Conflict Risk

Highly specific terms like 'GenericChildPerEntityParent', 'akka-reminders', and 'ITimeProvider' establish a clear niche with minimal overlap risk against any other skill. Voice is third person ('Supports both local testing and clustered production modes'), so no person-violation penalty applies.

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

skill_md_line_count

SKILL.md is long (615 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

Aaronontheweb/dotnet-skills

Path

skills/akka-hosting-actor-patterns/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.