FC github-bug-report
Submit bug reports to GitHub for OpenClaw issues. Use when: (1)发现了明确的bug并想提交给官方; (2)官方产品出现问题需要报障; (3)想查询现有issue状态; (4)需要跟进已提交issue的进展. Includes issue template, GitHub API workflow, and post-submission follow-up reminders via cron.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
How to improve
- Remove the critical guard findings (secrets, dangerous commands, hidden instructions): while they stand the skill is blocked and cannot grade above F.
- 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 · 14
-
critical Secrets in code
secret-github-tokenreferences/quick-ref.md:17GitHub token (quoted — discussed, not commanded)-H "Authorization: token ghp_…FXv"
quoted -
critical Secrets in code
secret-github-tokenreferences/quick-ref.md:24GitHub token (quoted — discussed, not commanded)-H "Authorization: token ghp_…FXv"
quoted -
critical Secrets in code
secret-github-tokenreferences/quick-ref.md:31GitHub token (quoted — discussed, not commanded)-H "Authorization: token ghp_…FXv" \
quoted -
critical Secrets in code
secret-github-tokenreferences/quick-ref.md:42GitHub token (quoted — discussed, not commanded)-H "Authorization: token ghp_…FXv" \
quoted -
critical Secrets in code
secret-github-tokenscripts/submit_issue.py:11GitHub token (quoted — discussed, not commanded)TOKEN = "ghp_…FXv"
quoted -
critical Secrets in code
secret-github-tokenSKILL.md:94GitHub token (quoted — discussed, not commanded)当前 token：`ghp_…FXv`
quoted -
critical Secrets in code
secret-github-tokenSKILL.md:98GitHub tokenAuthorization: token ghp_…FXv
Medium and low: 7
-
low Secrets in code
secret-high-entropy-tokenreferences/quick-ref.md:17High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)-H "Authorization: token ghp_…FXv"
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/quick-ref.md:24High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)-H "Authorization: token ghp_…FXv"
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/quick-ref.md:31High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)-H "Authorization: token ghp_…FXv" \
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/quick-ref.md:42High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)-H "Authorization: token ghp_…FXv" \
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/submit_issue.py:11High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)TOKEN = "ghp_…FXv"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:94High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)当前 token：`ghp_…FXv`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:98High-entropy token-like string (may be an id, hash or a credential)Authorization: token ghp_…FXv
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 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
- 100Tools and files. No external tools needed
- 100Steps. 5 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 449 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 230: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.