SKILLEMALL.ai
RU Sign in

AC software-data-github-interact-developer-helper

Guide GitHub issue, pull request, and repository work for coding agents. Use when the user needs to inspect GitHub context, triage issues, plan safe changes, prepare API or CLI commands, summarize PR state, or turn repository signals into implementation steps.

ClawHub Agent Skills author: Kyro v0.1.1 MIT-0 7 files body ≈ 672 tokens Open the sourceclawhub.ai↗ analyzed 17 h ago

Guide GitHub issue, pull request, and repository work for coding agents.

As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

ProcedureGitHubSoftware developmenttype 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
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
C
57/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    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: 7. 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 57/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
    • 30Running it twice. 3 mutating operations with no state check
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 25 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 672 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
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 260: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 25 items
    • +4Reference files are cited in the instructions (1 of 1)

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

    External checks

    ClawHub: clean
    This is a GitHub workflow helper with broad and somewhat messy activation text, but it does not include executable code, hidden persistence, credential theft, or automatic repository changes.
    LLM: benign (high) · VirusTotal: · 20 Jun 2026