agentleFS
Sign inStart free
fusebase-devfusebase-dev/fusebase-flow/.agents/skills/file-upload/SKILL.md

file-upload

Skill9 starsChanged 27 days agoMITView on GitHub

Canonical low-level Fusebase file upload lifecycle and file API guide. Use it when implementing temp -> stored -> display URL flows or building file descriptors for downstream apps.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use sqli, xss and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SubhiSecSkill

    sqli

    Hunt SQL injection in REST/GraphQL/SOAP/raw parameters using sqlmap, ghauri, manual UNION/Time/Boolean techniques, and custom WAF-bypass tamper scripts. Use when an input flows into a database query or when the user has identified a parameter that might be vulnerable.

    Also in 6 projects that use this

  • SubhiSecSkill

    xss

    Hunt reflected, stored, and DOM-based Cross-Site Scripting (XSS) including CSP bypass, polyglot payloads, mutation XSS (mXSS), markdown XSS, and template XSS. Use when the user has identified a parameter or input that reflects to the page, or wants to test for XSS in a specific input.

    Also in 7 projects that use this

  • yaklangSkill

    open-redirect

    Open redirect playbook. Use when URL parameters, form actions, or JavaScript sinks control navigation targets and may redirect users to attacker-controlled destinations.

    Also in 6 projects that use this

  • blacklanternsecuritySkill

    ssrf

    Guide server-side request forgery (SSRF) exploitation during authorized penetration testing.

    Also in 7 projects that use this

  • langbyyiSkill

    path-traversal

    Path traversal and LFI playbook. Use when file paths, download endpoints, include operations, archive extraction, or wrapper behavior may expose filesystem control.

    Also in 4 projects that use this

  • blacklanternsecuritySkill

    csrf

    Exploit Cross-Site Request Forgery (CSRF) vulnerabilities during authorized penetration testing.

    Also in 4 projects that use this

  • +3 more from SubhiSec
  • +1 more from blacklanternsecurity

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Do not use this skill to describe how to write dashboard cell data.

    line 20
  2. Very specific:

    Do not use this skill for Gate MCP operation auth, scopes, or operation discovery.

    line 21
  3. Distinctive:

    Do not copy upload endpoint or payload blocks into neighboring skills.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “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

File Upload

This skill is the single source of truth for the low-level file upload lifecycle. Load Upload Lifecycle for the canonical tempStoredFileName -> storedFileUUID -> readUrl / relative url -> file descriptor flow.

Hard rules

  • Never store user file/binary bytes in a FuseBase PostgreSQL isolated store (base64 / bytea / data URL), including “MVP” shortcuts. Upload with this skill / Gate files ops; persist only storedFileUUID, readUrl, and small metadata in SQL or dashboard cells.
  • Needing files.write is not a reason to put attachments in SQL. Sync Gate permissions (fusebase app update <appId> --sync-gate-permissions) instead.
  • Visitor / anonymous / public-link apps: browser visitor tokens usually cannot call files.write. Broker upload on the app feature backend with FBS_FEATURE_TOKEN, then return storedFileUUID / readUrl to the client.
  • Ordinary isolated-SQL write/execute paths are not the 64MiB importIsolatedStoreSqlRows cap — practical bodies are ~100–150 KB. Do not design attachments against SQL payload size.

When NOT To Use This Skill

  • Do not use this skill to describe how to write dashboard cell data. For dashboard files columns, load fusebase-dashboards and pass the already-uploaded file descriptor to batchPutDashboardData.
  • Do not use this skill for Gate MCP operation auth, scopes, or operation discovery. For Gate startMultipartFileUpload, completeMultipartFileUpload, and deleteFile, load fusebase-gate (prompt/reference files).
  • Do not copy upload endpoint or payload blocks into neighboring skills. Link to Upload Lifecycle and keep only a short handoff.

Scope

  • Owns: temp file creation, stored file creation, display URL rules, and file descriptor terminology.
  • Neighbor skills: fusebase-dashboards owns dashboard files cell writes; fusebase-gate owns Gate operation names, auth, and scope.
  • Required terminology: tempStoredFileName, storedFileUUID, readUrl, relative url, file descriptor.

Anti-Overlap Checklist

  • Keep this skill focused on low-level lifecycle and file APIs.
  • Link neighboring skills instead of duplicating their API blocks.
  • Use one handoff sentence when another skill owns the next step.
  • Do not describe dashboard batchPutDashboardData payloads here.
  • Do not describe Gate auth/scope rules here.
  • Never recommend SQL blob / base64 attachment storage.

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