SKILLEMALL.ai

BF fswe

Full-stack engineering skill with 24 modules covering architecture, API, performance, testing, DevOps, security, and modern TypeScript stack.

ClawHub Agent Skills author: Khamalismadie⚡ v2.0.0 MIT-0 29 files body ≈ 1 088 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process F 48/100 · Will not run — References files that are not bundled: references/<module>/SKILL.md

IntegrationSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
64
Run on models
none yet
Process rating
F
48/100
Will not run
References files that are not bundled: references/<module>/SKILL.md
Tools and files w 18
0
Inputs and preconditions w 11
0
When it triggers w 12
20
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: 5. 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: references/<module>/SKILL.md
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 48/100

Will not run. References files that are not bundled: references/<module>/SKILL.md
  • 0Tools and files. 1 referenced file(s) missing: references/<module>/SKILL.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 34 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1088 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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)
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 141: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 34 items
  • +3Output format is stated explicitly

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

External checks

ClawHub: clean
This is a coherent full-stack engineering reference skill, but some sample code should be treated as illustrative and hardened before production use.
LLM: benign (high) · VirusTotal: · 31 Jul 2026