Fetches add-provider-package from vercel/ai and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/add-provider-package
Restart Cursor to activate add-provider-package. Access via /add-provider-package in your agent's command palette.
⚠
Security Notice
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.
Add feature-specific examples as needed (e.g., <provider>-tool-call.ts, <provider>-cache-control.ts).
11. Add Documentation
Create documentation in content/providers/01-ai-sdk-providers/<last number + 10>-<provider>.mdx
Include:
Setup instructions
Available models
Model capabilities
Provider-specific options
Usage examples
API configuration
12. Create Changeset
Run pnpm changeset and:
Select the new provider package
Choose major version (for new packages starting at 0.0.0)
Describe what the package provides
13. Update References
Run pnpm update-references from the workspace root to update tsconfig references.
14. Build and Test
# From workspace rootpnpm build
# From provider packagecd packages/<provider>pnpmtest# Run all testspnpm test:node # Run Node.js testspnpm test:edge # Run Edge testspnpm type-check # Type checking# From workspace rootpnpm type-check:full # Full type check including examples
15. Run Examples
Test your examples:
cd examples/ai-functions
pnpm tsx src/generate-text/<provider>.ts
pnpm tsx src/stream-text/<provider>.ts
Provider Method Naming
Full names: languageModel(id), imageModel(id), embeddingModel(id) (required)
Short aliases: .chat(id), .image(id), .embedding(id) (for DX)
File Naming Conventions
Source files: kebab-case.ts
Test files: kebab-case.test.ts
Type test files: kebab-case.test-d.ts
Provider classes: <Provider>Provider, <Provider>LanguageModel, etc.
Security Best Practices
Never use JSON.parse directly - use parseJSON or safeParseJSON from @ai-sdk/provider-utils
Load API keys securely using loadApiKey from @ai-sdk/provider-utils
Validate all API responses against schemas
Error Handling
Errors should extend AISDKError from @ai-sdk/provider and use a marker pattern:
import{ AISDKError }from'@ai-sdk/provider';const name
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
