Name: app-builder
Rating: 56.8 (1 reviews)
Author: boisenoise

app-builder

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

72%

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 concise, well-structured hub that routes Claude to the right reference per task, with strong progressive disclosure. Its weaknesses are missing executable detail (referenced files are not bundled) and a workflow lacking validation checkpoints for multi-agent coordination.

Suggestions

Bundle the referenced files (project-detection.md, tech-stack.md, agent-coordination.md, scaffolding.md, feature-building.md, templates/) or inline the key executable content so guidance is actionable without missing references.

Add validation/verification checkpoints to the coordination workflow (e.g. confirm the plan before dispatching agents, verify each agent's output before proceeding).

Fix the "Templates (13)" header to match the 12 listed templates, and replace the generic "When to Use" boilerplate with concrete triggering conditions.

Dimension	Reasoning	Score
Conciseness	The body is lean and table-driven (content map, templates, related agents) and assumes Claude's competence without explaining basic concepts, so nearly every token earns its place.	3 / 3
Actionability	It gives concrete routing (per-file "When to Read" column, "Read the matching template only!") and a worked example, but the executable substance lives in referenced files that are not present in the bundle, leaving guidance incomplete.	2 / 3
Workflow Clarity	The Usage Example sequences six steps (project type -> tech stack -> plan -> coordinate agents -> report -> preview), but there are no validation checkpoints or feedback loops, which matters for multi-agent batch coordination.	2 / 3
Progressive Disclosure	The overview is well organized with a clear content map, "When to Read" signals, and one-level-deep references, matching the top anchor for clear navigation and content split.	3 / 3
	Total	10 / 12 Passed

Description

60%

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 action-oriented but lacks explicit "when to use" trigger guidance and natural user keywords, capping completeness and trigger-term quality. It is distinguishable but not strongly so without clear triggers.

Suggestions

Add an explicit "Use when ..." clause naming natural user phrasings (e.g. building, scaffolding, or generating a full-stack web/mobile app from a natural language request).

Replace jargon ("orchestrator", "coordinates agents") with trigger terms users actually say, and include common variations ("build an app", "scaffold a project", "make a web app").

Tighten distinctiveness by naming the distinct scope (e.g. "from a single natural-language request") so it does not collide with narrower scaffolding skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions in third person ("Creates full-stack applications from natural language requests", "Determines project type, selects tech stack, coordinates agents"), matching the top anchor for specific concrete actions.	3 / 3
Completeness	It clearly states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	"full-stack applications from natural language requests" gives some relevant keywords, but it lacks common user-sayable variations and leans on jargon like "orchestrator" and "coordinates agents".	2 / 3
Distinctiveness Conflict Risk	"Main application building orchestrator" / "Creates full-stack applications" carves out a niche but could overlap with other app-scaffolding skills, and the absence of explicit triggers raises conflict risk.	2 / 3
	Total	9 / 12 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: boisenoise/skills-collections
Commit: f36337d

Reviewed: 2 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.