SKILLEMALL.ai
GitHub ↗ RU Sign in

BC Family Steward

AI-powered family office management system for ultra-high-net-worth families - manage family members, professional contacts, legal documents, and tasks with natural language

ClawHub Agent Skills author: Justin Liu v1.0.0 7 files · 2 scripts body ≈ 2 497 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

ReferenceInfrastructuretype 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
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
64
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Running it twice w 4
30
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • 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 59/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 1 mutating operations with no state check
  • 40Consistency. Frontmatter name (Family Steward) differs from the folder (family-steward)
  • 50Failures and branches. 0 branches, has a failure section
  • 70When it triggers. States when to use, but not when not to
  • 100Tools and files. No external tools needed
  • 100Steps. 93 steps
  • 100Execution cost. Instruction body is 2497 tokens
  • 100Progress reporting. Reports progress
  • 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
  • -214 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 173: enough signal without eating the budget
  • +4Structure: 27 headings
  • +3Step-by-step instructions: 93 items
  • +4Has examples (28 code blocks)

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

External checks

ClawHub: clean
Family Steward is a coherent local family-office management skill, but users should be careful because it handles highly sensitive records and has broad activation language.
LLM: benign (medium) · VirusTotal: · 29 May 2026