Name the task
A useful package name says what the skill helps users do: review pull requests, summarize Sentry issues, draft release notes, or plan migrations.
Discoverability
Help users find and understand your skill.
Good discoverability is not keyword stuffing. Use clear names, accurate descriptions, real examples, and safe public content.
Write for people
Explain when to use the skill, which tools it supports, what output to expect, and what files it installs. Avoid vague claims like smarter workflow.
Use honest keywords
Mention tools and workflows only when they are true: Cursor skill, Claude skill, prompt package, code review assistant, or incident summary skill.
Show examples
A real install command, a short example, and a list of included files help users understand the package.
Explain versions
Users need to trust what they install. Explain behavior changes, compatibility, and old releases clearly.
Do not leak private details
Do not include private prompts, customer data, secret names, API keys, or internal documents. Public packages must be safe to inspect.
Page quality checklist
Every important page should help users before they sign in. Pages should explain the topic, link to the next step, and make install or publish actions easy to find.
- One clear H1 that describes the page purpose.
- A concise meta description with the main user intent.
- Canonical URL, sitemap entry, and readable internal links.
- Structured data when the page is an article, FAQ, collection, or package detail.
- Fast static rendering where possible, with live registry data loaded separately.
- Useful text on the page, not only cards, icons, or JavaScript-rendered shells.
How to write package metadata
A package description should answer four questions: what task the skill helps with, which AI tools it supports, what files it installs, and what happens after install.
Good:
"Summarizes Sentry desktop app issues into triage notes for Cursor and Claude, with project rules and a reusable issue template."
Weak:
"AI-powered productivity helper for better workflows."What AIPM should keep improving
AIPM should keep adding helpful public pages for real user needs: installing skills, publishing skills, Cursor and Claude setup, safety, team workflows, troubleshooting, and package examples.