Individual skill
Headless CMS GraphQL Connector
Connects headless CMS backends (WordPress WPGraphQL, Strapi, Contentful) to frontend frameworks using Apollo Client and urql. Handles content previews, ISR cache invalidation, and webhook-driven rebuilds.
skills/headless-cms-graphql-connector/SKILL.md
Source commit fc97377adefd53e861c1d456aa1392e4a4e022a2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
Repository context
- Repository stars (not skill ratings)
- 62
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- codex Repository topic
- cursor Repository topic
- npx-skills Repository topic
- openclaw Repository topic
- ai-tools Repository topic
- mcp Repository topic
- awesome-list Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,124 bytes
Read excerpt
# Headless CMS GraphQL Connector
Connects headless CMS backends (WordPress WPGraphQL, Strapi, Contentful) to frontend frameworks using Apollo Client and urql. Handles content previews, ISR cache invalidation, and webhook-driven rebuilds.
## Installation
Requirements and caveats from upstream:
- When creating a GraphQL document we always start with a root operation type (the Query Object type for this example) because it serves as an entry point to the API. From there we must specify the selection set of fiel...
- Variable definitions can be optional or required. In the case above, since there isn’t an ! next to the Episode type, it’s optional. But if the field you are passing the variable into requires a non-null argument, the...
Basic usage or getting-started notes:
- In the previous example, we just asked for the name of our hero which returned a String , but fields can also return Object types (and lists thereof). In that case, you can make a sub-selection of fields for that Obje...
- Note that in this example, the friends field returns an array of items. GraphQL queries look the same for single items or lists of items; however, we know which one to expect based on what is indicated in the schema.
- Arguments can be of many different types. In the above example, we have used an Enum type, which represents one of a finite set of options (in this case, units of length, either METER or FOOT ). GraphQL comes with a d...