Firebase Storage Agent Skill
Use when setting up Storage, uploading/downloading files, managing metadata, handling errors, or applying security rules.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/evanca/flutter-ai-rules --skill firebase-storageThe instruction itself
9 sections, as written by the authorFirebase Cloud Storage Skill
This skill defines how to correctly use Firebase Cloud Storage in Flutter applications.
When to Use
Use this skill when:
- Setting up Cloud Storage in a Flutter project.
- Uploading or downloading files.
- Managing file metadata.
- Handling Storage errors and monitoring upload progress.
1. Setup and Configuration
flutter pub add firebase_storage
import 'package:firebase_storage/firebase_storage.dart';
final storage = FirebaseStorage.instance;
// Or specify a bucket explicitly:
// final storage = FirebaseStorage.instanceFor(bucket: "gs://BUCKET_NAME");
- Firebase Storage requires the Blaze (pay-as-you-go) plan.
- Run
flutterfire configureto update your Firebase config with the default Storage bucket name.
> Security note: By default, a Cloud Storage bucket requires Firebase Authentication for any action. Configuring public access may also make App Engine files publicly accessible — restrict access again when you set up Authentication.
2. File Operations
Create a reference:
final storageRef = FirebaseStorage.instance.ref();
final fileRef = storageRef.child("uploads/file.jpg");
Upload:
final uploadTask = fileRef.putFile(file);
final snapshot = await uploadTask;
final downloadUrl = await snapshot.ref.getDownloadURL();
Download (in-memory):
final data = await fileRef.getData();
Download URL:
final downloadUrl = await fileRef.getDownloadURL();
Delete:
await fileRef.delete();
3. Metadata Management
Get metadata:
final metadata = await fileRef.getMetadata();
print('Content type: ${metadata.contentType}');
print('Size: ${metadata.size}');
Update metadata:
final newMetadata = SettableMetadata(
contentType: "image/jpeg",
customMetadata: {'uploaded_by': 'user123'},
);
await fileRef.updateMetadata(newMetadata);
Use custom metadata to store additional key/value pairs with your files.
4. Error Handling
Use try-catch with FirebaseException. Key error codes:
| Code | Meaning |
|---|---|
| storage/object-not-found | File doesn't exist at the reference |
| storage/bucket-not-found | No bucket configured for Cloud Storage |
| storage/project-not-found | No project configured for Cloud Storage |
| storage/quota-exceeded | Storage quota exceeded |
| storage/unauthenticated | User needs to authenticate |
| storage/unauthorized | User lacks permission |
| storage/retry-limit-exceeded | Operation timeout exceeded |
- For
quota-exceededon the Spark plan, upgrade to Blaze. - Implement retry logic for network-related errors and timeouts.
5. Performance and Best Practices
Monitor upload progress:
final uploadTask = fileRef.putFile(file);
uploadTask.snapshotEvents.listen((TaskSnapshot snapshot) {
print('Progress: ${(snapshot.bytesTransferred / snapshot.totalBytes) * 100}%');
});
- Cancel uploads with
uploadTask.cancel(). - Pause / resume with
uploadTask.pause()anduploadTask.resume(). - Optimize file sizes before upload to reduce costs and improve performance.
- Use Cloud Storage with Firestore for comprehensive data management.
- Use the Firebase Local Emulator Suite for local development and testing.
6. Security
- Use Firebase Security Rules to control access to files.
- Combine Storage rules with Firebase Authentication for user-based access control.
- Test security rules thoroughly before deploying to production.
References
Other skills for the same job
different authors, same section of the catalogue
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
This skill should be used when the user asks to "perform cloud penetration testing", "assess Azure or AWS or GCP security", "enumerate cloud resources", "exploit cloud misconfigurations", "test O365 security", "extract secrets from cloud environments", or "audit cloud infrastructure". It provides comprehensive techniques for security assessment across major cloud platforms.
You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies.
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
This skill should be used when the user asks to "escalate privileges on Linux", "find privesc vectors on Linux systems", "exploit sudo misconfigurations", "abuse SUID binaries", "exploit cron jobs for root access", "enumerate Linux systems for privilege escalation", or "gain root access from low-privilege shell". It provides comprehensive techniques for identifying and exploiting privilege escalation paths on Linux systems.
Expert malware analyst specializing in defensive malware research, threat intelligence, and incident response. Masters sandbox analysis, behavioral analysis, and malware family identification. Handles static/dynamic analysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage, threat hunting, incident response, or security research.
This skill should be used when the user asks to "use Metasploit for penetration testing", "exploit vulnerabilities with msfconsole", "create payloads with msfvenom", "perform post-exploitation", "use auxiliary modules for scanning", or "develop custom exploits". It provides comprehensive guidance for leveraging the Metasploit Framework in security assessments.
Expert in secure mobile coding practices specializing in input validation, WebView security, and mobile-specific security patterns. Use PROACTIVELY for mobile security implementations or mobile security code reviews.
How to use it
Take evanca/firebase-storage from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.