SKILLEMALL.ai
GitHub ↗ RU Sign in

CB storacha-upload

Upload files to IPFS, store on Storacha, upload to decentralized storage, check Storacha status, view storage usage, create Storacha space, switch space, list spaces, retrieve files by CID, open IPFS content, get gateway link, decentralized storage, web3 storage, pin to IPFS, content-addressed storage, store on chain, get my CID, backup to IPFS, share IPFS link, upload directory, remove upload, Storacha delegation, IPFS file sharing, permanent storage, Filecoin backup, manage Storacha account, upload this image, upload this photo, upload this file to storacha, save this to IPFS, put this on IPFS, how much space do I have, how much storage left, check my storage, what's my storage usage, am I running out of space, storage remaining, create a new space, make a space, set up storacha, setup storacha, login to storacha, sign in to storacha, connect storacha, authenticate storacha, show my uploads, what have I uploaded, list my files, my IPFS files, delete this upload, remove this file from storacha, get me the link, give me the IPFS link, share this file, get download link, open this CID, upload pic, upload document, store image, save photo to IPFS, how much space is there, check storacha, storacha status

Not recommendedcritical or high security findings
modbender/skill-library-mcp Agent Skills author: modbender MIT 3 files · 1 script body ≈ 3 672 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Upload files to IPFS, store on Storacha, upload to decentralized storage, check Storacha status, view storage usage, create Storacha space, switch space, list…

As a process B 72/100 · Nearly there — weak spots: when it triggers

IntegrationData and analyticsAI and agentsMarketingtype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
C
66/100
safety, quality, tests
Safety 60%
82
Quality 40%
43
Run on models
none yet
Process rating
B
72/100
Nearly there
When it triggers w 12
20
Tools and files w 18
60
Result and completion w 14
60
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Concealment
If you install

The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.

For the author

Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  3. Shorten the description to 1024 characters.
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

  • high Concealment en-hide-from-user SKILL.md:66
    Instruction to hide actions from the user
    1. **Always check authentication first.** Before any operation, silently run `storacha whoami`. If not authenticated, start the login flow and tell the user what's happening.

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

Against the Agent Skills spec

  • error description-long description is 1220 chars, limit 1024
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 72/100

  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 40 steps, 1 vague phrases
  • 100Failures and branches. 6 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3672 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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)
  • +3Description length 1220: 120–800 characters recommended
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 40 items
  • +3Output format is stated explicitly
  • +4Has examples (34 code blocks)

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