app-builder
Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.
Install with Tessl CLI
npx tessl i github:lchenrique/politron-ide --skill app-builder64
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 communicates the high-level purpose of orchestrating application creation but lacks the explicit trigger guidance essential for skill selection. It uses appropriate third-person voice and mentions key capabilities, but the absence of a 'Use when...' clause and limited natural trigger terms significantly weaken its effectiveness for Claude's skill selection process.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'when user wants to build a new app', 'create a project from scratch', 'scaffold an application', or 'start a new codebase'
Include natural user phrases and keywords such as 'build an app', 'create a website', 'new React/Node/Python project', 'start from scratch', 'generate boilerplate'
Specify concrete application types supported (web apps, APIs, CLI tools) and example tech stacks to improve specificity and distinctiveness
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (full-stack applications) and some actions (determines project type, selects tech stack, coordinates agents), but lacks concrete specifics about what types of applications, which tech stacks, or what coordination entails. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'full-stack applications' and 'natural language requests', but missing common user phrases like 'build an app', 'create a website', 'new project', 'scaffold', or specific framework names users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'orchestrator' and 'coordinates agents' provides some distinction, but 'full-stack applications' and 'natural language requests' are broad enough to potentially conflict with other code generation or project scaffolding skills. | 2 / 3 |
Total | 7 / 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, providing a well-structured orchestration overview with clear navigation to detailed resources. However, it lacks concrete executable guidance and validation checkpoints that would be critical for an application-building orchestrator handling complex multi-step processes.
Suggestions
Add concrete code or command examples for at least one template scaffolding operation (e.g., actual CLI commands to initialize a project)
Include explicit validation checkpoints in the workflow, such as 'Verify database schema before proceeding to API routes' or 'Run type-check after scaffolding'
Add error handling guidance for common failure scenarios during agent coordination (e.g., what to do if aesthetic-agent fails to generate assets)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference and avoiding unnecessary explanations. Every section serves a clear purpose without padding or explaining concepts Claude already knows. | 3 / 3 |
Actionability | Provides good structural guidance with template references and agent coordination, but lacks executable code examples. The usage example shows a process flow but not actual commands or code to execute. | 2 / 3 |
Workflow Clarity | The usage example shows a numbered sequence, but lacks explicit validation checkpoints or error recovery steps. For an orchestrator coordinating multiple agents and creating full applications, there should be verification steps between phases. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear content map table at the top, well-organized template references, and one-level-deep links to detailed files. The 'When to Read' column provides clear navigation guidance. | 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.