SKILLEMALL.ai
GitHub ↗ RU Sign in

AB auto-repo-setup

Diagnoses and repairs repository setup and guarded Git workflows for Claude Code or Codex — environment repair, startup sync, hook auditing, collaborator handoff. Use when a repo won't run, a teammate onboards, hook output duplicates, or commit/push/conflict needs guarding. Not for lost-commit recovery (use git-safety-net), GitHub ops (use github-ops), or history scrubbing (use github-sensitive-data-cleanup).

daymade/claude-code-skills Claude Code author: daymade MIT 11 files · 4 scripts body ≈ 3 394 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Diagnoses and repairs repository setup and guarded Git workflows for Claude Code or Codex — environment repair, startup sync, hook auditing, collaborator…

As a process B 65/100 · Nearly there — weak spots: result and completion

ProcedureGitHubSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
91
Run on models
none yet
Process rating
B
65/100
Nearly there
Result and completion w 14
0
When it triggers w 12
50
Failures and branches w 10
50
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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: 9. 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 65/100

    • 0Result and completion. Does not say what the result is
    • 50When it triggers. No condition that starts the skill
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web, git, python) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 54 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3394 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • low The response is described with custom markup (3 tags): a typed call is more reliable
    • medium 4 test cases, all positive: not one "should refuse" or "should ask first"

    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
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 412: enough signal without eating the budget
    • +4Structure: 16 headings
    • +3Step-by-step instructions: 54 items
    • +4Reference files are cited in the instructions (5 of 5)
    • +3All 3 scripts are documented

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