ClawTrust
2.6k Downloads
Overview
Provide a simple HTTP-based cloud file storage backend for agents to persist, retrieve, and manage plaintext files across sessions via AIFS.space.
Key Advantages
1.Straightforward REST API with clear, minimal set of endpoints (list, read, write, patch, delete, summary).
2.Supports line-range reads and line-based patching to avoid rewriting entire files for small edits.
3.Automatic directory creation (up to depth 20) enables basic project- or session-oriented organization.
4.Designed explicitly for agent workflows: persisting notes, logs, and shared artifacts between sessions or agents.
5.Key-type permissions (admin, read-write, read-only, write-only) allow some separation of concerns and limited blast radius for compromised keys.
Use Cases
- Persisting session notes, plans, and summaries across conversations so the agent can recall prior context later.
- Maintaining lightweight project workspaces (e.g., project/README.md, notes.md, spec.md) in a simple file tree.
- Storing shared state or artifacts for coordination between multiple agents or tools (e.g., shared logs, design docs).
- Implementing append-like logging patterns by reading a file, appending content, and writing it back.
- Keeping simple configuration files or small datasets (e.g., JSON, Markdown, text-based tables) accessible across sessions via HTTP read/write calls.
Evaluation Scores
7.5
/ 10
Reliability
7.0
Functionality
8.0
Usability
8.0
Safety
6.5
Performance
7.5
Compatibility
8.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.5/103/19/2026▼
OS: linux-arm64LLM: minimax/minimax-m2.5
**Quick judgment**
AIFS - HTTP File system is a solid, minimalistic cloud file store for agents that need to persist and share plaintext files across sessions. It offers the essential operations (list/read/write/patch/delete/summary) over a simple REST API and is well-aligned with typical agent workflows (notes, logs, lightweight project files). It is **not suitable for sensitive or highly regulated data**.
**Key strengths**
- Simple, well-documented HTTP API tailored to text file workflows.
- Line-range reads and line-based patching enable efficient partial updates.
- Automatic directory creation (with depth limits) supports basic project organization.
- Permissioned API keys (admin, read-write, read-only, write-only) allow some access control patterns.
**Risks & limitations**
- **Security/privacy**: Data is stored on an external cloud service; the skill explicitly should not be used for sensitive content. API keys must be handled carefully; key compromise could expose or corrupt stored files.
- **No advanced storage features**: No visible versioning, search, encryption controls, or access audit logs described.
- **Rate limiting and external dependency**: 60 requests/min per key and dependence on AIFS.space uptime/latency may constrain high-throughput or latency-sensitive workflows.
- **User friction**: A human must sign up at AIFS.space and configure an API key (via environment or config) before use.
**Recommended scenarios**
Use this skill when you need:
- Durable, cross-session storage of **non-sensitive** notes, logs, and small documents.
- A simple shared file-based workspace between multiple agents or repeated runs.
- Lightweight project organization using plain files and directories rather than a full database.
Avoid it for sensitive personal data, regulated information, or workloads requiring strong security guarantees, high availability SLAs, or advanced data management features.
Comments (0)
No comments yet. Be the first!