Name: scala-pro
Rating: 36.8 (1 reviews)
Author: administrakt0r

scala-pro

Master enterprise-grade Scala development with functional programming, distributed systems, and big data processing. Expert in Apache Pekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures.

Quality

33%

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/scala-pro/SKILL.md

The canonical home for this skill is scala-pro in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

17%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 functions as a resume of Scala expertise rather than an actionable skill: it describes capabilities Claude already knows, provides no code or commands, lacks a real workflow with validation, and references a playbook file that is mis-pathed and absent. It adds little that Claude cannot already supply.

Suggestions

Replace the expertise enumeration with concrete, executable guidance — code patterns, command snippets, and decision rules for the tasks the skill is meant to perform.

Add a real multi-step workflow with explicit validation checkpoints for the risky operations in scope (e.g., Akka-to-Pekko migration, Spark pipeline changes).

Move the bulk reference material into actual bundle files under references/ and link them with correct paths, keeping SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is a lengthy enumeration of expertise areas Claude already knows (type classes, monads, circuit breakers, GC tuning, event sourcing) stated as descriptive bullets, delivering low value per token despite not padding with concept tutorials.	2 / 5
Actionability	No code, commands, or executable guidance appear anywhere; the content only describes capabilities ("Deep understanding of...", "Mastery of...", "Experience with...") rather than instructing how to do anything.	1 / 5
Workflow Clarity	Only a rough, high-level pseudo-process is given ("Clarify goals, constraints... Apply relevant best practices... validate outcomes") with no concrete sequence, no checkpoints, and no validation steps for risky operations.	2 / 5
Progressive Disclosure	The body is a monolithic inline dump of reference-style expertise that belongs in separate files, and the sole referenced file (`resources/implementation-playbook.md`) uses a wrong path and does not exist among the bundle files.	2 / 5
	Total	7 / 20 Passed

Description

50%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 conveys a clear domain and notable technology names but reads as an expertise claim rather than a statement of concrete actions, and it omits any "Use when..." trigger guidance. It is moderately specific and distinct but not comprehensive.

Suggestions

Reframe the description around concrete actions the skill performs (e.g., 'Designs and implements', 'Migrates Akka to Pekko') rather than mastery claims.

Add an explicit 'Use when...' clause naming the natural trigger phrases users would say (e.g., 'Use when building or migrating Scala distributed systems, Akka/Pekko actor systems, or Spark data pipelines').

Include synonyms and file/extension cues (e.g., 'Scala 3', '.scala', 'sbt build') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("enterprise-grade Scala development", "functional programming", "distributed systems", "big data processing") and specific technologies ("Apache Pekko, Akka, Spark, ZIO/Cats Effect"), but lists expertise/areas rather than concrete actions the skill performs.	3 / 5
Completeness	Provides a clear "what" (enterprise Scala mastery across FP, distributed systems, big data) but has no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes natural terms users say ("Scala development", "functional programming", "distributed systems", "big data processing", "Akka", "Spark", "ZIO"), but lacks synonyms, file extensions, and common variations such as "Scala 3".	3 / 5
Distinctiveness Conflict Risk	The enterprise-Scala niche is somewhat specific and lists distinct technologies, but the broad domain overlaps with general Scala and coding skills, and without explicit trigger phrases it could still fire for the wrong skill.	3 / 5
	Total	12 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/scala-pro/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.