SKILLEMALL.ai
GitHub ↗ RU Sign in

CD archify-tuning

Improve Archify diagram accuracy, visual quality and complete authoring speed with fewer repairs. Use for generation experiments or evaluating changes to layout, routing, diagnostics, authoring instructions and acceptance rules against actual diagrams and agent traces.

The skillemall take

The skill promises to improve Archify diagram accuracy, visual quality, and authoring speed. Quality score sits at 72, process at 38—it works, but unevenly. Nine files and five scripts, yet the data flags broken references. No critical findings, but low process score signals either rough instructions or logic that needs field testing.

Install if you're experimenting with Archify and can tolerate refinement cycles. For production use without validating against your own diagrams, it's a gamble.

tt-a1i/archify Agent Skills author: tt-a1i MIT 9 files · 5 scripts body ≈ 2 203 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Improve Archify diagram accuracy, visual quality and complete authoring speed with fewer repairs.

As a process D 38/100 · Unfinished process — References files that are not bundled: ../../../CONTRIBUTING.md, ../../../CONTRIBUTING.md

AnalyzerData and analyticsAI and agentstype 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
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
D
38/100
Unfinished process
References files that are not bundled: ../../../CONTRIBUTING.md, ../../../CONTRIBUTING.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

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

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../../CONTRIBUTING.md
  • warning missing-ref reference to a missing file: ../../../CONTRIBUTING.md
  • note edit-residue the text marks something as outdated (lines 16): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 38/100

Will not run. References files that are not bundled: ../../../CONTRIBUTING.md, ../../../CONTRIBUTING.md
  • 0Tools and files. 2 referenced file(s) missing: ../../../CONTRIBUTING.md, ../../../CONTRIBUTING.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 100Steps. 21 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2203 tokens
  • low The response is described with custom markup (4 tags): a typed call is more reliable

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
  • +4No input/output examples
  • -31 of 5 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 269: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 21 items
  • +4Reference files are cited in the instructions (3 of 3)

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

In the sandbox The scripts kept to themselves

The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.

Запущено 5 скриптов; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.

scripts/collect.mjsничего за пределами своей папки
scripts/lib.mjsничего за пределами своей папки
scripts/replay.mjsничего за пределами своей папки
scripts/round.mjsничего за пределами своей папки
scripts/shots.mjsничего за пределами своей папки

20 Oct 2026