CtrlK
BlogDocsLog inGet started
Tessl Logo

app-builder

Main application building orchestrator.

38

Quality

36%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/app-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

This skill excels at progressive disclosure and conciseness — it's a well-organized hub that efficiently directs Claude to the right resources. However, the main body lacks concrete, executable steps and validation checkpoints for the orchestration workflow itself. The usage example is illustrative but not actionable enough to guide Claude through the actual coordination process.

Suggestions

Add a concrete step-by-step orchestration workflow with explicit validation checkpoints (e.g., 'Verify tech stack compatibility before scaffolding', 'Validate generated plan before dispatching to agents').

Include at least one executable code snippet or concrete command in the main body (e.g., how to invoke an agent, how to check project detection results).

Add error handling guidance for common failure modes in the orchestration process (e.g., what to do when project type is ambiguous, when agent coordination fails).

DimensionReasoningScore

Conciseness

The content is lean and well-structured using tables for navigation. It doesn't explain what Claude already knows and every section serves a clear purpose — file map, templates, agents, and a usage example.

3 / 3

Actionability

The usage example shows a high-level process but lacks executable commands or concrete code. The skill relies heavily on external files for actual instructions, and the main body itself provides only navigation and a conceptual workflow rather than copy-paste-ready guidance.

2 / 3

Workflow Clarity

The usage example outlines a sequence (detect project type → choose stack → plan → coordinate → report → preview) but lacks validation checkpoints, error handling, or feedback loops. For an orchestrator coordinating multiple agents and destructive/generative operations, explicit validation steps are missing.

2 / 3

Progressive Disclosure

Excellent progressive disclosure with a clear content map, selective reading rule, well-organized tables pointing to one-level-deep references (6 supporting files + 13 templates), and clear signals for when to read each file.

3 / 3

Total

10

/

12

Passed

Description

0%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is critically underspecified. It provides no concrete actions, no trigger terms a user would naturally use, no 'when to use' guidance, and is so generic it would conflict with nearly any development-related skill. It reads more like an internal label than a functional skill description.

Suggestions

Specify concrete actions the skill performs, e.g., 'Scaffolds new application projects, coordinates file structure creation, sets up build configurations, and wires together frontend/backend components.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a new app, start a project from scratch, scaffold an application, or set up a full-stack project.'

Clarify the scope and boundaries to reduce conflict risk, e.g., specify which types of applications (web apps, CLI tools, mobile apps) and how this skill differs from individual component skills (frontend, backend, database setup).

DimensionReasoningScore

Specificity

The description is extremely vague — 'Main application building orchestrator' names no concrete actions. It doesn't specify what kind of applications, what 'building' entails, or what 'orchestrator' means in practice.

1 / 3

Completeness

The description barely addresses 'what' (building applications, vaguely) and completely omits 'when' — there is no 'Use when...' clause or any explicit trigger guidance.

1 / 3

Trigger Term Quality

The terms 'application building' and 'orchestrator' are generic and not natural keywords a user would say. Users are more likely to say 'create an app', 'scaffold a project', 'build a web app', etc. 'Orchestrator' is internal jargon, not a user-facing trigger term.

1 / 3

Distinctiveness Conflict Risk

'Application building' is extremely broad and could conflict with virtually any skill related to coding, project setup, frontend, backend, deployment, or scaffolding. There is nothing to distinguish this from other development-related skills.

1 / 3

Total

4

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
Dokhacgiakhoa/antigravity-ide
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.