Contentful Automation
Automate headless CMS operations in Contentful -- list spaces, retrieve space metadata, and update space configurations through the Composio Contentful integration.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Contentful Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate headless CMS operations in Contentful -- list spaces, retrieve space metadata, and update space configurations through the Composio Contentful integration.
When not to use it
Skip Contentful Automation when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/contentful-automation # Save SKILL.md to ~/.claude/skills/contentful-automation/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/contentful-automation/SKILL.md. For a shared project, commit the folder at .claude/skills/contentful-automation/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Contentful Automation skill for this task: Use Contentful Automation when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
63/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 67/100
- Practical detail
- 50/100
- Source evidence
- 63/100
- Source signals
- 80/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Contentful 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)*
Intended uses
- Use Contentful Automation when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.