SKILLEMALL.ai
GitHub ↗ RU Sign in

BB project-explorer

Explores unfamiliar GitHub projects, installs and runs them, analyzes architecture, and generates comprehensive documentation guides

ClawHub Agent Skills author: zhanggroot7 v1.0.0 MIT-0 2 files body ≈ 1 081 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 71/100 · Nearly there — weak spots: running it twice, progress reporting

AnalyzerGitHubWriting and documentsInfrastructuretype 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
76/100
safety, quality, tests
Safety 60%
100
Quality 40%
40
Run on models
none yet
Process rating
B
71/100
Nearly there
Progress reporting w 2
0
Running it twice w 4
30
Failures and branches w 10
55
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • error name-missing SKILL.md: frontmatter has no `name`
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "trigger"
  • note frontmatter-key unknown frontmatter key "skill_version"
  • note frontmatter-key unknown frontmatter key "version_date"

Process rating: all ten parameters 71/100

  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 55Failures and branches. 1 branches
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 67 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1081 tokens

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)
  • -212 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 132: enough signal without eating the budget
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 67 items
  • +3Output format is stated explicitly
  • +4Has examples (0 code blocks)

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

External checks

ClawHub: suspicious
The skill appears intended to explore or set up GitHub projects, but it gives broad activation guidance and directs cloning, dependency installation, and running projects without clear safety gates.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026