contentful-api
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: contentful-api
description: Comprehensive Contentful REST API guide. Covers Content Management API (CMA) for creating/updati…
category: engineering
runtime: no special runtime
---
# contentful-api output preview
## PART A: Task fit
- Use case: Comprehensive Contentful REST API guide. Covers Content Management API (CMA) for creating/updating content, Content Delivery API (CDA) for fetching published content, Preview API, Images API, and GraphQL API. All examples use curl/HTTP — language-agnostic. Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Shared References / Content Management API (CMA) / Content Delivery API (CDA)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Comprehensive Contentful REST API guide. Covers Content Management API (CMA) for creating/updating content, Content Delivery API (CDA) for fetching published content, Preview API, Images API, and GraphQL API. All examples use curl/HTTP — language-agnostic. Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “Shared References / Content Management API (CMA) / Content Delivery API (CDA)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Shared References / Content Management API (CMA) / Content Delivery API (CDA)”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: contentful-api
description: Comprehensive Contentful REST API guide. Covers Content Management API (CMA) for creating/updati…
category: engineering
source: tomevault-io/skills-registry
---
# contentful-api
## When to use
- Comprehensive Contentful REST API guide. Covers Content Management API (CMA) for creating/updating content, Content De…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Shared References / Content Management API (CMA) / Content Delivery API (CDA)” and keep inference separate from source facts.
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "contentful-api" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Shared References / Content Management API (CMA) / Content Delivery API (CDA)
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Contentful REST API Guide
Language-agnostic guide for Contentful APIs using HTTP/curl.
Shared References
- Authentication — Token types, auth headers, API base URLs (US/EU)
- HTTP Conventions — Version locking, rate limits, pagination, errors, locale structure
Content Management API (CMA)
Read/write API for managing content, content types, assets, and environments.
Start here: references/content-management/overview.md
- entries.md — CRUD, publish/unpublish, versioning, query parameters
- content-types.md — Define/update content models, field types, validations
- assets.md — Upload, process, publish media files
- environments.md — Create, clone, manage environments and aliases
Content Delivery API (CDA)
Read-only API for fetching published content.
Start here: references/content-delivery/overview.md
- querying.md — Filters, search operators, pagination, ordering
- includes-links.md — Include parameter, link resolution
- localization.md — Locale parameter, fallback chains
- sync.md — Incremental content synchronization
Content Preview API
Draft + published content via same CDA endpoints, different host/token.
Reference: references/content-preview/overview.md
Images API
On-the-fly image transformations via URL parameters. No authentication needed.
Reference: references/images/overview.md
GraphQL API
Query content via GraphQL with CDA tokens.
Reference: references/graphql/overview.md
Quick Reference
# CMA: Create a draft entry
curl -X POST https://api.contentful.com/spaces/{space_id}/environments/{env_id}/entries \
-H "Authorization: Bearer {cma_token}" \
-H "Content-Type: application/vnd.contentful.management.v1+json" \
-H "X-Contentful-Content-Type: blogPost" \
-d '{"fields":{"title":{"en-US":"Hello"}}}'
# Then publish: PUT .../entries/{id}/published with X-Contentful-Version header
# CDA: Fetch entries
curl "https://cdn.contentful.com/spaces/{space_id}/environments/{env_id}/entries?content_type=blogPost" \
-H "Authorization: Bearer {cda_token}"
Source: contentful/skills — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review