CtrlK
BlogDocsLog inGet started
Tessl Logo

agenta-package-practices

Where to put frontend code (package vs app layer) and how to use the @agenta/* packages. Use when authoring or moving code in web/packages, choosing between @agenta/ui, @agenta/entities, @agenta/entity-ui, @agenta/shared, @agenta/playground, using molecules, loadable/runnable bridges, the EntityPicker, or writing package unit tests.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable, well-structured reference with real code examples and explicit build/lint validation. Its main weakness is redundancy: package purposes and the subpath import catalog are repeated across several sections.

Suggestions

Consolidate the package-purpose listings that recur in the Quick heuristic tree, Package overview table, Subpath imports, and Package selection guide into one canonical reference to remove redundancy.

Move the full subpath import catalog into a separate reference file and keep only one representative import example per package inline in SKILL.md.

Trim the per-section restatements of each package's role; point back to the README table once instead of repeating it under each pattern section.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code, but package purposes are restated across four sections (Quick heuristic tree, Package overview table, Subpath imports, Package selection guide) and the inline subpath import catalog is bulky, so it could be tightened.

3 / 5

Actionability

Copy-paste-ready import statements and complete executable examples for EnhancedModal, molecule controllers, loadable/runnable bridges, EntityPicker variants, vitest config, and Fern mocking cover the common cases.

5 / 5

Workflow Clarity

A clear placement decision tree plus an explicit validation checkpoint ("Verify your change builds AND lints before pushing: pnpm turbo run build --filter=... and ... lint --filter=...") sequence the work, with only minor gaps.

4 / 5

Progressive Disclosure

Well-signaled one-level-deep references ("Full documentation: web/packages/.../README.md", AGENTS.md contract, reference test files) and clean section headers, though the extensive inline subpath catalog could live in a reference file.

4 / 5

Total

16

/

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 tight, well-targeted description that states both capability and explicit trigger conditions with concrete, codebase-specific terms. It avoids fluff and over-claiming while remaining comprehensive.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "authoring or moving code in web/packages", "choosing between @agenta/ui, @agenta/entities...", "using molecules, loadable/runnable bridges, the EntityPicker", and "writing package unit tests" — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both what ("Where to put frontend code... and how to use the @agenta/* packages") and when ("Use when authoring or moving code... or writing package unit tests") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong, domain-specific keywords users in this codebase would say ("package unit tests", "EntityPicker", "molecules", "web/packages") with all package variants listed, but the terms lean technical and a few natural phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (@agenta/* workspace packages, web/packages, molecules/bridges/EntityPicker) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Agenta-AI/agenta
Reviewed

Table of Contents

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.