SKILLEMALL.ai
GitHub ↗ RU Sign in

CF workflow

Structured work: multi-phase tasks, feature builds, planning, objective loops, hill climbing.

notque/vexjoy-agent Agent Skills author: notque MIT 80 files · 9 scripts body ≈ 2 877 tokens Open the sourcegithub.com↗ analyzed 24 h ago

Structured work: multi-phase tasks, feature builds, planning, objective loops, hill climbing.

As a process F 45/100 · Will not run — References files that are not bundled: references/pl-spec.md, references/pl-pre-plan.md, references/pl-plan-files.md

ProcedureSoftware developmentInfrastructureData and analyticstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
C
79/100
safety, quality, tests
Safety 60%
95
Quality 40%
56
Run on models
none yet
Process rating
F
45/100
Will not run
References files that are not bundled: references/pl-spec.md, references/pl-pre-plan.md, references/pl-plan-files.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

What is at stake

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

Broad scope 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 asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Write Edit Bash Glob Grep Skill Agent Task

Files scanned: 80. 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/pl-spec.md
  • warning missing-ref reference to a missing file: references/pl-pre-plan.md
  • warning missing-ref reference to a missing file: references/pl-plan-files.md
  • warning missing-ref reference to a missing file: references/pl-manage.md
  • warning missing-ref reference to a missing file: references/pl-pause.md
  • warning missing-ref reference to a missing file: references/pl-resume.md
  • warning missing-ref reference to a missing file: references/...
  • warning missing-ref reference to a missing file: references/systematic-debugging.md
  • warning missing-ref reference to a missing file: references/systematic-refactoring.md
  • warning missing-ref reference to a missing file: references/research-pipeline.md
  • warning missing-ref reference to a missing file: references/research-to-article.md
  • warning missing-ref reference to a missing file: references/skill-creation-pipeline.md
  • warning missing-ref reference to a missing file: references/system-upgrade.md
  • warning missing-ref reference to a missing file: references/toolkit-improvement.md
  • warning missing-ref reference to a missing file: references/workflow-orchestrator.md
  • note frontmatter-key unknown frontmatter key "routing"
  • note edit-residue the text marks something as outdated (lines 250): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 45/100

Will not run. References files that are not bundled: references/pl-spec.md, references/pl-pre-plan.md, references/pl-plan-files.md
  • 0Tools and files. 15 referenced file(s) missing: references/pl-spec.md, references/pl-pre-plan.md, references/pl-plan-files.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. 4 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 8 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2877 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)
  • +3Description length 93: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 8 items
  • +4Reference files are cited in the instructions (40 of 48)

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