SKILLEMALL.ai

AC ocas-forge

Use when creating, building, reviewing, repairing, or validating Agent Skill packages. Runs a mandatory six-phase pipeline: existence gate, classify, scope, architecture, build, validate. Default output is the finished installable package. Trigger phrases: 'create a new skill', 'build a skill', 'design a skill', 'review this skill', 'repair this skill', 'validate skill package', 'update forge'. Do not use for skill evaluation or variant proposals (use Mentor).

ClawHub Agent Skills author: Indigo Karasu v2.3.0 MIT-0 8 files body ≈ 2 056 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions

AnalyzerInfrastructureAI and agentstype and topics are labelled automatically from the skill text
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
Inputs and preconditions w 11
0
When it triggers w 12
50
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 · 0

    ✓ No critical or high findings

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

    Against the Agent Skills spec

    • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 4, column 14: description: Use when creating, building, reviewing, repairing, or validating A… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "install"

    Process rating: all ten parameters 62/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 50When it triggers. No condition that starts the skill
    • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
    • 100Steps. 57 steps
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2056 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • low 19 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 464: enough signal without eating the budget
    • +4Structure: 20 headings
    • +3Step-by-step instructions: 57 items
    • +4Has examples (5 code blocks)
    • +4Reference files are cited in the instructions (4 of 4)

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

    External checks

    ClawHub: suspicious
    Forge has a legitimate skill-building purpose, but it automatically adds background jobs and can silently replace its own installed files from GitHub, so it needs user review before installation.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026