SKILLEMALL.ai
GitHub ↗ RU Sign in

AB create-branch

Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.

sickn33/agentic-awesome-skills Claude Code author: sickn33 MIT 1 file body ≈ 1 370 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Create a git branch following Sentry naming conventions.

As a process B 70/100 · Nearly there — weak spots: result and completion, when it triggers, progress reporting

GeneratorSoftware 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
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
86
Run on models
none yet
Process rating
B
70/100
Nearly there
Progress reporting w 2
0
When it triggers w 12
20
Result and completion w 14
40
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: create-branch (sickn33/agentic-awesome-skills)

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

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: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"

    Process rating: all ten parameters 70/100

    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 40Result and completion. Does not say what the result is
    • 60Tools and files. Uses tools (bash, git) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 13 steps
    • 100Failures and branches. 6 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1370 tokens
    • 100Running it twice. Mutating operations check current state
    • low The response is described with custom markup (5 tags): a typed call is more reliable

    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

    • +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
    • +5Description quotes 5 example trigger phrases
    • +3Description length 217: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 13 items
    • +4Has examples (3 code blocks)

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