CtrlK
BlogDocsLog inGet started
Tessl Logo

app-builder-sdk

Build a new holaOS app using @holaboss/app-builder-sdk (5 backend primitives + optional shadcn dashboard UI). The canonical path for vibe-coded apps — integration modules AND dashboard apps both live here.

58

Quality

67%

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 ./runtime/harnesses/src/embedded-skills/app-builder-sdk/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with concrete code, commands, and well-sequenced workflows including validation feedback loops. Its weaknesses are verbosity from meta-narrative and duplication, and a monolithic structure whose referenced bundle files are not actually present.

Suggestions

Trim meta-narrative that does not guide action — keep the rule, drop the 'why this is a separate turn' rationale, the 'What this gate is NOT' bullets, and the forensic plan path reference.

Deduplicate rules restated across sections (e.g. the @holaboss/ui import guidance and the 'do not ping the upstream host' point each appear multiple times) to tighten conciseness.

Move inline detail (the ~55-primitive catalog and the full YAML/verification material) into bundled reference files so SKILL.md is an overview, and either ship the referenced reference/* and sdk-package/* files or remove the repo-root path references that the skill itself warns against.

DimensionReasoningScore

Conciseness

The technical material (primitives, slug gotchas, lint rules, YAML, verification commands) earns its place, but there is notable rationale/narrative padding — the 'why this is a separate auto-queued turn' essay, the forensic plan path 'holaOS/docs/plans/2026-05-22-...', and anti-patterns restated across multiple sections — that could be tightened; not a 1 because it does not explain concepts Claude already knows, but not a lean 3 either.

2 / 3

Actionability

Fully executable guidance throughout: complete `providerEffectAction(...)` and `getIntegrationStatus` code blocks, real `bun add`/`bun install` commands, concrete package.json/app.runtime.yaml/workspace.yaml snippets, curl binding commands, and a verification checklist with exact commands and expected outputs — copy-paste ready.

3 / 3

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints: the numbered 'Install protocol' ('Do not skip steps'), the propose_connect loop with explicit stop/wait behavior, the polish pass with a screenshot-driven rewrite→iterate feedback loop, and the verification checklist that says stop at first failure and report verbatim — including destructive-migration gating requiring user confirm + backup.

3 / 3

Progressive Disclosure

A 'Reference index (read order)' section gives well-signaled one-level-deep navigation, but the SKILL.md itself is a ~570-line monolith with full detail inline (the ~55-primitive catalog, complete YAML, duplicated anti-pattern lists) that should be split into bundled reference files; the referenced files (reference/*, sdk-package/*) are not present in the bundle, so it is not the appropriately-split 3.

2 / 3

Total

10

/

12

Passed

Description

57%

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 and clearly niche-scoped to holaOS app building, but it lacks an explicit 'Use when...' trigger clause and leans on internal jargon over natural user keywords. Completeness is capped at 2 by the missing when-guidance.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers, e.g. 'Use when the user asks to build a new holaOS app, add an integration module, or create a dashboard app', to lift completeness and trigger_term_quality.

Replace internal jargon ('vibe-coded apps', '5 backend primitives') with common user-facing variations a person would actually say ('build a holaOS app', 'add an integration', 'make a dashboard').

Add more than one concrete action verb (e.g. 'Compose, register, and deploy a new holaOS app...') so the capability list matches the score-3 specificity anchor.

DimensionReasoningScore

Specificity

It names the domain and concrete artifacts ("5 backend primitives + optional shadcn dashboard UI", "integration modules AND dashboard apps"), but the action vocabulary is essentially a single verb ("Build a new holaOS app"); the score-3 anchor expects multiple distinct action verbs like 'extract, fill, merge', so this is a strong 2 rather than a 3.

2 / 3

Completeness

The 'what' is explicit ("Build a new holaOS app using @holaboss/app-builder-sdk") but there is no 'Use when...' trigger clause in the description; per the rubric a missing explicit trigger clause caps completeness at 2, and the 'when' is only implied.

2 / 3

Trigger Term Quality

Relevant domain keywords exist ("holaOS app", "dashboard apps", "integration modules"), but several terms are internal jargon ("vibe-coded apps", "5 backend primitives") and there is no enumerated set of natural user variations like the score-3 example ('PDF files, PDFs, forms, .pdf').

2 / 3

Distinctiveness Conflict Risk

The niche is sharply bounded — building holaOS apps via one named SDK, with two distinguished shapes — so it is unlikely to trigger for unrelated skills; not the 2 anchor because it is far more specific than 'Works with document files'.

3 / 3

Total

9

/

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

skill_md_line_count

SKILL.md is long (573 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
holaboss-ai/holaOS
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.