prismarine-skill

Development guide for using the Prismarine DynamoDB ORM. Use when defining DynamoDB models, generating client code, or performing database operations using Prismarine.

Quality

93%

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

Quality

Content

87%Weight 40%Scale 1-3

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 concise, actionable overview that delegates detail to real one-level-deep reference files. Its main weakness is the lack of validation/verification checkpoints in the workflow, which is notable given the destructive database operations it covers.

Suggestions

Add a validation/verification step to the Core Workflow (e.g., confirm the generated client imports cleanly or that a model round-trips via put/get) before declaring the workflow complete, since put/update/delete are destructive DynamoDB operations.

Link references/cli-usage.md from the Client Generation section so the full CLI reference is discoverable, matching the pattern used for the other reference files.

Replace the placeholder decorator example (@c.model(PK='...', SK='...')) with a minimal concrete model class to make the Model Definition section as copy-paste-ready as the CRUD and CLI examples.

Dimension	Reasoning	Score
Conciseness	The body is lean and dominated by actionable code/commands; the few one-line context sentences ("Models define the schema and keys...", "The generated client provides a high-level API...") are brief and do not pad with concepts at length, matching the lean-and-efficient anchor.	3 / 3
Actionability	Provides a copy-paste-ready CLI command ("uv run prismarine generate-client common --base . --model-library pydantic") and concrete CRUD code ("TeamModel.put(...)", "TeamModel.get(...)") with specific file names; not score 2 because the primary examples are executable rather than pseudocode.	3 / 3
Workflow Clarity	The Core Workflow lists a clear sequence (Define Models → Generate Client → Extend/Use) but includes no validation or verification checkpoints for destructive database operations (put/update/delete), which the rubric caps at 2; not score 3 because feedback loops are absent, and not score 1 because the sequence is explicit.	2 / 3
Progressive Disclosure	A clear overview links to one-level-deep, well-signaled references ([model-definition.md], [crud-api.md], [easysam.md]) that all exist in references/, with detail appropriately split out; not score 2 because references are clearly signaled and content is well split rather than inlined.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 concise, third-person, and explicitly covers both what the skill does and when to use it with multiple concrete trigger phrases. It is clearly distinct to the Prismarine niche and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "defining DynamoDB models", "generating client code", and "performing database operations" — matching the multiple-specific-actions anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly states what ("Development guide for using the Prismarine DynamoDB ORM") and when ("Use when defining DynamoDB models, generating client code, or performing database operations"), satisfying both halves with an explicit trigger clause; not capped at 2 because the "Use when..." clause is present.	3 / 3
Trigger Term Quality	Natural trigger phrases a user would say ("DynamoDB models", "client code", "database operations", "Prismarine") give good coverage; not score 2 because common variations of when-to-use are present rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	Tied to a named niche tool ("Prismarine DynamoDB ORM") with distinct triggers, making conflict with generic skills unlikely; not score 2 because the niche is clearly delimited rather than broadly overlapping.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: scartill/easysam-skills
Path: skills/prismarine-skill/SKILL.md
Commit: b2bd8e2

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