SKILLEMALL.ai
GitHub ↗ RU Sign in

BC codex-qa

QA the omo Codex Light edition (lazycodex / packages/omo-codex) itself, in strict isolation so ONLY our plugin is exercised, never the user's real ~/.codex. The first-party method drives the real `codex app-server` against an isolated CODEX_HOME plus a LOCAL mock model (no real API call), and proves a plugin hook fired by asserting hook/started + hook/completed notifications. Also: isolated install verification, per-component hook probes, a tmux TUI smoke, and runtime log observation (RUST_LOG / logs SQLite / /debug-config). Ships tested helper scripts each with a --self-test. Use whenever someone changes anything under packages/omo-codex or wants to QA, smoke-test, verify, or debug the Codex plugin, its hooks/components, the installer/config.toml, the app-server flow, or the Codex TUI. Triggers: codex qa, qa codex, codex-qa, test codex plugin, verify codex hook, codex app-server, lazycodex qa, isolated CODEX_HOME, prove codex hook fired, codex tui test.

code-yeongyu/oh-my-openagent Agent Skills author: code-yeongyu NOASSERTION 16 files · 9 scripts body ≈ 1 697 tokens Open the sourcegithub.com↗ analyzed 14 d ago

QA the omo Codex Light edition (lazycodex / packages/omo-codex) itself, in strict isolation so ONLY our plugin is exercised, never the user's real ~/.codex.…

As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

IntegrationDockerSoftware 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
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: oh-my-opencode

How to improve

    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: 16. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 56/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 5 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 8 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1697 tokens
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low The response is described with custom markup (3 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)
    • +3Description length 968: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • -31 of 5 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 8 items
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (6 of 6)

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

    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.

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

    Из них 5 не дошли до работы, и об их поведении мы ничего не узнали.

    scripts/app-server-drive.shне запустился: missing dependency: jq
    scripts/hook-unit-probe.shне запустился: missing dependency: jq
    scripts/install-verify.shне запустился: missing dependency: codex
    scripts/lsp-e2e.shне запустился: [codex-lsp-e2e] --scenario is required
    scripts/tui-smoke.shне запустился: missing dependency: tmux
    scripts/lib/app-server-client.mjsничего за пределами своей папки
    scripts/lib/app-server-client.test.jsничего за пределами своей папки
    scripts/lib/common.shничего за пределами своей папки
    scripts/lib/mock-model.mjsничего за пределами своей папки

    26 Sept 2026