SKILLEMALL.ai

BF digital-employee-builder

Build a runnable Agent digital employee from a business codebase or business-function description. Input a business system/module (source code, API docs, or functional spec); output a complete digital-employee workspace — AGENTS.md (operating rules), SOUL.md (persona), IDENTITY.md, USER.md, TOOLS.md, HEARTBEAT.md, an MCP server wrapping business capabilities, per-workflow Skills — plus steps to onboard, run, and verify it in OpenClaw (default) or other harness frameworks (Claude Code, Cursor, custom). Triggers: digital employee, business-code-to-agent, turn a business system into an agent, SOUL.md, AGENTS.md, OpenClaw agent workspace, agent-ify a business function.

ClawHub Agent Skills author: jaggerxzj v0.1.0 MIT-0 7 files body ≈ 5 383 tokens Open the sourceclawhub.ai analyzed 3 d ago

Build a runnable Agent digital employee from a business codebase or business-function description.

As a process F 39/100 · Will not run — References files that are not bundled: assets/workspace/, assets/workspace/*.tmpl, assets/mcp-server-python/server.py.tmpl

GeneratorAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
54
Run on models
none yet
Process rating
F
39/100
Will not run
References files that are not bundled: assets/workspace/, assets/workspace/*.tmpl, assets/mcp-server-python/server.py.tmpl
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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. 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: 7. 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 ≈ 5383 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: assets/workspace/
  • warning missing-ref reference to a missing file: assets/workspace/*.tmpl
  • warning missing-ref reference to a missing file: assets/mcp-server-python/server.py.tmpl
  • warning missing-ref reference to a missing file: assets/mcp-server-ts/server.ts.tmpl
  • warning missing-ref reference to a missing file: assets/skill-template/
  • warning missing-ref reference to a missing file: scripts/workflow.py.tmpl

Process rating: all ten parameters 39/100

Will not run. References files that are not bundled: assets/workspace/, assets/workspace/*.tmpl, assets/mcp-server-python/server.py.tmpl
  • 0Tools and files. 6 referenced file(s) missing: assets/workspace/, assets/workspace/*.tmpl, assets/mcp-server-python/server.py.tmpl
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 23 mutating operations with no state check
  • 70Execution cost. Instruction body is 5383 tokens
  • 85Steps. 77 steps, 1 vague phrases
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 14 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 673: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 77 items
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (5 of 5)

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

External checks

ClawHub: suspicious
This skill has a legitimate purpose, but its templates can create agents that use business credentials for live API changes and scheduled checks without strong built-in safeguards.
LLM: suspicious (medium) · 27 Aug 2026