SKILLEMALL.ai
GitHub ↗ RU Sign in

BC troubleshooting

Ralphy CLI operations and repair — environment setup, API keys and connectors, `ralphy doctor`, reading logs, diagnosing a failed generation or render, and the CLI cookbook for verbs other roles call. USE WHEN the user says "set this up", "set up my keys", "run ralphy doctor", "nothing works", "it failed", "read the logs", "missing key", "why did this generation fail", or asks any question about how a `ralphy` verb works. TRIGGER (EN): "doctor", "nothing works", "set up keys", "read the logs", "debug this failure", "missing API key", "how do I run <verb>".

alecs5am/ralphy Agent Skills author: alecs5am 4 files body ≈ 1 252 tokens Open the sourcegithub.com↗ analyzed 11 h ago

Ralphy CLI operations and repair — environment setup, API keys and connectors, ralphy doctor, reading logs, diagnosing a failed generation or render, and the…

As a process C 51/100 · Has gaps — References files that are not bundled: ../hyperframes/references/playbook.md

IntegrationSoftware developmentAI 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
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
86
Run on models
none yet
Process rating
C
51/100
Has gaps
References files that are not bundled: ../hyperframes/references/playbook.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
This is a copy of a skill from another catalog; the rating counts the canonical one: troubleshooting (alecs5am/ralphy)

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../hyperframes/references/playbook.md
  • note frontmatter-key unknown frontmatter key "namespace"

Process rating: all ten parameters 51/100

Will not run. References files that are not bundled: ../hyperframes/references/playbook.md
  • 0Tools and files. 1 referenced file(s) missing: ../hyperframes/references/playbook.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. 1 mutating operations with no state check
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 14 steps
  • 100Failures and branches. 3 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1252 tokens
  • 100Progress reporting. Reports progress

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

  • +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
  • +5Description quotes 15 example trigger phrases
  • +3Description length 562: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 14 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)

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