SKILLEMALL.ai

BF project-os-organizer

Privacy-first, chat-first project manager for vibe coders. Track projects, capture updates, and resume work across local folders, Claude/Codex, and GitHub with explicit opt-in controls.

ClawHub Agent Skills author: Joseph Antonio Bozzo-Horwich v1.2.1 20 files · 13 scripts body ≈ 2 555 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 49/100 · Will not run — References files that are not bundled: scripts/install_openclaw_skill.sh

ProcedureGitHubSoftware developmentInfrastructureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
99
Quality 40%
63
Run on models
none yet
Process rating
F
49/100
Will not run
References files that are not bundled: scripts/install_openclaw_skill.sh
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Dangerous commands cmd-background-process scripts/daemonize_command.py:49
    Starts a background / autostarted process
    os.setsid()

Files scanned: 20. 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/install_openclaw_skill.sh

Process rating: all ten parameters 49/100

Will not run. References files that are not bundled: scripts/install_openclaw_skill.sh
  • 0Tools and files. 1 referenced file(s) missing: scripts/install_openclaw_skill.sh
  • 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
  • 30Running it twice. 3 mutating operations with no state check
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 129 steps
  • 100Failures and branches. 6 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2555 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 12 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
  • +4No input/output examples
  • -35 of 15 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 185: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 129 items
  • +4Reference files are cited in the instructions (2 of 2)

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

External checks

ClawHub: suspicious
This local project organizer is mostly purpose-aligned, but it deserves Review because broad chat routing, direct shell config loading, and opt-in remote/background execution give it more authority than the user may expect.
LLM: suspicious (medium) · VirusTotal: suspicious · 28 May 2026