CB github-integration
(no description)
- "create a GitHub issue" - "open an issue on"
As a process B 65/100 · Nearly there — weak spots: when it triggers, running it twice, progress reporting
IntegrationGitHubVS CodeSoftware developmenttype and topics are labelled automatically from the skill text
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger - warning
body-longSKILL.md body ≈ 6828 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 65/100
- 0When it triggers. No condition that starts the skill
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 35 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 6828 tokens
- 100Steps. 91 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- low 10 top-level sections: this looks like several domains in one skill
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)
- +3Description length 0: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 78 headings
- +3Step-by-step instructions: 91 items
- +3Output format is stated explicitly
- +4Has examples (70 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
This GitHub skill is coherent and not deceptive, but it gives an agent direct token-backed power to merge PRs, edit or delete files, and change issues without clear confirmation safeguards.
LLM: suspicious (medium) · VirusTotal: · 4 Jul 2026