CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

composable-mini-apps

Build focused workspace apps and cross-app workflows, using A2A only when a task needs a peer-owned capability. Use when designing mini-app boundaries.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/composable-mini-apps/SKILL.md
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.

The body is an efficient, highly actionable architecture policy: concrete tool invocations, an explicit artifact contract, clear delegation criteria, and a worked multi-app example. All dimensions land at 4 — kept from 5 by a duplicated boundary rule, the absence of failure/recovery guidance, and inlined detail that could live in a reference file.

Suggestions

Merge the near-verbatim peer-exclusivity statements in Rule and Discovery And Invocation into a single canonical statement to reclaim tokens.

Add brief failure guidance for cross-app calls (e.g. what to do when a sibling's invocation fails or times out) to strengthen the workflow's feedback loop.

If the skill grows, move the artifact field schema and the discovery-tool semantics into a one-level-deep reference file, keeping SKILL.md as the overview.

DimensionReasoningScore

Conciseness

Dense, policy-grade prose that assumes Claude's competence — e.g. "Keep provider credentials and upstream API details in the app that owns that provider or workflow" — with no explanations of known concepts. It falls short of anchor 5 only because the peer-exclusivity rule is stated nearly verbatim twice ("A peer's availability or ability to enrich the result is not enough" in Rule vs. "A sibling's availability or ability to enrich the result is not enough" in Discovery And Invocation).

4 / 5

Actionability

Gives concrete tool names and call patterns throughout — "pass `app: \"<id>\"`", "GET /_agent-native/agents?selfAppId=<app-id>", "invokeAgent() / agent-native invoke", "provider-api-catalog ... provider-api-request" — plus a complete artifact field schema and a worked example with real artifact ids. It is anchor 4 rather than 5 because some guidance stays at policy level ("Give each mini-app one clear job") and there are no copy-paste snippets covering common cases.

4 / 5

Workflow Clarity

The decision flow is well sequenced — discover siblings via <available-apps>, use describe-workspace-apps only under explicitly stated conditions, invoke with narrow prompts, then hand off compact artifacts — and the Example section traces the full chain end to end. It is anchor 4 rather than 5 because there are no validation or recovery checkpoints (e.g. what to do when a peer call fails); no destructive or batch operations exist, so the workflow-clarity cap does not apply.

4 / 5

Progressive Disclosure

A single-file skill (no references/, scripts/, or assets/ bundle exists) with clean section headers, a summary table, and a well-signaled Related Skills section — easy to navigate with nothing buried or nested. It is anchor 4 rather than 5 because at ~140 lines, detailed material like the discovery tool semantics and the artifact field schema is inlined where a one-level-deep reference file could carry it, and Related Skills entries are bare names rather than links.

4 / 5

Total

16

/

20

Passed

Description

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

The description answers both 'what' and 'when' with a clear, third-person statement and an explicit trigger clause, and its niche is mostly distinct. Its main weaknesses are limited action coverage and trigger keywords missing common variations, which leave specificity and trigger-term quality at the midpoint.

Suggestions

Broaden the 'Use when' clause with concrete trigger variations, e.g. "Use when designing mini-app boundaries, splitting a workspace into focused apps, deciding whether to call a sibling app, or composing cross-app workflows with A2A."

Add one or two more concrete capabilities to the 'what', such as deciding app ownership boundaries, delegating peer-owned provider calls, and handing off compact artifacts between apps.

Include natural synonyms users would actually say (mini-apps, focused apps, app splitting, agent-to-agent calls) so the skill triggers on phrasing beyond "mini-app boundaries".

DimensionReasoningScore

Specificity

Names the domain ("focused workspace apps and cross-app workflows", "A2A") and 1-2 concrete actions (build apps, build workflows, use A2A selectively), but coverage is not comprehensive — delegation criteria, artifact handoff, and app-boundary decisions are absent. It is above anchor 2 because the actions are not generic, but below anchor 4 because only a couple of specific actions are listed.

3 / 5

Completeness

Has a clear 'what' ("Build focused workspace apps and cross-app workflows, using A2A only when a task needs a peer-owned capability") and an explicit 'when' ("Use when designing mini-app boundaries"), so it clears the missing-'Use when' cap. Not 5 because the 'when' clause is a single narrow trigger and lacks concrete multi-phrase triggers like the anchor-5 example.

4 / 5

Trigger Term Quality

Relevant keywords like "workspace apps", "cross-app workflows", "A2A", and "mini-app boundaries" are present, but common variations users might say are missing (e.g. "splitting an app", "app decomposition", "when to call a sibling app", "agent-to-agent"). Fits anchor 3 better than 4 because keyword coverage is partial rather than good-with-a-few-gaps.

3 / 5

Distinctiveness Conflict Risk

The A2A/peer-owned-capability/mini-app niche is fairly distinct with clear triggers, but there is minor overlap risk with the closely related a2a-protocol skill, which covers how apps expose and call A2A endpoints. Fits anchor 4 ("Mostly distinct; minor overlap risk with closely related skills"), not 5 ("Clear niche with distinct triggers") given that adjacency.

4 / 5

Total

14

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BuilderIO/agent-native

Path

.agents/skills/composable-mini-apps/SKILL.md

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.