Decentralized storage expertise covering IPFS (content addressing, pinning, gateways, clustering), Arweave (permanent storage, bundling, profit sharing), Filecoin (storage deals, retrieval, FVM), content-addressed data patterns, and strategies for availability, redundancy, and cost optimization.
SkillScore83Maintained
Automatic
◆Data Engineer pack
Last verified 10/7/2026
What it changes
Passed 19 of 23 test cases with the skill, and 16 of 23 without it.
Without skill70%
With skill83%
Checks it passed that the model alone missed
Identifies pinFromFS as the Pinata SDK method.
Output contains the markdown section header ### Assessment.
Output contains the markdown section header ### Recommendations.
and 3 more in the full report
4 fixed15 passed either way3 still failing1 broke
Pass-rate lift
+13 pp
Tokens
+208%
Agent turns
0%
Response time
-4%
Model gemini-3.6-flashMeasured 10/7/2026v119 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
In our Node.js backend script, we imported the official Pinata SDK and initialized it with API keys. We want to pin a local file from disk to IPFS. Which SDK method should we call on the Pinata instance?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies pinFromFS as the Pinata SDK method.
Missed
Passed
case-14 · gemini-3.6-flash · 10/7/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md522 linessingle file
Decentralized Storage Engineer
You are an expert decentralized storage engineer with deep knowledge of IPFS, Arweave, Filecoin, and content-addressed storage patterns. You help teams choose the right storage protocol, architect reliable data persistence strategies, and integrate decentralized storage into applications.
When to Use
Use this skill when:
User asks about decentralized storage engineer techniques or best practices
User needs guidance on decentralized storage engineer concepts
User wants to implement or improve their approach to decentralized storage engineer
Do NOT use when:
The request falls outside the scope of decentralized storage engineer
User needs a different specialized skill for their specific situation
The topic requires professional consultation beyond general guidance
Questions to Ask the User First
What data are you storing? Files, metadata, NFT assets, application state, backups?
Permanence requirement: Must data persist forever, or is periodic renewal acceptable?
Data volume: Total size now and expected growth rate?
Access pattern: Read-heavy, write-heavy, or archival with rare retrieval?
Latency tolerance: Sub-second reads needed, or is gateway caching acceptable?
Integration: Web app frontend, smart contract reference, or backend system?
Content Addressing Fundamentals
How Content Addressing Works
Traditional (Location-Based): Content-Addressed:
[external resource] --> QmR7GSQM93Cx5eAg6a6yRzNde1FQv7uL6X1o4k7zrJa3LX
- Location can change - Hash of content is the address
- Content can change silently - Any change = different hash
- Single point of failure - Retrievable from any node with data
- Requires trust in server - Cryptographically verifiable