app-builder
Main application building orchestrator.
54
Quality
36%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/app-builder/SKILL.mdQuality
Discovery
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 underdeveloped, providing almost no useful information for skill selection. It lacks specific actions, natural trigger terms, explicit usage guidance, and distinctiveness. Claude would have no reliable basis to choose this skill over others in a multi-skill environment.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Scaffolds new projects, configures build systems, sets up directory structures, integrates dependencies').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user wants to create a new app, start a project, scaffold an application, or set up a codebase').
Specify what type of applications or frameworks this covers to distinguish it from other development-related skills (e.g., 'React apps', 'Python projects', 'full-stack applications').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('orchestrator') without listing any concrete actions. It does not specify what the skill actually does beyond the generic term 'building.' | 1 / 3 |
Completeness | Missing both 'what' (no specific actions listed) and 'when' (no trigger guidance or use cases). The description fails to answer either question meaningfully. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. 'Orchestrator' is technical jargon, and 'main application building' is not how users naturally phrase requests. | 1 / 3 |
Distinctiveness Conflict Risk | 'Application building' is extremely generic and would conflict with any skill related to coding, development, project setup, or software creation. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
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 organization and token efficiency, serving as a clean orchestration hub with excellent progressive disclosure through its content map and template tables. However, it lacks concrete executable guidance for how to actually invoke agents or validate the orchestration process, making it more of a reference document than an actionable skill.
Suggestions
Add concrete commands or code for invoking each agent (e.g., how to call project-planner, what inputs it expects)
Include validation checkpoints in the workflow (e.g., 'Verify database schema before proceeding to API routes')
Add error handling guidance for common orchestration failures (e.g., agent timeout, dependency conflicts)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for quick scanning, no unnecessary explanations of concepts Claude knows. Every section serves a clear purpose with minimal prose. | 3 / 3 |
Actionability | Provides good structural guidance with clear file references and template links, but the usage example is illustrative rather than executable. No concrete commands or code snippets for actually invoking agents or running the orchestration. | 2 / 3 |
Workflow Clarity | The usage example shows a numbered process flow, but lacks explicit validation checkpoints or error handling. No feedback loops for when agent coordination fails or how to verify each step completed successfully. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear content map, one-level-deep references to specific files, and well-organized tables. The 'When to Read' column provides excellent navigation guidance for selective reading. | 3 / 3 |
Total | 10 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
3395991
- 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.