SKILLEMALL.ai

AC code-reviewer

Default code-quality route for broad code review, PR review, maintainability, correctness, and regression-risk checks. Do not use as the primary route for dedicated OWASP/security audits, review-feedback handling, completion verification, AI-code cleanup, or TDD/test-first work.

foryourhealth111-pixel/Vibe-Skills Agent Skills author: foryourhealth111-pixel Apache-2.0 9 files · 4 scripts body ≈ 1 313 tokens Open the sourcegithub.com↗ analyzed 29 h ago

Default code-quality route for broad code review, PR review, maintainability, correctness, and regression-risk checks.

As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice

AnalyzerDockerKubernetesSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
98
Quality 40%
95
Run on models
none yet
Process rating
C
58/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
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 · 2

    ✓ No critical or high findings

    Medium and low: 2
    • low Secrets in code secret-password-literal references/python-style-guide.md:141
      Hard-coded password / key literal (may be an example) (placeholder value)
      api_key = "sk-1…def"
      placeholder
    • low Exfiltration read-dotenv SKILL.md:150
      Reads a .env file (documentation of a security skill)
      cp .env.example .env
      security skill

    Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 21, 23): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 58/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 1 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (python) that frontmatter does not declare
    • 100Steps. 63 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1313 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 11 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
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 279: enough signal without eating the budget
    • +4Structure: 28 headings
    • +3Step-by-step instructions: 63 items
    • +4Has examples (7 code blocks)
    • +4Reference files are cited in the instructions (4 of 4)
    • +3All 4 scripts are documented

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