Run any Skill in Manus with one click

data-store-object-storage

Stars0

Forks0

UpdatedApril 27, 2026 at 12:24

ALWAYS load this skill before any S3 or Azure Blob Storage operation — even for simple uploads or listings. Skipping it is a leading cause of failures from mixing up provider field names, missing sourceType/sourceValue on uploads, and using wrong method semantics for list versus get. Use when working with Amazon S3 or Azure Blob Storage. Applies to listing objects, downloading content, retrieving metadata, uploading, overwriting, and deleting objects. This skill mandates: (1) reading the provider-specific payload reference before constructing any request — S3 uses bucket and key while Azure uses container and blob, mixing them will fail, (2) using SELECT for prefix-based listing and GET for single-object retrieval — these are different operations, (3) always providing sourceType and sourceValue for INSERT and UPDATE operations, and (4) using the schema tool for bucket/container metadata, not for relational schema discovery. Co-load with domain skills; this skill governs payload structure. Both are required.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

TheColorRed

TheColorRed/data-store-mcp

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

13 files

SKILL.md

readonly

name

data-store-object-storage

description

ALWAYS #tool:read/readFile these additional instructions to understand the Data Store flow. Use the tools in the correct order to operate on object storage resources.

ALWAYS #tool:read/readFile AWS S3 payload instructions before constructing any payload for S3. The field names and requirements differ between providers, and using the wrong format will lead to errors.

ALWAYS #tool:read/readFile Azure Blob Storage payload instructions before constructing any payload for Azure Blob Storage. The field names and requirements differ between providers, and using the wrong format will lead to errors.

Object Storage

Use this skill when the user needs to inspect or manage objects in cloud object storage such as Amazon S3 or Azure Blob Storage. This skill covers common object storage workflows such as listing content, downloading files, uploading new objects, replacing existing objects, and deleting storage items. It is designed for operations that are centered on object resources rather than relational tables or document records.

When To Use

Use this skill when the user wants to list, download, upload, replace, or delete objects in a bucket or container. It should be selected whenever the problem is about object-level storage operations rather than standard database queries. This skill also applies when the user explicitly mentions Amazon S3 or Azure Blob Storage, or when they need metadata, signed URLs, or content from a cloud object store.

Use this skill when the user wants to list, download, upload, replace, or delete objects in a bucket or container.
Use this skill when the user needs metadata, signed URLs, or content from object storage.
Use this skill for both Amazon S3 and Azure Blob Storage operations.

Tool Usage

The object storage skill uses the shared data store toolset to map storage methods to the appropriate tool operations. Each tool corresponds to a concrete storage action, and using the correct tool helps keep payload construction consistent. Rely on these tool mappings when responding to requests about object storage operations.

Use the #tool:data-store/select tool to get the object content or metadata.
Use the #tool:data-store/insert tool to upload an object (INSERT).
Use the #tool:data-store/update tool to overwrite an object (UPDATE).
Use the #tool:data-store/delete tool to remove an object (DELETE).
Use the #tool:data-store/mutation tool as a generic alias for INSERT, UPDATE, DELETE, GET, and SELECT.
Use the #tool:data-store/schema tool to get metadata for the bucket/container and objects.

Provider Notes

Provider-specific naming matters because Amazon S3 and Azure Blob Storage use different field names for the same logical concepts. This section describes how each provider maps the shared object storage model to its own payload fields. Understanding these differences reduces errors and helps the agent choose the correct payload format.

Amazon S3 uses bucket and key; Azure Blob Storage uses container and blob.
The same methods apply to both providers, but the exact field names differ.
SELECT is a listing operation. For S3, key is optional and acts as a prefix when provided; omitting key lists from the bucket root. For Azure Blob, blob is optional and acts as a prefix filter.
GET, INSERT, UPDATE, and DELETE identify a single object and require an exact object path.
INSERT and UPDATE always require both sourceType and sourceValue. When sourceType is path, the MIME type is detected automatically from the file extension.
S3 GET returns a signedUrl pre-signed for one hour in addition to the object body and metadata.
Azure Blob DELETE returns a succeeded flag and an errorCode; it does not throw on a missing blob.
If the connection provides a default bucket or container, that field may be omitted from the payload.

Object Storage Payload

The provider-specific payload instructions contain the exact fields and requirements for each supported storage service. Always consult the instructions before generating the final payload, because they explain required fields, optional fields, and method-specific behavior. These references are the authoritative source for field names and shape expectations.

Example Assets

Example payload files are included to show concrete request shapes for each operation and provider. Review the examples before building a payload so you can confirm the correct field names and minimal required properties. These assets are helpful as templates for both Amazon S3 and Azure Blob Storage requests.

More from this repository

same repository

data-store-document

TheColorRed/data-store-mcp

ALWAYS load this skill before any MongoDB or NoSQL document operation — even if the query looks simple. Skipping it is a leading cause of failures from wrong method names, missing required fields, and malformed filter payloads. Use when working with NoSQL document data sources, currently MongoDB. Applies to querying, inserting, updating, deleting documents, and inspecting collections. This skill mandates: (1) reading the payload reference before constructing any request so required fields like filter, value, and tableName are set correctly, (2) using the schema tool to discover collection names before querying when they are not already confirmed, (3) routing reads to select and writes to insert/update/delete rather than defaulting everything to mutation, and (4) using listTables for a lightweight collection list instead of a full schema fetch. Co-load with domain skills — they provide context; this skill governs payload structure and routing. They are complementary, not interchangeable.

2026-04-270

data-store-ftp

TheColorRed/data-store-mcp

ALWAYS load this skill before any FTP operation — even for simple file reads or directory listings. Skipping it is a leading cause of failures from missing remote path fields, wrong method values, and malformed upload payloads. Use when working with FTP servers to list directories, read file contents, upload new files, overwrite existing files, or delete remote files. This skill mandates: (1) reading the payload reference before constructing any request so required path and method fields are set correctly, (2) using select with the correct method for directory listing versus file content retrieval — these are different operations, (3) always providing a sourceValue and sourceType for upload and overwrite operations, and (4) preferring dedicated CRUD tools over mutation unless no specific tool fits. REST and object storage patterns do not apply to FTP. Co-load with domain skills — they provide context; this skill governs payload structure. They are complementary, not interchangeable.

2026-04-270

data-store-graphql

TheColorRed/data-store-mcp

ALWAYS load this skill before any GraphQL operation — even if you are familiar with the GraphQL query language. Skipping it is a leading cause of failures from wrong tool routing, missing variables fields, and treating GraphQL like a REST endpoint. Use when working with GraphQL APIs to run queries, send mutations, or inspect responses. This skill mandates: (1) reading the payload reference before constructing any operation so the query string, variables, and headers are shaped correctly, (2) routing all read/list/search GraphQL queries to the select tool — not mutation, (3) routing all GraphQL mutations to the mutation tool — not insert/update/delete unless they are aliases, and (4) never using REST payload guidance for a GraphQL endpoint even if it is served over HTTP. GraphQL is not REST — REST patterns produce invalid requests. Co-load with domain skills — they provide context; this skill governs operation authoring and routing. They are complementary, not interchangeable.

2026-04-270

data-store-operations

TheColorRed/data-store-mcp

ALWAYS load this skill when tool routing is ambiguous, a request fails, or you are unsure which provider tool to call — regardless of which data source is involved. Skipping it is a leading cause of repeated failed tool calls, unnecessary schema fetches, and inconsistent error responses. Use for cross-provider operational workflow guidance covering SQL, document, key-value, REST, GraphQL, FTP, and object storage. This skill mandates: (1) reading the tool-routing reference before making any tool call when the correct tool is not obvious, (2) following the schema-first execution flow when payload shape or table/collection details are uncertain, (3) applying the deterministic error recovery steps after any tool failure before retrying, and (4) formatting all results and errors to the response standards defined in this skill. This is a meta-skill — layer it on top of provider-specific skills. Layer this alongside provider skills — they govern payloads; this skill governs routing and recovery. Both are required.

2026-04-270

data-store-rest

TheColorRed/data-store-mcp

ALWAYS load this skill before any REST API operation — even for simple GET requests. Skipping it is a leading cause of failures from wrong tool routing, missing required payload fields like endpoint and method, and conflating REST with GraphQL for HTTP-based connections. Use when working with REST APIs to send GET, POST, PUT, PATCH, DELETE, or custom HTTP method requests. This skill mandates: (1) reading the payload reference before constructing any request so endpoint, method, headers, body, and query parameters are shaped correctly, (2) mapping HTTP verbs to the correct tools — GET to select, POST to insert, PUT to update, DELETE to delete, any other method to mutation, (3) never using GraphQL payload structure for a REST endpoint even if both are served over HTTP, and (4) never using SQL or document guidance when the data source is an HTTP API. Provide endpoint and method or the request will fail. Co-load with domain skills — they provide context; this skill governs request structure. Both are required.

2026-04-270

data-store-sql

TheColorRed/data-store-mcp

ALWAYS load this skill before any SQL operation — even if you already know SQL syntax. Skipping it is a leading cause of query failures from wrong column names, wrong quoting, and missing params. Use when working with relational SQL databases: MySQL, MariaDB, MSSQL, PostgreSQL, or SQLite. Applies to SELECT, INSERT, UPDATE, DELETE, DDL, and stored procedures. This skill mandates: (1) inspecting schema before querying when table/column details are not already confirmed, (2) parameterized queries with a params array — never interpolate values into SQL strings, (3) dialect-specific identifier quoting and syntax per provider, and (4) routing CRUD to dedicated tools and DDL/procedures to mutation. MariaDB uses the MySQL connector. Familiarity with SQL does not replace this skill — it enforces correctness and safety patterns that prevent the most common failures. Co-load with any domain skill — domain skills provide context; this skill governs SQL authoring and routing. They are complementary, not interchangeable.

2026-04-270

name

data-store-object-storage

description

ALWAYS #tool:read/readFile these additional instructions to understand the Data Store flow. Use the tools in the correct order to operate on object storage resources.

Object Storage

When To Use

Use this skill when the user wants to list, download, upload, replace, or delete objects in a bucket or container.
Use this skill when the user needs metadata, signed URLs, or content from object storage.
Use this skill for both Amazon S3 and Azure Blob Storage operations.

Tool Usage

Use the #tool:data-store/select tool to get the object content or metadata.
Use the #tool:data-store/insert tool to upload an object (INSERT).
Use the #tool:data-store/update tool to overwrite an object (UPDATE).
Use the #tool:data-store/delete tool to remove an object (DELETE).
Use the #tool:data-store/mutation tool as a generic alias for INSERT, UPDATE, DELETE, GET, and SELECT.
Use the #tool:data-store/schema tool to get metadata for the bucket/container and objects.

Provider Notes

Amazon S3 uses bucket and key; Azure Blob Storage uses container and blob.
The same methods apply to both providers, but the exact field names differ.
SELECT is a listing operation. For S3, key is optional and acts as a prefix when provided; omitting key lists from the bucket root. For Azure Blob, blob is optional and acts as a prefix filter.
GET, INSERT, UPDATE, and DELETE identify a single object and require an exact object path.
INSERT and UPDATE always require both sourceType and sourceValue. When sourceType is path, the MIME type is detected automatically from the file extension.
S3 GET returns a signedUrl pre-signed for one hour in addition to the object body and metadata.
Azure Blob DELETE returns a succeeded flag and an errorCode; it does not throw on a missing blob.
If the connection provides a default bucket or container, that field may be omitted from the payload.