SKILLEMALL.ai

AB bort-agent

Interact with BORT AI agents on BNB Chain via BAP-578. Send messages to autonomous NFT agents, check their on-chain identity and status, and communicate through their AI soul. Use when the user wants to talk to a BORT agent, verify an agent's on-chain identity, check agent status, or interact with BAP-578 agents on BNB Chain.

modbender/skill-library-mcp Agent Skills author: modbender MIT 6 files · 4 scripts body ≈ 1 178 tokens Open the sourcegithub.com analyzed 2 d ago

Interact with BORT AI agents on BNB Chain via BAP-578.

As a process B 70/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting

IntegrationAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
99
Quality 40%
84
Run on models
none yet
Process rating
B
70/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Running it twice w 4
30
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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Secrets in code secret-high-entropy-token references/bap578-overview.md:11
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | PlatformRegistry | `0x98…316` |
      table

    Files scanned: 6. 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 70/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 5 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 18 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1178 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)
    • -2localhost URLs: will not work for another user
    • -41 reference files, but SKILL.md never points to them: the model will not open them
    • +1No license
    • +2Single-language instructions
    • +3Description length 327: enough signal without eating the budget
    • +4Structure: 11 headings
    • +3Step-by-step instructions: 18 items
    • +3Output format is stated explicitly
    • +4Has examples (7 code blocks)
    • +3All 4 scripts are documented

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