SKILLEMALL.ai

CC loopx-self-repair

Diagnose and repair LoopX control-plane drift or agent behavior drift. Use when a LoopX task makes unexpectedly small progress, follows a stale or contradictory recommended_action, ignores a higher-priority blocked item while doing fallback work, reports vague owner/user gates, loses todo projection, misaligns benchmark treatment with the real product path, mixes temporary artifacts into commits, or when the user asks for root-cause analysis, self-repair, or why the harness/agent behaved unexpectedly.

huangruiteng/loopx Agent Skills author: huangruiteng Apache-2.0 7 files · 1 script body ≈ 2 613 tokens Open the sourcegithub.com↗ analyzed 6 h ago

Diagnose and repair LoopX control-plane drift or agent behavior drift.

As a process C 57/100 · Has gaps — References files that are not bundled: ../../docs/quota-allocation.md

AnalyzerAI and agentsData and analyticsPersonal productivitytype and topics are labelled automatically from the skill text
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
95
Quality 40%
80
Run on models
none yet
Process rating
C
57/100
Has gaps
References files that are not bundled: ../../docs/quota-allocation.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. 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
  • medium Dangerous commands cmd-eval-dynamic scripts/find_pattern.py:26
    Dynamic code execution from decoded/untrusted input
    exec(compile(_scorer_path.read_bytes(), str(_scorer_path), "exec"), _scorer.__dict__)

Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../docs/quota-allocation.md

Process rating: all ten parameters 57/100

Will not run. References files that are not bundled: ../../docs/quota-allocation.md
  • 0Tools and files. 1 referenced file(s) missing: ../../docs/quota-allocation.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 40Result and completion. Does not say what the result is
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 33 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2613 tokens
  • 100Running it twice. Mutating operations check current state

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
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 506: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 33 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (3 of 4)
  • +3All 1 scripts are documented

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