You are an expert Strapi v5 developer specializing in plugin development, custom APIs, and CMS architecture. Your mission is to write production-grade Strapi v5 code following official conventions and best practices.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionstrapi-expertExecute the skills CLI command in your project's root directory to begin installation:
Fetches strapi-expert from mkshahzad77/claude-skill-strapi-expert and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate strapi-expert. Access via /strapi-expert in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
4
total installs
4
this week
2
GitHub stars
0
upvotes
Run in your terminal
4
installs
4
this week
2
stars
You are an expert Strapi v5 developer specializing in plugin development, custom APIs, and CMS architecture. Your mission is to write production-grade Strapi v5 code following official conventions and best practices.
In Strapi v5, always use the Document Service API (strapi.documents) for all data operations. The Entity Service API from v4 is deprecated.
| Operation | Document Service (v5) | Entity Service (deprecated) |
|---|---|---|
| Find many | strapi.documents('api::article.article').findMany() |
strapi.entityService.findMany() |
| Find one | strapi.documents(uid).findOne({ documentId }) |
strapi.entityService.findOne() |
| Create | strapi.documents(uid).create({ data }) |
strapi.entityService.create() |
| Update | strapi.documents(uid).update({ documentId, data }) |
strapi.entityService.update() |
| Delete | strapi.documents(uid).delete({ documentId }) |
strapi.entityService.delete() |
| Publish | strapi.documents(uid).publish({ documentId }) |
N/A |
| Unpublish | strapi.documents(uid).unpublish({ documentId }) |
N/A |
// In a service or controller
const articles = await strapi.documents('api::article.article').findMany({
filters: { publishedAt: { $notNull: true } },
populate: ['author', 'categories'],
locale: 'en',
status: 'published', // 'draft' | 'published'
});
// Create with draft/publish support
const newArticle = await strapi.documents('api::article.article').create({
data: {
title: 'My Article',
content: 'Content here...',
},
status: 'draft', // Creates as draft
});
// Publish a draft
await strapi.documents('api::article.article').publish({
documentId: newArticle.documentId,
});
A Strapi v5 plugin follows this structure:
my-plugin/
├── package.json # Must have strapi.kind: "plugin"
├── strapi-server.js # Server entry point
├── strapi-admin.js # Admin entry point
├── server/
│ └── src/
│ ├── index.ts # Main server export
│ ├── register.ts # Plugin registration
│ ├── bootstrap.ts # Bootstrap logic
│ ├── destroy.ts # Cleanup logic
│ ├── config/
│ │ └── index.ts # Default config
│ ├── content-types/
│ │ └── my-type/
│ │ └── schema.json
│ ├── controllers/
│ │ └── index.ts
│ ├── routes/
│ │ └── index.ts
│ ├── services/
│ │ └── index.ts
│ ├── policies/
│ │ └── index.ts
│ └── middlewares/
│ └── index.ts
└── admin/
└── src/
├── index.tsx # Admin entry
├── pages/
├── components/
└── translations/
{
"name": "my-plugin",
"version": "1.0.0",
"strapi": {
"kind": "plugin",
"name": "my-plugin",
"displayName": "My Plugin"
}
}
// server/src/routes/index.ts
export default {
'content-api': {
type: 'content-api',
routes: [
{
method: 'GET',
path: '/items',
handler: 'item.findMany',
config: {
policies: [],
auth: false, // Public access
},
},
{
method: 'POST',
path: '/items',
handler: 'item.create',
config: {
policies: ['is-owner'],
},
},
],
},
};
export default {
admin: {
type: 'admin',
routes: [
{
method: 'GET',
path: '/settings',
handler: 'settings.getSettings',
config: {
policies: ['admin::isAuthenticatedAdmin'],
},
},
],
},
};
// server/src/controllers/item.ts
import type { Core } from '@strapi/strapi';
const controller = ({ strapi }: { strapi: Core.Strapi }) => ({
async findMany(ctx) {
const items = await strapi
.documents('plugin::my-plugin.item')
.findMany({
filters: ctx.query.filters,
populate: ctx.query.populate,
});
return { data: items };
},
async create(ctx) {
const { data } = ctx.request.body;
const item = await strapi
.documents('plugin::my-plugin.item')
.create({ data });
return { data: item };
},
});
export default controller;
// server/src/services/item.ts
import type { Core } from '@strapi/strapi';
const service = ({ strapi }: { strapi: Core.Strapi }) => ({
async findPublished(locale = 'en') {
return strapi.documents('plugin::my-plugin.item').findMany({
status: 'published',
locale,
});
},
async publishItem(documentId: string) {
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
python-expert-best-practices-code-review
47wispbit-ai/skills
Backendtag: expertpython-expert
27shubhamsaboo/awesome-llm-apps
Backendtag: expertfastapi-expert
19jeffallan/claude-skills
Backendtag: expertdjango-expert
15jeffallan/claude-skills
Backendtag: expertantigravity-design-expert
209sickn33/antigravity-awesome-skills
Frontendtag: expertinterior-design-expert
145erichowens/some_claude_skills
Frontendtag: expertReviews
4.6★★★★★47 reviews- JJin Lopez★★★★★Dec 28, 2024
We added strapi-expert from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- AAdvait Gill★★★★★Dec 24, 2024
strapi-expert reduced setup friction for our internal harness; good balance of opinion and flexibility.
- LLucas Huang★★★★★Dec 12, 2024
strapi-expert is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- RRahul Santra★★★★★Nov 27, 2024
Solid pick for teams standardizing on skills: strapi-expert is focused, and the summary matches what you get after install.
- IIsabella Garcia★★★★★Nov 19, 2024
strapi-expert fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- LLucas Choi★★★★★Nov 15, 2024
Registry listing for strapi-expert matched our evaluation — installs cleanly and behaves as described in the markdown.
- MMin Chen★★★★★Nov 3, 2024
Useful defaults in strapi-expert — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- IIsabella Zhang★★★★★Oct 22, 2024
Registry listing for strapi-expert matched our evaluation — installs cleanly and behaves as described in the markdown.
- PPratham Ware★★★★★Oct 18, 2024
I recommend strapi-expert for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- IIsabella Liu★★★★★Oct 10, 2024
strapi-expert has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 47
1 / 5Discussion
Comments — not star reviews- No comments yet — start the thread.