SKILLEMALL.ai
GitHub ↗ RU Sign in

BB buildertrend

Complete Buildertrend automation via Browser Relay - 43 playbooks covering sales, project management, financials, scheduling, change orders, daily logs, RFIs, punch lists, invoicing, procurement. No API required.

ClawHub Agent Skills author: Kris Mj v1.0.0 53 files body ≈ 3 427 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 73/100 · Nearly there — weak spots: result and completion, when it triggers

ProcedureInfrastructureOperations and projectstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
98
Quality 40%
71
Run on models
none yet
Process rating
B
73/100
Nearly there
Result and completion w 14
0
When it triggers w 12
20
Inputs and preconditions w 11
70
the three weakest of ten parameters · all ten

How to improve

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

✓ No critical or high findings

Medium and low: 2
  • low Secrets in code secret-high-entropy-token playbooks/photo-video-management.md:239
    High-entropy token-like string (may be an id, hash or a credential)
    2026…ete
  • low Secrets in code secret-high-entropy-token playbooks/photo-video-management.md:240
    High-entropy token-like string (may be an id, hash or a credential)
    2026…ing

Files scanned: 53. 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")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 73/100

  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 61 steps
  • 100Failures and branches. 3 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3427 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low 11 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 212: enough signal without eating the budget
  • +4Structure: 25 headings
  • +3Step-by-step instructions: 61 items
  • +4Has examples (4 code blocks)

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

External checks

ClawHub: suspicious
This Buildertrend skill is useful, but it needs Review because it can change accounting records and other workspace systems beyond the clearly stated browser-only Buildertrend scope.
LLM: suspicious (high) · VirusTotal: · 29 May 2026