/contentful-automation
Automate headless CMS operations in Contentful -- list spaces, retrieve space metadata, and update space configurations through the Composio Contentful integration.
$ npx -y skills add openteams-lab/openteams --skill contentful-automation --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/contentful-automation
Context preview
The summary Claude sees to decide when to auto-load this skill.
Automate headless CMS operations in Contentful -- list spaces, retrieve space metadata, and update space configurations through the Composio Contentful integration.
SKILL.md
contentful-automation.SKILL.mdname: Contentful Automation
description: "Automate headless CMS operations in Contentful -- list spaces, retrieve space metadata, and update space configurations through the Composio Contentful integration."
requires:
mcp:
- rubeContentful Automation
Manage your **Contentful** headless CMS spaces directly from Claude Code. List spaces, retrieve metadata, and update space configurations without leaving your terminal.
**Toolkit docs:** [composio.dev/toolkits/contentful](https://composio.dev/toolkits/contentful)
---
Setup
1. Add the Composio MCP server to your configuration:
https://rube.app/mcp
2. Connect your Contentful account when prompted. The agent will provide an authentication link. Ensure your access token has space management scopes.
---
Core Workflows
1. List All Spaces
Discover all Contentful spaces accessible to your authenticated account. This is typically the first operation since most other actions require a `space_id`.
**Tool:** `CONTENTFUL_LIST_SPACES`
Key parameters:
- `limit` (1-1000) -- maximum number of spaces to return (default: 100)
- `skip` -- number of spaces to skip for pagination
- `order` -- sort by field, e.g., `sys.createdAt` or `-sys.createdAt` for descending
Example prompt: *"List all my Contentful spaces"*
---
2. Get Space Details
Retrieve detailed metadata for a specific space including its current `sys.version`, which is required for updates.
**Tool:** `CONTENTFUL_GET_SPACE`
Key parameters:
- `space_id` (required) -- the ID of the space to retrieve (alphanumeric, 1-64 chars)
Example prompt: *"Get details for Contentful space abc123def"*
---
3. Update Space Name
Update the name of a specific space. Requires the current version number for optimistic locking to prevent concurrent modification conflicts.
**Tool:** `CONTENTFUL_UPDATE_SPACE`
Key parameters:
- `space_id` (required) -- ID of the space to update
- `name` (required) -- new name for the space (1-255 chars)
- `version` (required) -- current space version from `sys.version` (must be > 0)
Example prompt: *"Rename Contentful space abc123def to 'Production Content Hub'"*
---
4. Audit Space Inventory
Combine space listing and detail retrieval to audit your organization's Contentful spaces.
**Tools:** `CONTENTFUL_LIST_SPACES` then `CONTENTFUL_GET_SPACE`
Workflow: 1. List all spaces to get IDs and names 2. Fetch details for each space to get version info, creation dates, and metadata
Example prompt: *"Audit all Contentful spaces -- list them with their creation dates and current versions"*
---
Known Pitfalls
- **Version conflicts on update:** `CONTENTFUL_UPDATE_SPACE` requires the latest `sys.version` from `CONTENTFUL_GET_SPACE`. If someone else modified the space between your read and write, the update will fail with a version conflict. Always fetch the space immediately before updating.
- **Pagination for many spaces:** `CONTENTFUL_LIST_SPACES` uses `limit` and `skip` parameters. When you have many spaces, iterate by incrementing `skip` until no more results are returned to avoid missing spaces.
- **Scope limitations:** These tools only manage space-level metadata (names). They cannot create or modify entries, content types, or assets within a space.
- **Auth/permissions mismatch:** Updates via `CONTENTFUL_UPDATE_SPACE` will fail if your token lacks space management scopes, even if reads via `CONTENTFUL_GET_SPACE` succeed. Verify your token has write permissions.
- **Space ID format:** The `space_id` must match the pattern `^[a-zA-Z0-9-_.]{1,64}$`. Invalid characters will be rejected.
---
Quick Reference
| Tool Slug | Description | |---|---| | `CONTENTFUL_LIST_SPACES` | List all spaces accessible to your account | | `CONTENTFUL_GET_SPACE` | Retrieve detailed metadata for a single space | | `CONTENTFUL_UPDATE_SPACE` | Update the name of a space (requires version) |
---
*Powered by [Composio](https://composio.dev)*
Read more
name: Contentful Automation
description: "Automate headless CMS operations in Contentful -- list spaces, retrieve space metadata, and update space configurations through the Composio Contentful integration."
requires:
mcp:
- rubeContentful Automation
Manage your **Contentful** headless CMS spaces directly from Claude Code. List spaces, retrieve metadata, and update space configurations without leaving your terminal.
**Toolkit docs:** [composio.dev/toolkits/contentful](https://composio.dev/toolkits/contentful)
---
Setup
1. Add the Composio MCP server to your configuration:
https://rube.app/mcp
2. Connect your Contentful account when prompted. The agent will provide an authentication link. Ensure your access token has space management scopes.
---
Core Workflows
1. List All Spaces
Discover all Contentful spaces accessible to your authenticated account. This is typically the first operation since most other actions require a `space_id`.
**Tool:** `CONTENTFUL_LIST_SPACES`
Key parameters:
- `limit` (1-1000) -- maximum number of spaces to return (default: 100)
- `skip` -- number of spaces to skip for pagination
- `order` -- sort by field, e.g., `sys.createdAt` or `-sys.createdAt` for descending
Example prompt: *"List all my Contentful spaces"*
---
2. Get Space Details
Retrieve detailed metadata for a specific space including its current `sys.version`, which is required for updates.
**Tool:** `CONTENTFUL_GET_SPACE`
Key parameters:
- `space_id` (required) -- the ID of the space to retrieve (alphanumeric, 1-64 chars)
Example prompt: *"Get details for Contentful space abc123def"*
---
3. Update Space Name
Update the name of a specific space. Requires the current version number for optimistic locking to prevent concurrent modification conflicts.
**Tool:** `CONTENTFUL_UPDATE_SPACE`
Key parameters:
- `space_id` (required) -- ID of the space to update
- `name` (required) -- new name for the space (1-255 chars)
- `version` (required) -- current space version from `sys.version` (must be > 0)
Example prompt: *"Rename Contentful space abc123def to 'Production Content Hub'"*
---
4. Audit Space Inventory
Combine space listing and detail retrieval to audit your organization's Contentful spaces.
**Tools:** `CONTENTFUL_LIST_SPACES` then `CONTENTFUL_GET_SPACE`
Workflow: 1. List all spaces to get IDs and names 2. Fetch details for each space to get version info, creation dates, and metadata
Example prompt: *"Audit all Contentful spaces -- list them with their creation dates and current versions"*
---
Known Pitfalls
- **Version conflicts on update:** `CONTENTFUL_UPDATE_SPACE` requires the latest `sys.version` from `CONTENTFUL_GET_SPACE`. If someone else modified the space between your read and write, the update will fail with a version conflict. Always fetch the space immediately before updating.
- **Pagination for many spaces:** `CONTENTFUL_LIST_SPACES` uses `limit` and `skip` parameters. When you have many spaces, iterate by incrementing `skip` until no more results are returned to avoid missing spaces.
- **Scope limitations:** These tools only manage space-level metadata (names). They cannot create or modify entries, content types, or assets within a space.
- **Auth/permissions mismatch:** Updates via `CONTENTFUL_UPDATE_SPACE` will fail if your token lacks space management scopes, even if reads via `CONTENTFUL_GET_SPACE` succeed. Verify your token has write permissions.
- **Space ID format:** The `space_id` must match the pattern `^[a-zA-Z0-9-_.]{1,64}$`. Invalid characters will be rejected.
---
Quick Reference
| Tool Slug | Description | |---|---| | `CONTENTFUL_LIST_SPACES` | List all spaces accessible to your account | | `CONTENTFUL_GET_SPACE` | Retrieve detailed metadata for a single space | | `CONTENTFUL_UPDATE_SPACE` | Update the name of a space (requires version) |
---
*Powered by [Composio](https://composio.dev)*
Plan, Build, and Ship — with a team of AI agents instead of one
Repo: openteams-lab/openteams
Other skills on openteams.
- /ably-automation
Automate Ably tasks via Rube MCP (Composio). Always search tools first for current schemas.
Open skill - /abstract-automation
Automate Abstract tasks via Rube MCP (Composio). Always search tools first for current schemas.
Open skill - /abuselpdb-automation
Automate Abuselpdb tasks via Rube MCP (Composio). Always search tools first for current schemas.
Open skill - /abyssale-automation
Automate Abyssale tasks via Rube MCP (Composio). Always search tools first for current schemas.
Open skill - /accelo-automation
Automate Accelo tasks via Rube MCP (Composio). Always search tools first for current schemas.
Open skill - /accredible-certificates-automation
Automate Accredible Certificates tasks via Rube MCP (Composio). Always search tools first for current schemas.
Open skill

