BC zion-baas
Instructions and authentication code for building headless BaaS applications with Zion.app (functorz.com). Use when integrating Zion backend features like GraphQL, actionflows, AI agents, binary assets, and payments.
As a process C 57/100 · Has gaps — weak spots: result and completion, when it triggers, consistency
GeneratorSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
- 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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 10280 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (zion-baas) differs from the folder (zion-baas-skill)
- 40Execution cost. Instruction body is 10280 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 171 steps
- 100Failures and branches. 6 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
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)
- +3Output format is not stated: the model decides each time
- -36 of 6 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 216: enough signal without eating the budget
- +4Structure: 73 headings
- +3Step-by-step instructions: 171 items
- +4Has examples (43 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: suspicious
This skill appears purpose-built for Zion backend administration, but it stores powerful developer/admin/user tokens in plaintext project files and enables live backend mutations with limited safety controls.
LLM: suspicious (high) · VirusTotal: · 29 May 2026