CD github
Query and manage GitHub repositories - list repos, check CI status, create issues, search repos, and view recent activity.
Query and manage GitHub repositories - list repos, check CI status, create issues, search repos, and view recent activity.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches
The same skill appears in 4 more places: ClawHub, ClawHub, ClawHub, ClawHub
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 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
- 30Running it twice. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (github) differs from the folder (openclaw-github-assistant)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 16 steps
- 100Execution cost. Instruction body is 541 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 122: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
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.
Запущено 7 скриптов; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.
api.d.ts | ничего за пределами своей папки |
api.js | ничего за пределами своей папки |
index.d.ts | ничего за пределами своей папки |
index.js | ничего за пределами своей папки |
test.js | ничего за пределами своей папки |
types.d.ts | ничего за пределами своей папки |
types.js | ничего за пределами своей папки |
26 Sept 2026