Workflow·Files & Storage·v1.2.0

Backblaze B2 Cloud Storage

Manage Backblaze B2 cloud storage: list files, audit usage, estimate cost, clean up stale data, review security posture, and manage…

You say
Buy it · $69 Read it before you buy $69 Written by backblaze-labs · unverified publisher
Context cost
7.7k tokensestimated from the bundle, loaded when it triggers
Bundle
8 files · 30.8 kB1 script among them — read before you run
Licence
MITpaid listing
Last change
v1.2.0
Servers it uses
Noneruns standalone

What it does

Manage Backblaze B2 cloud storage. List files, audit usage, estimate cost, clean up stale data, review security posture, and manage lifecycle rules. Use when the user mentions B2, Backblaze, object storage buckets, or storage cleanup.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

object-storagebucketsbackblazecleanup
Filed under

Files & Storage

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md4.8 kB · 111 lines
--- name: b2-cloud-storage description: Manage Backblaze B2 cloud storage. List files, audit usage, estimate cost, clean up stale data, review security posture, and manage lifecycle rules. Use when the user mentions B2, Backblaze, object storage buckets, or storage cleanup. license: MIT compatibility: Requires user-installed b2 CLI v4+ and Python 3.10+. metadata: author: jdeleon version: "1.2.0" allowed-tools: Bash(b2:*) Bash(python:*) Read Write Grep Glob ---
12# B2 Cloud Storage Management
13
14Manage Backblaze B2 cloud storage: list files, audit usage, estimate cost, clean up stale data, and review security posture.
15
16## Security Rules (MANDATORY)
17
181. **Never** run b2 account get, b2 account clear, or any b2 key * subcommand — these expose or mutate credentials.
192. **Never** read ~/.b2_account_info or any file matching *b2_account_info* — this is the B2 credential database (SQLite).
203. **Always** run b2 rm --dry-run before any real deletion; show the user what would be deleted and require an explicit "yes" before executing.
214. **Never** change a bucket to allPublic without first warning the user about the security implications and getting explicit confirmation.
225. **Default to read-only** — only perform writes or deletes when the user explicitly requests them.
236. **Never** store or write API keys, application keys, or account IDs to any file.
247. If the user pastes key values into the chat instead of the terminal, warn them immediately and recommend rotating the key. Never echo, store, or reference key values that appear in conversation.
25
26## First-Use Flow
27
281. Check the B2 CLI is installed: b2 version. If missing, ask the user to install the CLI outside the agent, then rerun b2 version - see references/setup.md for detail.
292. Verify the CLI is authorized: b2 ls. If it fails with an auth error, walk the user through references/setup.md.
303. Check for a per-project config at .claude/b2-config.json in the project root. If missing, ask the user for bucket + prefix and create one.
31
32### Interactive auth note
33
34b2 account authorize (no args) reads keys from an interactive prompt, which agents cannot drive. The user has two options:
35
36- Run it themselves in the terminal — in Claude Code they can type !b2 account authorize to execute directly in the session.
37- Pass the keyID and applicationKey as positional args: b2 account authorize <keyID> <appKey> (keys will appear in shell history — less safe).
38- Or set B2_APPLICATION_KEY_ID and B2_APPLICATION_KEY env vars before running B2 commands (recommended for scripts and CI).
39
40## Project-Level Config
41
42Per-project config at .claude/b2-config.json:
43
44```json
45{
46 "bucket": "my-project-bucket",
47 "prefix": "",
48 "accountInfoPath": "~/.b2_account_info"
49}
50```
51
52| Field | Purpose |
53|-------|---------|
54| bucket | Default bucket name for this project |
55| prefix | Optional prefix to scope all operations (e.g. data/models/) |
56| accountInfoPath | Path to B2 credential file — allows different keys per project |
57
58If accountInfoPath differs from the default, prepend B2_ACCOUNT_INFO=<path> when running b2 commands. This file stores bucket names and paths only — never API keys.
59
60## Common Actions
61
62### List & search
63
64```bash
65b2 ls b2://<bucket> # top-level
66b2 ls -r b2://<bucket> # recursive
67b2 ls -r --json b2://<bucket> # JSON for scripting
68b2 ls --versions -r --json b2://<b> # include old versions + hide markers
69b2 ls b2://<bucket>/<prefix> # prefix-scoped
70```
71
72### Inspect file
73
74```bash
75b2 file info b2id://<fileId>
76```
77
78### Storage audit (usage, stale, large, duplicates, cost)
79
80```bash
81python scripts/storage_audit.py <bucket>
82python scripts/storage_audit.py <bucket> --json
83python scripts/storage_audit.py <bucket> --stale-days 180 --large-mb 500 --prefix-depth 2
84```
85
86Reports live vs. billable storage, unfinished large files, old versions, hide markers, SHA1-based duplicates, and an estimated monthly cost.
87
88### Cleanup (destructive)
89
90See references/cleanup-playbook.md. Never skip the dry-run step.
91
92### Lifecycle rules
93
94```bash
95b2 bucket get <bucket>
96b2 bucket update --lifecycle-rules '<json>' <bucket> allPrivate
97```
98
99Lifecycle rule JSON format is in references/b2-cli-reference.md.
100
101### Security review
102
103See references/security-review.md for the full checklist (bucket type, SSE, CORS, object lock, replication, lifecycle coverage).
104
105## References
106
107- references/setup.md — first-use setup walk-through (install, app-key creation, authorization)
108- references/cleanup-playbook.md — safe deletion procedure with dry-run
109- references/security-review.md — per-bucket security audit checklist
110- references/b2-cli-reference.md — CLI v4 command reference
111
In the file
SKILL.md671 words
Files8
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈120
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
7,580
on trigger
The instruction body and 7 supporting files, read only when the skill fires.
3.9%
of a 200k window
Ten skills this size would take about 39% of the window before you open a file.
050k100k150k200k context window

7.7k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It asks the agent to write files, using whatever file access your client already has. It never touches the network.

What it asks for
Writes filesyes
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

8 files, 30.8 kB on disk. Mostly text — the instructions the model reads — with 1 script in it that your client would run only if the instructions tell it to.

  • SKILL.md4.8 kB
  • b2-config.example.json0.1 kB
  • .claude-plugin/plugin.json0.6 kB
  • references/b2-cli-reference.md2.8 kB
  • references/cleanup-playbook.md2.7 kB
  • references/security-review.md3.1 kB
  • references/setup.md3.7 kB
  • scripts/storage_audit.py13.0 kB
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 1 script beside the text, so the bundle is 8 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$69 once
Backblaze B2 Cloud Storage · MIT · backblaze-labs
one-time
Price$69 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery release of 1.x through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Version1.2.0
Publishedno release date on file
Price$69
Referencebackblaze-labs/backblaze-b2-cloud-storage

Versions

v1.2.0 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v1.2.0
  • No earlier releases have been published to the marketplace.
Pinning

Put backblaze-labs/backblaze-b2-cloud-storage@1.2.0 in the install command to hold this exact version. Without the suffix you get whatever is current the day you install, and nothing moves under you afterwards.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

BA
backblaze-labs

Publishes on mcprush.

0 servers listed1 skill listednot claimed
Profile
Publisher
Servers0