agentleFS
Sign inStart free
butterbase-aibutterbase-ai/butterbase-plugin/skills/journey-storage/SKILL.md

journey-storage

Skill535 starsChanged 5 months agoMITView on GitHub

Use as the storage build stage of the Butterbase journey. Implements the Storage section of 02-plan.md by delegating to the storage skill. Calls manage_storage (update_config) for bucket setup; uploads are exercised at frontend integration time, not here. Skipped if the plan has no file uploads.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If docs/butterbase/03-preflight.md is missing, older than 24 hours, or 00-state.md has app_id: null, invoke …

    line 18
  2. Very specific:

    Refresh docs: Call butterbase_docs with topic: "storage".

    line 27
  3. Very specific:

    Read the Storage section of 02-plan.md.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Journey: Storage

Stage 3d of the guided journey. Configure storage buckets/ACLs from the plan.

When to use

  • Dispatched by journey when current_stage: storage.
  • Directly via /butterbase-skills:journey-storage.
  • Skipped (annotated (n/a)) if the plan has no Storage section.

Preflight

If docs/butterbase/03-preflight.md is missing, older than 24 hours, or 00-state.md has app_id: null, invoke butterbase-skills:journey-preflight first. Wait for it to return successfully before proceeding.

Inputs

  • docs/butterbase/02-plan.md — the Storage section.
  • docs/butterbase/00-state.md — for app_id.

Procedure

  1. Refresh docs. Call butterbase_docs with topic: "storage". For presigned URL patterns, also WebFetch https://docs.butterbase.ai/storage. Skip if cache is fresh.
  2. Read the Storage section of 02-plan.md. Print it back: "About to configure storage: <buckets>. Proceed?". Wait for yes.
  3. Invoke butterbase-skills:storage via the Skill tool, passing the Storage plan and app_id. The wrapped skill calls manage_storage action: update_config per bucket (visibility, max object size).
  4. Smoke: request an upload URL via manage_storage action: upload_url and a matching download_url to confirm presigned URL minting works.
  5. Append one line to docs/butterbase/04-build-log.md: <ISO timestamp> storage manage_storage ok
  6. Tick - [x] storage in 00-state.md, set current_stage: to the next unchecked stage.
  7. Return to journey orchestrator (or ask "Continue to the next stage? (yes/no)").

Outputs

  • Configured storage buckets.
  • One line in 04-build-log.md.

Anti-patterns

  • ❌ Persisting s3_key in app data — always persist object_id. The wrapped skill handles this; do not override it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free