appfactory-builder
Build and deploy production apps using AppFactory's 7 pipelines (websites, mobile, dApps, AI agents, plugins, mini apps, bots). One prompt → live URL.
61
51%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xaxiom/appfactory/appfactory-builder/SKILL.mdQuality
Discovery
67%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 strong on specificity and distinctiveness, clearly naming the tool (AppFactory), its 7 pipeline types, and the concrete outcome (live URL from one prompt). However, it lacks an explicit 'Use when...' clause, which caps completeness, and some trigger terms could be more aligned with natural user language.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to build, deploy, or launch a website, mobile app, bot, plugin, AI agent, dApp, or mini app using AppFactory.'
Include more natural user-facing trigger terms such as 'web app', 'build a site', 'launch an app', 'deploy to production', or 'generate a live URL'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and outputs: 'Build and deploy production apps' across 7 named pipeline types (websites, mobile, dApps, AI agents, plugins, mini apps, bots), with a concrete outcome ('One prompt → live URL'). | 3 / 3 |
Completeness | Clearly answers 'what does this do' (build and deploy apps via AppFactory's 7 pipelines), but there is no explicit 'Use when...' clause or equivalent trigger guidance telling Claude when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes several natural keywords like 'websites', 'mobile', 'dApps', 'AI agents', 'plugins', 'bots', and 'deploy', but misses common user phrasings like 'web app', 'build a site', 'launch', 'host', or 'AppFactory' as an explicit trigger. Some terms like 'mini apps' and 'dApps' are niche and may not match typical user language. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'AppFactory's 7 pipelines' and the specific list of pipeline types (dApps, mini apps, bots, etc.) creates a clear niche that is unlikely to conflict with generic coding or deployment skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a project README than an actionable skill for Claude. It contains significant promotional content (token links, social media, showcase submissions), verbose pipeline descriptions that repeat the summary table, and contributing guidelines that are irrelevant to building apps. The core actionable content — clone, scaffold, deploy — is buried among unnecessary sections and lacks validation steps or error handling.
Suggestions
Remove all promotional content (token links, social media, contributing guidelines, OpenClaw heartbeat section) — these don't help Claude build apps and waste significant token budget.
Integrate the LOCAL_RUN_PROOF_GATE and Ralph QA validation into the actual workflow steps rather than just mentioning them in the architecture section — e.g., 'After build, verify: npm run build && npm start, then deploy only if successful.'
For each pipeline beyond websites, provide at least one concrete executable command sequence instead of just 'Follow CLAUDE.md' — or consolidate the skill to focus only on the website pipeline with clear references to other pipeline CLAUDE.md files.
Remove the 'Pipeline Details' section which largely repeats the summary table, and instead use that space for concrete examples of prompts and expected outputs for each pipeline type.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines. It includes extensive sections on contributing back, reporting issues, architecture details, OpenClaw agent heartbeat tasks, token launchpad links, and social media handles — none of which help Claude execute the core task. The 'Pipeline Details' section largely repeats information from the table. Marketing language ('Ship something') and promotional content ($FACTORY token links) waste tokens. | 1 / 3 |
Actionability | The Quick Start section provides concrete bash commands for cloning, scaffolding, and deploying, which is good. However, most pipelines just say 'Follow <pipeline>/CLAUDE.md' without giving any inline executable guidance. The website pipeline is the only one with actual commands. Key details like environment variables, API keys, or Vercel authentication are missing. | 2 / 3 |
Workflow Clarity | There is a numbered sequence (clone → pick pipeline → build → deploy) which provides basic structure. However, there are no validation checkpoints — no step to verify the build succeeded before deploying, no error recovery guidance, and no feedback loops. The LOCAL_RUN_PROOF_GATE is mentioned in the architecture section but never integrated into the actual workflow steps. | 2 / 3 |
Progressive Disclosure | The skill references per-pipeline CLAUDE.md files for detailed instructions, which is good progressive disclosure. However, the main file itself contains too much inline content that doesn't belong (contributing guidelines, architecture details, OpenClaw heartbeat tasks, promotional links). The references are present but the content that should be separated is kept inline. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- 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.