AC opengemini-nextjs-bestpractice-builder
Build opinionated SaaS projects for solo developers with OpenClaw as orchestrator and Gemini CLI as planning and generation copilot, using a fixed best-practice stack: Next.js App Router, Tailwind, shadcn/ui, Neon PostgreSQL, Prisma 6, Clerk, Resend, Stripe, Cloudflare R2, PostHog, Sentry, Vercel, and FastAPI only for Python-required workloads. Use when the user wants to brainstorm, define, scaffold, document, structure, or implement a SaaS with this exact stack and project layout.
As a process C 57/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, consistency
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Build opinionated SaaS projects for solo developers with OpenClaw … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 57/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 7 mutating operations with no state check
- 40Consistency. Frontmatter name (opengemini-nextjs-bestpractice-builder) differs from the folder (opengemini-next-js-bestpractice-builder)
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 105 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1344 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 486: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 105 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.