CtrlK
BlogDocsLog inGet started
Tessl Logo

mobile-app-structure

Feature-folder layout, states/ convention, and data-flow rules for the Agenta mobile app (web/mobile). Use when creating or moving files under web/mobile, deciding where a component lives, adding a new feature or screen, or wiring data into mobile components.

77

Quality

96%

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

100%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.

An exemplary structure/convention skill: lean, concrete, and self-contained, with exact paths, explicit forbidden imports, and a sequenced checklist ending in a validation step. It assumes Claude's competence and leaves no ambiguity about how to add a feature.

DimensionReasoningScore

Conciseness

Lean and efficient: a layout tree, five terse rules, and a numbered checklist with no padding or explanation of concepts Claude already knows, so every token earns its place.

5 / 5

Actionability

Provides concrete executable guidance including exact directory paths, filenames (<X>Skeleton.tsx), forbidden imports (@agenta/oss, @agenta/ee), and concrete verification commands (pnpm --filter @agenta/mobile lint && types:check), covering the common cases.

5 / 5

Workflow Clarity

The "Adding a new feature" checklist is a clearly sequenced 1-5 process with an explicit validation checkpoint (lint + types:check) at the end, satisfying the feedback-loop requirement for create/move operations.

5 / 5

Progressive Disclosure

Under 50 lines with no bundle files, well-organized into clear sections (Layout, Rules, Adding a new feature) and inline cross-references to sibling skills; appropriately self-contained per the simple-skill exception.

5 / 5

Total

20

/

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, well-scoped description that clearly answers both what the skill governs and when to invoke it, with concrete trigger phrases anchored to a specific app directory. The only soft spot is trigger-term breadth, which relies on project vocabulary rather than synonyms or file extensions.

DimensionReasoningScore

Specificity

Names concrete capabilities ("Feature-folder layout, states/ convention, and data-flow rules") plus concrete trigger actions ("creating or moving files", "deciding where a component lives", "adding a new feature or screen", "wiring data"), giving comprehensive coverage rather than just several actions.

5 / 5

Completeness

Explicitly states both what it does (feature-folder layout, states convention, data-flow rules) and when to use it with concrete trigger phrases ("Use when creating or moving files under web/mobile, ... adding a new feature or screen, or wiring data").

5 / 5

Trigger Term Quality

Good coverage of natural phrases users would say ("creating or moving files", "adding a new feature or screen", "wiring data"), though it leans on internal vocabulary rather than the synonym/file-extension breadth the top anchor shows.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to the Agenta mobile app (web/mobile) with triggers tied to a specific app subtree, giving a clear niche with minimal conflict risk.

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.