tinystruct-patterns

Expert guidance for developing with the tinystruct Java framework. Use when working on the tinystruct codebase or any project built on tinystruct — including creating Application classes, @Action-mapped routes, unit tests, ActionRegistry, HTTP/CLI dual-mode handling, the built-in HTTP server, the event system, JSON with Builder/Builders, database persistence with AbstractData, POJO generation, Server-Sent Events (SSE), file uploads, and outbound HTTP networking.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

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 content is highly actionable with executable examples and a well-structured progressive-disclosure layout backed by real reference files. The main weaknesses are minor token inefficiencies (duplicated comments, full XML snippets, a long internal source-file list) and the absence of explicit validation feedback loops for database/upload/batch operations, which caps workflow clarity at 2.

Suggestions

Remove the duplicate '// Broadcast to all' line and consider trimming the MCP Maven <dependency> block to just the version note, since the version is the only time-sensitive detail.

Add an explicit validation/checkpoint step to the database and file-upload workflows (e.g., verify persisted records or uploaded file integrity before proceeding) to lift workflow clarity to 3.

Trim or collapse the 'Reference Source Files (Internal)' list — these are discoverable in the repo and add token weight without proportional guidance value.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient and avoids explaining concepts Claude already knows, but several parts could be tightened: the duplicate '// Broadcast to all' line, the full MCP Maven dependency block, and the extensive 'Reference Source Files (Internal)' list inflate the token budget without proportionate value. It is mostly efficient but includes some unnecessary bulk, matching the score-2 anchor.	2 / 3
Actionability	The body provides fully executable, copy-paste-ready Java code across multiple concrete scenarios (basic application, login mode disambiguation, JSON with Builder/Builders, SSE, file upload, MCP tool/server), plus exact dispatcher commands and config snippets. This matches the score-3 'fully executable code/commands; specific examples; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Multi-step processes (MCP tool creation, server deployment) are listed as numbered steps with a clear sequence, and the Red Flags table functions as a troubleshooting checklist. However, operations involving database writes, file uploads, and batch/persistence changes lack explicit validation-checkpoint feedback loops (validate -> fix -> retry), which the rubric notes should cap workflow_clarity at 2 for such contexts.	2 / 3
Progressive Disclosure	The SKILL.md body is a concise overview that points one level deep to six real, well-signaled reference files in the 'Technical Reference' section (architecture.md, routing.md, data-handling.md, database.md, system-usage.md, testing.md — all verified to exist). Content is appropriately split between the overview and references with clear navigation, matching the score-3 anchor.	3 / 3
	Total	10 / 12 Passed

Description

100%

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 strong across all dimensions: it is specific, uses third-person voice, includes an explicit 'Use when' trigger clause, and is tightly scoped to the tinystruct framework. It reads like the rubric's good examples and shows no fluff or first/second-person voice penalties.

Dimension	Reasoning	Score
Specificity	The description lists numerous concrete actions — 'creating Application classes, @Action-mapped routes, unit tests, ActionRegistry, HTTP/CLI dual-mode handling, the built-in HTTP server, the event system, JSON with Builder/Builders, database persistence with AbstractData, POJO generation' — matching the rubric's 'multiple specific concrete actions' anchor; it goes beyond naming a domain.	3 / 3
Completeness	It explicitly states what the skill does ('Expert guidance for developing with the tinystruct Java framework') and when to use it with an explicit trigger clause ('Use when working on the tinystruct codebase or any project built on tinystruct — including...'). Both 'what' and 'when' are clearly answered with explicit triggers, matching the score-3 anchor.	3 / 3
Trigger Term Quality	Natural terms a user would say are well covered — 'tinystruct', '@Action-mapped routes', 'unit tests', 'database persistence', 'file uploads', 'Server-Sent Events (SSE)', 'outbound HTTP networking'. A developer working on a tinystruct codebase would naturally mention these; coverage is broad, not just jargon.	3 / 3
Distinctiveness Conflict Risk	The skill targets a very specific niche — the tinystruct Java framework — and all triggers are scoped to that framework, making it unlikely to fire for unrelated skills. The highly framework-specific terminology gives it a clear, distinct niche per the score-3 anchor.	3 / 3
	Total	12 / 12 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Commit: 754b8dd

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