SKILLEMALL.ai
GitHub ↗ RU Sign in

BD ci-e2e-time-tune

Tune literal `register_cuda_ci(est_time=...)` values in `tests/e2e` from complete GitHub Actions logs produced by `ci-fetch-log`. Use when asked to calibrate E2E timing estimates, produce an evidence-backed runtime CSV, or apply estimate-only changes. Aggregate passed samples by test file, apply a 1.25 safety factor with mandatory upward bucket rounding, and never commit or push changes.

radixark/miles Agent Skills author: radixark 1 file body ≈ 2 048 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Tune literal registercudaci(esttime=...) values in tests/e2e from complete GitHub Actions logs produced by ci-fetch-log. Use when asked to calibrate E2E…

As a process D 43/100 · Unfinished process — References files that are not bundled: ../ci-fetch-log/SKILL.md

GeneratorGitHubData 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
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
D
43/100
Unfinished process
References files that are not bundled: ../ci-fetch-log/SKILL.md
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

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

Against the Agent Skills spec

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

Process rating: all ten parameters 43/100

Will not run. References files that are not bundled: ../ci-fetch-log/SKILL.md
  • 0Tools and files. 1 referenced file(s) missing: ../ci-fetch-log/SKILL.md
  • 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. 2 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 31 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2048 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 (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
  • +1No license
  • +2Single-language instructions
  • +3Description length 390: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 31 items
  • +4Has examples (3 code blocks)

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