SKILLEMALL.ai
GitHub ↗ RU Sign in

CF support-to-repro-pack

Convert support tickets, logs, and screenshots into sanitized, reproducible engineering issue packs

ClawHub Agent Skills author: mshs01156 v1.0.0 MIT-0 61 files body ≈ 1 194 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process F 52/100 · Will not run — References files that are not bundled: references/reproduction-checklist.md, references/severity-matrix.md, templates/engineering_issue.md

GeneratorInfrastructureCustomer supporttype 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
C
69/100
safety, quality, tests
Safety 60%
98
Quality 40%
26
Run on models
none yet
Process rating
F
52/100
Will not run
References files that are not bundled: references/reproduction-checklist.md, references/severity-matrix.md, templates/engineering_issue.md
Tools and files w 18
0
Result and completion w 14
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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Secrets in code secret-labelled-token examples/case_hard/input_ticket.md:17
    Labelled token / key literal (vendor format unknown — verify it is not a live credential) (test fixture / example file)
    - API key: sk_l…emo
    fixture
  • low Secrets in code secret-high-entropy-token examples/case_hard/input_ticket.md:17
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)
    - API key: sk_l…emo
    fixture

Files scanned: 42. 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")
  • warning missing-ref reference to a missing file: references/reproduction-checklist.md
  • warning missing-ref reference to a missing file: references/severity-matrix.md
  • warning missing-ref reference to a missing file: templates/engineering_issue.md
  • warning missing-ref reference to a missing file: templates/internal_escalation.md
  • warning missing-ref reference to a missing file: templates/customer_reply.md
  • note frontmatter-key unknown frontmatter key "triggers"

Process rating: all ten parameters 52/100

Will not run. References files that are not bundled: references/reproduction-checklist.md, references/severity-matrix.md, templates/engineering_issue.md
  • 0Tools and files. 5 referenced file(s) missing: references/reproduction-checklist.md, references/severity-matrix.md, templates/engineering_issue.md
  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Failures and branches. 5 branches
  • 100Steps. 25 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1194 tokens
  • 100Running it twice. Mutating operations check current state
  • 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)
  • +3Description length 99: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 25 items
  • +4Has examples (3 code blocks)

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

External checks

ClawHub: suspicious
This skill is a legitimate support-ticket packaging tool, but its sanitization promises are stronger than the artifacts support, so sensitive customer data could remain in generated outputs.
LLM: suspicious (high) · VirusTotal: · 29 May 2026