AC git_commit_pr_workflow
Use when the user wants the full git workflow: branch creation if needed, commit, push, and PR create or update with a concise summary and test plan.
As a process C 58/100 · Has gaps — weak spots: result and completion, failures and branches, consistency
ProcedureSoftware developmentWriting and documentsInfrastructuretype and topics are labelled automatically from the skill text
This is a copy of a skill from another catalog; the rating counts the canonical one: git_commit_pr_workflow (ClawHub)
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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 58/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 17 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (git_commit_pr_workflow) differs from the folder (git-commit-pr-workflow)
- 60Tools and files. Uses tools (git) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 22 steps
- 100Execution cost. Instruction body is 287 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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 149: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 22 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.
External checks
ClawHub: clean
The reviewed skill artifacts are coherent developer-assistance workflows with disclosed commands and no evidence of hidden collection, persistence, or exfiltration.
LLM: benign (medium) · VirusTotal: · 29 May 2026