CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

adding-workspace-apps

How to add an app to an Agent-Native workspace: classifying an "agent" request, scaffolding `apps/<app-name>`, app discovery and descriptions, mounting and base paths, action-first data, and finishing a chat-template app. Use when asked to create, build, scaffold, or generate a new agent or app in a workspace.

Quality

89%

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

82%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-crafted workflow/policy skill: highly concrete and workspace-specific, with exact commands, paths, and env vars, and a strong verify-before-reporting checkpoint guarding the main failure mode. The multi-step sequence must be inferred from topic order rather than an explicit ordered flow, and all policy content is inlined in a single file with detail delegated to sibling skills rather than bundle references.

Suggestions

Add a brief numbered workflow overview (classify the ask → scaffold with `agent-native add-app` → verify on the gateway → build out actions/UI/data → finish branding) so the execution sequence is explicit; the current topic-ordered sections leave the order to be inferred and place scaffolding/verification after the data and DB policy sections.

Trim the redundant restatement in Scaffolding — "Never report the app as created while the preview still shows something else" repeats the preceding confirm-before-reporting rule — and compress optional rationale clauses ("so the app hydrates correctly…", "since the preview root can still show a different app") to save tokens.

If the skill grows, move self-contained policy domains (Vault Access, PostgreSQL Database, discovery/manifest configuration) into one-level-deep reference files under references/ so SKILL.md stays a lean overview with clearly signaled navigation.

DimensionReasoningScore

Conciseness

The body is a dense rule-set of workspace-specific facts Claude cannot know (vault access modes, `AGENT_NATIVE_WORKSPACE_APPS_JSON`, `configureClientRouterBasename()` placement, `/_agent-native/actions/:name`) with no padding about already-known concepts. A few spots could be trimmed — "Never report the app as created while the preview still shows something else" restates the preceding confirm-before-reporting instruction, and rationale clauses like "so the app hydrates correctly when mounted at /<app-name>" are optional — matching "efficient; minor instances of over-explanation" rather than the every-token-earns-its-place top anchor.

4 / 5

Actionability

Gives copy-paste-ready specifics throughout: the exact scaffold command "`pnpm exec agent-native add-app <app-name> --template=<template>` from the workspace root", env var names, file-level detail ("`configureClientRouterBasename()` call in `app/entry.client.tsx`, before `hydrateRoot`"), hook names (`useActionQuery`/`useActionMutation`), and an executable verification step ("request `/<app-name>` on the running gateway and confirm it returns the new app"). Implementation depth is appropriately delegated to named sibling skills, matching the fully-executable anchor for an instruction-only skill.

5 / 5

Workflow Clarity

The Scaffolding section contains an explicit validation checkpoint with error recovery ("Before saying the app is created, request `/<app-name>` on the running gateway and confirm it returns the new app, not a fallback route", plus the misconfigured-host remediation naming where to set the dev command). However, the overall lifecycle (classify → scaffold → verify → build → finish) is never enumerated and must be inferred from topic-ordered sections, with scaffolding/verification appearing after the data and database policy sections — fitting "clear sequence with most checkpoints present; minor validation gaps" rather than the enumerated-checklist top anchor.

4 / 5

Progressive Disclosure

Nine well-headed sections plus a clearly signaled, one-level-deep "Related Skills" list and an inline pointer to `.agents/skills/shadcn-ui/SKILL.md` make navigation easy, and no referenced path is missing (the skill has no bundle directories). But the ~110-line body inlines several full policy domains (Vault Access, PostgreSQL Database, discovery/manifest configuration) with no internal reference split — good structure with minor organization gaps rather than the appropriately-split top anchor, and the under-50-line no-references exception does not apply.

4 / 5

Total

17

/

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 description: it enumerates the concrete lifecycle of workspace-app creation, includes an explicit "Use when" clause with natural verb synonyms, and carves out a clearly distinct niche in the Agent-Native workspace domain. The only gap is a couple of missing natural trigger synonyms ("make", "add") that the body text itself uses.

DimensionReasoningScore

Specificity

Enumerates six concrete lifecycle areas — "classifying an \"agent\" request, scaffolding `apps/<app-name>", "mounting and base paths", "action-first data, and finishing a chat-template app" — including the actual scaffold path, comprehensively covering the workflow end to end. It matches the "multiple specific concrete actions; comprehensive coverage" anchor rather than the level-below "minor gaps" anchor, since even the compressed topic labels name specific technical areas rather than vague language.

5 / 5

Completeness

Explicitly answers both: the "what" is the enumerated capability list (classifying, scaffolding, discovery, mounting, action-first data, finishing) and the "when" is a concrete trigger clause ("Use when asked to create, build, scaffold, or generate a new agent or app in a workspace"). It is not a 4 because the "when" is already explicit and specific with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"Use when asked to create, build, scaffold, or generate a new agent or app in a workspace" provides four natural verb synonyms plus the "agent"/"app" nouns, but omits common phrasings the body itself lists — "make" and "add" (the skill is named adding-workspace-apps). This fits "good keyword coverage; a few natural terms missing" rather than the comprehensive synonym coverage of the top anchor.

4 / 5

Distinctiveness Conflict Risk

Claims a clear niche — adding an app to "an Agent-Native workspace" under `apps/<app-name>` — with triggers ("new agent or app in a workspace") distinct from sibling skills' concerns (actions, UI primitives, portability), so conflict risk is minimal. It is not a 4 because the named environment and scaffold path leave little overlap with generic app-building or code skills.

5 / 5

Total

19

/

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/adding-workspace-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.