SKILLEMALL.ai
GitHub ↗ RU Sign in

CF architecture-deepening

Improve architecture across modules by deepening interfaces.

notque/vexjoy-agent Agent Skills author: notque MIT 8 files · 2 scripts body ≈ 3 064 tokens Open the sourcegithub.com↗ analyzed 7 d ago

Improve architecture across modules by deepening interfaces.

As a process F 38/100 · Will not run — References files that are not bundled: ../../shared-patterns/schemas/architecture-change-handoff.schema.json

ProcedureSoftware developmenttype 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%
90
Quality 40%
62
Run on models
none yet
Process rating
F
38/100
Will not run
References files that are not bundled: ../../shared-patterns/schemas/architecture-change-handoff.schema.json
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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.

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

✓ No critical or high findings

Medium and low: 2
  • medium Dangerous commands cmd-autorun-instruction references/maintenance-lifecycle.md:202
    Instructs the agent to auto-run a script on every session
    Never encode a skill and pipeline as one slash-delimited identifier. Both names must exist in the generated skill/pipeline registries. For any non-null consultation ADR, first run `adr-query.py regist
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Agent Bash Read Write Edit Glob Grep

Files scanned: 8. 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: ../../shared-patterns/schemas/architecture-change-handoff.schema.json
  • note frontmatter-key unknown frontmatter key "command"
  • note frontmatter-key unknown frontmatter key "routing"

Process rating: all ten parameters 38/100

Will not run. References files that are not bundled: ../../shared-patterns/schemas/architecture-change-handoff.schema.json
  • 0Tools and files. 1 referenced file(s) missing: ../../shared-patterns/schemas/architecture-change-handoff.schema.json
  • 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
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 22 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3064 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)
  • +3Description length 60: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -31 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 22 items
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)

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