Name: app-builder
Rating: 72.39999999999999 (1 reviews)
Author: administrakt0r

app-builder

Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.

1.55x

Quality

60%

Does it follow best practices?

Impact

98%

1.55x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/app-builder/SKILL.md

Quality

Content

61%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.

The body is a well-structured, token-efficient overview that navigates to per-topic reference files and templates, but it offers no executable guidance inline and its workflow lacks validation checkpoints. Several referenced bundle files are missing, weakening the progressive-disclosure promise.

Suggestions

Add explicit validation/verification checkpoints to the multi-agent workflow (e.g. confirm the plan with the user before coordinating agents, verify each agent's output before proceeding).

Include at least one concrete executable snippet (e.g. a sample scaffolding command or plan-confirmation step) so the body is actionable without the missing reference files.

Ship the referenced bundle files (project-detection.md, tech-stack.md, agent-coordination.md, scaffolding.md, feature-building.md, templates/SKILL.md, and the templates/*/TEMPLATE.md set) so the one-level-deep references resolve.

Dimension	Reasoning	Score
Conciseness	Mostly lean table-based content that assumes Claude's competence (no explanation of Next.js, Prisma, etc.), with minor filler such as the generic 'When to Use' boilerplate that could be trimmed.	4 / 5
Actionability	The content map and usage example give clear navigational guidance and a process outline, but no executable code or commands appear in the body; the actionable detail is deferred to referenced files that are not present in the bundle.	3 / 5
Workflow Clarity	A sequenced 6-step process is shown (project type -> tech stack -> plan -> coordinate agents -> report -> preview), but there are no validation/verification checkpoints for a multi-agent batch operation, capping workflow clarity at 3.	3 / 5
Progressive Disclosure	Good structure: a content-map table, templates table, and related-agents table provide well-signaled one-level-deep references and easy navigation, but the referenced files (project-detection.md, templates/*/TEMPLATE.md, etc.) do not exist in the bundle, preventing a top score.	4 / 5
	Total	14 / 20 Passed

Description

58%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.

The description concretely names the domain and several orchestrator actions but lacks an explicit 'when to use' trigger clause and natural user phrasings, capping completeness and trigger quality. It is mostly distinct from sibling skills.

Suggestions

Add an explicit 'Use when ...' clause naming natural user triggers (e.g. 'Use when the user asks to build, create, or scaffold a full-stack app from a natural-language request').

Include natural synonyms a user would actually say ('build an app', 'make a web application', 'scaffold a project') alongside 'full-stack applications'.

Tighten 'Main application building orchestrator' framing toward the user-visible outcome so the trigger reads as something a user would naturally request.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Creates full-stack applications from natural language requests', 'Determines project type, selects tech stack, coordinates agents'), though they remain somewhat orchestrator-level rather than fully comprehensive.	4 / 5
Completeness	The 'what' is clear, but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Relevant terms like 'full-stack applications', 'tech stack', and 'agents' appear, but common natural variations a user would say ('build an app', 'make a web app') are missing.	3 / 5
Distinctiveness Conflict Risk	'Main application building orchestrator' carving a full-stack-from-natural-language niche is mostly distinct, with only minor overlap risk against related build/scaffold skills.	4 / 5
	Total	14 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 12 missing, 12 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/app-builder/SKILL.md
Commit: 57c135b

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.