SKILLEMALL.ai
RU Sign in

AC redline

Live rate-limit awareness for Claude.ai (Max/Pro) and OpenAI (Plus/Pro/Codex). Never hit the red line again — your agent checks remaining budget every heartbeat and automatically throttles from full-send to conservation mode. Two CLI scripts + a 4-tier pacing strategy (GREEN/YELLOW/ORANGE/RED) that keeps you running at maximum token efficiency 24/7.

ClawHub Agent Skills author: Weston Johnson v0.2.0 3 files body ≈ 682 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process C 55/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

IntegrationAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
75
Run on models
none yet
Process rating
C
55/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 55/100

  • 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
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 5 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 682 tokens
  • 100Running it twice. No mutating operations

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 351: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 5 items
  • +3Output format is stated explicitly
  • +4Has examples (5 code blocks)

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

External checks

ClawHub: suspicious
RedLine has a legitimate usage-tracking purpose, but it asks agents to repeatedly use local OAuth credentials through scripts that are not included for review.
LLM: suspicious (high) · VirusTotal: benign · 27 May 2026