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

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

86%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 well-structured, highly actionable skill body with executable examples and excellent progressive disclosure through real reference files. Minor conciseness blemishes and missing validation checkpoints in a couple of workflows keep it just short of perfect.

Suggestions

Remove the duplicated '// Broadcast to all' comment (lines 108-109) and reconcile the two @Action("greet") methods in the basic example so it does not read as a copy-paste error.

Add a short '### When NOT to use' subsection under 'When to Activate' to fulfill the implied pairing and tighten trigger guidance.

Add an explicit validation/verification checkpoint to the MCP server deploy flow (e.g., confirm the server responds or tools are registered before declaring success).

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence, but contains minor padding such as a duplicated '// Broadcast to all' comment and a confusing duplicate @Action("greet") example in a single class that could be tightened.	4 / 5
Actionability	Fully executable, copy-paste-ready Java across all examples with imports, concrete annotations, and even input validation/sanitization logic in the MCP tool example.	5 / 5
Workflow Clarity	Clear sequenced guidance for MCP tool/server creation and config, but the deploy and routing flows lack explicit validation checkpoints, and the '### When to Use' heading dangles without a counterpart 'When NOT to use' subsection.	4 / 5
Progressive Disclosure	Body is a concise overview with six real, well-signaled, one-level-deep reference files (architecture.md, routing.md, data-handling.md, database.md, system-usage.md, testing.md) verified present in references/, plus organized internal source-file pointers.	5 / 5
	Total	18 / 20 Passed

Description

92%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 strong, specific description that clearly states both what the skill covers and when to use it, with comprehensive capability enumeration and a tight niche that minimizes conflict risk. The only minor gap is reliance on framework jargon over plain-language synonyms in trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'creating Application classes, @Action-mapped routes, unit tests, ActionRegistry, HTTP/CLI dual-mode handling... Server-Sent Events (SSE), file uploads, and outbound HTTP networking' — giving comprehensive coverage of the framework's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (expert guidance for developing with the tinystruct Java framework) and 'when' ('Use when working on the tinystruct codebase or any project built on tinystruct') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes a natural trigger phrase ('Use when working on the tinystruct codebase or any project built on tinystruct') with good coverage, but leans heavily on framework jargon (@Action, AbstractData, Builder/Builders) rather than the synonyms/variations a non-expert user might naturally say.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to the tinystruct framework with a clear niche and framework-specific triggers, making conflict with unrelated skills minimal.	5 / 5
	Total	19 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/tinystruct-patterns/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.