SKILLEMALL.ai

BC maritime-signpost

Signpost (not a knowledge pack) for maritime safety and class rules: SOLAS Consolidated Edition 2024 (IH110E) as the paywalled statutory core, ISM Code & Guidelines 2018 (ID117E), ISPS Code 2003 (K116E) and the 2021 guide (IB116E), and COLREGS 2026 (IC904E), with designation, edition, owner, status, and official URL only. Contains no source content. Free-path layers are US flag implementation (eCFR Title 46 and USCG circulars), the USCG Navigation Rules PDF, UK MCA notices under Open Government Licence v3.0, and class portals (DNV, ABS, Bureau Veritas). None of those layers is the IMO consolidated text. No in-repo pack covers these instruments.

jgsystemsconsulting/jgs-se-knowledge-packs Agent Skills author: jgsystemsconsulting 2 files body ≈ 3 724 tokens Open the sourcegithub.com↗ analyzed 2 h ago

Signpost (not a knowledge pack) for maritime safety and class rules: SOLAS Consolidated Edition 2024 (IH110E) as the paywalled statutory core, ISM Code &…

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

ProcedureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
C
51/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

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "kind"

    Process rating: all ten parameters 51/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
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 11 mutating operations with no state check
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 12 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3724 tokens

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

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