SKILLEMALL.ai

AC poidh-bounty

Post bounties and evaluate/accept winning submissions on poidh (pics or it didn't happen) on Arbitrum, Base, or Degen Chain. Use this skill when the user wants to create a bounty on poidh.xyz, post a task with an ETH or DEGEN reward on-chain, evaluate photo submissions using vision, accept a winning claim on a solo bounty, or initiate/resolve voting on an open bounty.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 4 777 tokens Open the sourcegithub.com analyzed 2 d ago

Post bounties and evaluate/accept winning submissions on poidh (pics or it didn't happen) on Arbitrum, Base, or Degen Chain.

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

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

    ✓ No critical or high findings

    Medium and low: 5
    • low Secrets in code secret-high-entropy-token SKILL.md:45
      High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
      | Arbitrum    | `0x55…719` | arbiscan.io         |
      table
    • low Secrets in code secret-high-entropy-token SKILL.md:46
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; documentation table row)
      | Base        | `0x55…719` | basescan.org        |
      detectortable
    • low Secrets in code secret-high-entropy-token SKILL.md:47
      High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; documentation table row)
      | Degen Chain | `0x18…43f` | explorer.degen.tips |
      detectortable
    • low Secrets in code secret-high-entropy-token SKILL.md:60
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      POIDH_CONTRACT_ADDRESS="0x18…43f"
      quoted
    • low Secrets in code secret-high-entropy-token SKILL.md:63
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      POIDH_CONTRACT_ADDRESS="0x55…719"
      quoted

    Files scanned: 1. 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 55/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 40Result and completion. Does not say what the result is
    • 40Consistency. Frontmatter name (poidh-bounty) differs from the folder (poidh)
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 60Steps. 38 steps, 5 vague phrases
    • 70When it triggers. States when to use, but not when not to
    • 70Execution cost. Instruction body is 4777 tokens
    • 100Failures and branches. 3 branches, has a failure section
    • 100Running it twice. Mutating operations check current state
    • low 13 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
    • +1No license
    • +2Single-language instructions
    • +3Description length 370: enough signal without eating the budget
    • +4Structure: 35 headings
    • +3Step-by-step instructions: 38 items
    • +4Has examples (26 code blocks)

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