Scaleway CLI is a command-line tool for managing Scaleway cloud infrastructure from a terminal. It is used by people who operate Scaleway resources and need terminal-based commands, with authentication configured through a Scaleway API key. The catalogue add-ons provide instructions, an MCP integration, and a skill for working with the CLI.
Borrowing it
Nothing to install: this file belongs to scaleway/scaleway-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/scaleway/scaleway-cli/main/.skills/nightly-test-debugger/SKILL.mdgit clone --depth 1 https://github.com/scaleway/scaleway-cliWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/scaleway/scaleway-cli/nightly-test-debugger)<a href="https://agentmods.dev/skills/scaleway/scaleway-cli/nightly-test-debugger"><img src="https://agentmods.dev/badge/skills/scaleway/scaleway-cli/nightly-test-debugger/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/scaleway/scaleway-cli/nightly-test-debugger"><img src="https://agentmods.dev/badge/skills/scaleway/scaleway-cli/nightly-test-debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00072 | $0.00728 |
| Opus 5.5 | $0.00029 | $0.00291 |
| Sonnet 5.5 | $0.00014 | $0.00146 |
| Haiku 4.5 | $0.00007 | $0.00073 |
Grade A, and why
nightly-test-debugger scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nightly Test Debugger
This skill helps you systematically analyze and debug failing nightly acceptance tests in the Scaleway CLI repository.
Understanding Nightly Tests
The nightly test suite (.github/workflows/nightly.yml) runs acceptance tests for all products daily at 00:00 UTC. Each product is tested in isolation with:
CLI_UPDATE_CASSETTES: true- Records API interactionsCLI_UPDATE_GOLDENS: true- Updates expected output files- Real API calls against Scaleway infrastructure
Common failure modes:
- API changes - Upstream API changed, test expectations no longer match
- Cassette mismatches - Recorded HTTP interactions don't match current behavior
- Golden file drift - Output format changed
- Infrastructure issues - Resource provisioning failures, quotas, timeouts
- Race conditions - Async operations not completing in expected time
- Dependency changes - Go module updates breaking compatibility
Debugging Workflow
Step 1: Gather Context
When investigating a failing nightly test, first collect the ID of the most recent run using:
gh run list --workflow "Nightly Acceptance Tests" --limit 1
Step 2: Read the Failure Logs
Fetch the full logs from the GitHub Actions run:
gh run view <RUN_ID> --log | grep FAIL:
This will give you names of the failed tests.
Step 3: Locate the Test File
Test files live in:
internal/namespaces/<product>/v<version>/<test_file>.go
Common patterns:
custom_<feature>_test.go- Feature-specific tests<product>_test.go- General tests
Read the failing test function to understand:
- What the test is trying to do
- What
BeforeFuncsetup runs - What
Checkassertions are made - What
AfterFunccleanup runs
Step 4: Categorize the Failure
Timeout/Infrastructure Failure
Symptoms:
context deadline exceeded
timeout waiting for resource
Diagnosis:
- Check if the timeout value is reasonable
- Look for resource provisioning delays
- Check for quota issues in the nightly environment
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 100 lines · 72 tokens per session scan A 2caf17f0481c
nightly-test-debugger is a skill published in the GitHub repository scaleway/scaleway-cli (1,019 stars, last pushed yesterday), licensed Apache-2.0. It adds 72 tokens to every session and 728 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
test-fix
Diagnose and minimally fix a failing test, then re-run.
swallowtail-qa
Playtest Godot games and exported builds, capture frame spikes, compare QA baselines, and produce Swallowtail branded reports. Use for release QA and reusable game-specific test scenarios, not routine implementation-only unit tests.
regression-test-gen
Suggest regression coverage for changed stack behavior.
live-verify
Prove a behavior change on the running system, not just the test suite: reproduce a bug as a failing test before the fix, then run an adversarial live pass across every path that reaches the behavior and read the resulting artifacts back. Use when fixing a bug, investigating a production issue, or before claiming a…
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.