SKILLEMALL.ai
GitHub ↗ RU Sign in

BD archive-project

Organize completed projects into searchable archives with session transcript backup.

ClawHub Agent Skills author: KaigeGao v1.2.5 MIT-0 4 files body ≈ 2 285 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ReferenceInfrastructuretype 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
87/100
safety, quality, tests
Safety 60%
99
Quality 40%
69
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
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.
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 Secrets in code secret-github-token scripts/sanitize_transcript.py:328
    GitHub token (placeholder value)
    '{"content": [{"text": "token ghp_…890 email te…@….com ip 192.168.1.1"}]}',
    placeholder

Files scanned: 4. 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")
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "dependencies"
  • note frontmatter-key unknown frontmatter key "configPaths"
  • note frontmatter-key unknown frontmatter key "permissions"
  • note frontmatter-key unknown frontmatter key "dataPolicy"

Process rating: all ten parameters 49/100

  • 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. 8 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, git) that frontmatter does not declare
  • 60Failures and branches. 2 branches
  • 100Steps. 19 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2285 tokens
  • 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)
  • +3Description length 84: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 19 items
  • +4Has examples (14 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: clean
This skill is a disclosed project-archiving workflow, but it handles sensitive local transcripts and should be used only when the user intends long-term retention.
LLM: benign (medium) · VirusTotal: · 29 May 2026