SKILLEMALL.ai
GitHub ↗ RU Sign in

DC app-builder-sdk

Build a new holaOS app using @holaboss/app-builder-sdk (5 backend primitives + optional shadcn dashboard UI). The canonical path for vibe-coded apps — integration modules AND dashboard apps both live here.

holaboss-ai/holaOS Agent Skills author: holaboss-ai NOASSERTION 43 files · 36 scripts body ≈ 10 945 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Build a new holaOS app using @holaboss/app-builder-sdk (5 backend primitives + optional shadcn dashboard UI).

As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, execution cost

IntegrationNotionSlackDiscordGmailData and analyticsSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
D
74/100
safety, quality, tests
Safety 60%
84
Quality 40%
60
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
30
Running it twice w 4
30
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. 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 · 4

✓ No critical or high findings

Medium and low: 4
  • medium Exfiltration net-redirectable-api-key reference/gcalendar-events/e2e.ts:32
    Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
    API key + configurable base URL from environment
  • medium Exfiltration net-redirectable-api-key reference/slack-messaging/e2e.ts:28
    Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
    API key + configurable base URL from environment
  • medium Exfiltration net-redirectable-api-key reference/telegram-messaging/e2e.ts:35
    Helper sends the API key to a host configured by an environment variable — the key can be redirected to another server
    API key + configurable base URL from environment
  • low Dangerous commands cmd-background-process SKILL.md:461
    Starts a background / autostarted process
    MCP_PORT=<port> nohup bun run server.ts > /tmp/<app_id>-module.log 2>&1 &

Files scanned: 43. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 10945 tokens (recommended < 5000); move details to references/
  • note edit-residue the text marks something as outdated (lines 22, 74): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 59/100

  • 0Result and completion. Does not say what the result is
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 31 mutating operations with no state check
  • 40Execution cost. Instruction body is 10945 tokens: crowds the task out of the window
  • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
  • 60Steps. 116 steps, 9 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 3 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 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
  • low The response is described with custom markup (13 tags): a typed call is more reliable

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
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +3Description length 205: enough signal without eating the budget
  • +4Structure: 42 headings
  • +3Step-by-step instructions: 116 items
  • +4Has examples (17 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.