SKILLEMALL.ai
GitHub ↗ RU Sign in

AC make-repo-contribution

All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly.

github/awesome-copilot Agent Skills author: github MIT 3 files body ≈ 1 479 tokens Open the sourcegithub.com↗ analyzed 31 h ago

All changes to code must follow the guidance documented in the repository.

As a process C 62/100 · Has gaps — weak spots: result and completion, failures and branches, running it twice

GeneratorSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: GitHub Copilot / VS Code Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
C
62/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: RA-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: 3. 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 62/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 19 mutating operations with no state check
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 24 steps, 1 vague phrases
    • 100Tools and files. Tools declared in frontmatter
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1479 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 10 top-level sections: this looks like several domains in one skill

    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 361: enough signal without eating the budget
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 24 items

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