SKILLEMALL.ai
GitHub ↗ RU Sign in

BF erpclaw

AI-native ERP system with self-extending OS. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting. 413 actions across 14 domains, 43 expansion modules. Constitutional guardrails, adversarial audit, schema migration. Double-entry GL, immutable audit trail, US GAAP.

ClawHub Agent Skills author: Nikhil Jathar v3.3.0 MIT-0 80 files body ≈ 4 653 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 44/100 · Will not run — References files that are not bundled: scripts/db_query.py

AnalyzerTelegramGitHubFinancetype 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
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
F
44/100
Will not run
References files that are not bundled: scripts/db_query.py
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
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.
  2. The text references files that are not there: add them or drop the references.
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: 80. 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 missing-ref reference to a missing file: scripts/db_query.py
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "cron"

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: scripts/db_query.py
  • 0Tools and files. 1 referenced file(s) missing: scripts/db_query.py
  • 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. 24 mutating operations with no state check
  • 40Consistency. Frontmatter name (erpclaw) differs from the folder (erp-claw)
  • 70When it triggers. States when to use, but not when not to
  • 70Execution cost. Instruction body is 4653 tokens
  • 100Steps. 12 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (4 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
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 377: enough signal without eating the budget
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 12 items
  • +4Has examples (2 code blocks)

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

External checks

ClawHub: suspicious
This ERP skill is mostly coherent with its stated purpose, but it needs review because it can run scheduled financial actions, execute downloaded modules, and perform host-level web dashboard deployment.
LLM: suspicious (high) · VirusTotal: · 29 May 2026