CtrlK
BlogDocsLog inGet started
Tessl Logo

putio/frontend-patterns

Apply put.io frontend code patterns and seed repo-local `.patterns/` conventions. Use when writing or reviewing UI/frontend code in a put.io frontend repo, picking the default approach for types, data parsing, state machines, error handling, components, or testing, or seeding/extending the repo's `.patterns/` folder. Skip repo shape, top-level docs, delivery, CI, proof harness work, and SDK package patterns.

85

3.16x
Quality

91%

Does it follow best practices?

Impact

95%

3.16x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, action-oriented, and well-structured with executable examples and a clear workflow. Its weaknesses are a missing explicit verify-failure feedback loop in the workflow and referenced reference files that do not exist in the bundle.

Suggestions

Add an explicit feedback loop to the Workflow (e.g. step 5: 'If verify fails, fix the issue and re-run verify before proceeding') to reach the top workflow-clarity anchor.

Ship the referenced ./references/frontend-defaults.md and ./references/pattern-template.md files, or remove the links, so progressive-disclosure navigation is not broken.

Consider a short validation note in step 4/5 describing what a passing 'verify' looks like, so the checkpoint is unambiguous.

DimensionReasoningScore

Conciseness

Lean and directive throughout — Quick Rules are dense one-liners, the workflow is a tight 6-step list, and code examples show patterns without explaining concepts Claude already knows. Every section earns its place.

3 / 3

Actionability

Provides fully executable TypeScript/TSX code blocks (Effect Schema parse-at-boundary, a discriminated-union TransferStatus rendered with Match.exhaustive) plus concrete file-naming and sectioning rules for .patterns/ entries.

3 / 3

Workflow Clarity

The 6-step Workflow is clearly sequenced and includes a validation checkpoint ('Run the repo's verify command'), but it lacks an explicit validate→fix→retry feedback loop if verification fails, keeping it below the top anchor.

2 / 3

Progressive Disclosure

The body is well-sectioned and signals one-level-deep references to ./references/frontend-defaults.md and ./references/pattern-template.md, but those reference files are not present in the bundle, so the navigation is broken rather than complete.

2 / 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 specific, action-oriented, and uses third-person imperative voice with an explicit Use-when trigger and explicit skip/sibling-skill routing. It cleanly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Apply put.io frontend code patterns', 'seed repo-local .patterns/ conventions', 'picking the default approach for types, data parsing, state machines, error handling, components, or testing', and 'seeding/extending the repo's .patterns/ folder'.

3 / 3

Completeness

Explicitly answers what ('Apply put.io frontend code patterns and seed repo-local .patterns/ conventions') and when ('Use when writing or reviewing UI/frontend code...') with an explicit Use-when trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms a frontend developer in a put.io repo would say — 'writing or reviewing UI/frontend code', 'types, data parsing, state machines, error handling, components, or testing', '.patterns/ folder'.

3 / 3

Distinctiveness Conflict Risk

Clear niche reinforced by an explicit 'Skip for...' clause naming sibling skills putio-frontend-repos and putio-sdk-dev, making overlap with other skills unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 7 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents