Fetches axiom-core-location from charleswiltgen/axiom 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/axiom-core-location
Restart Cursor to activate axiom-core-location. Access via /axiom-core-location 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.
// First launch: "Can we have Always access?"manager.requestAlwaysAuthorization()
Right (5-10% denial rate):
// Start with When In UseCLServiceSession(authorization:.whenInUse)// Later, when user triggers background feature:CLServiceSession(authorization:.always)
Time cost: 15 min to fix code, but 30-60% of users permanently denied = feature adoption destroyed.
Why: Users deny aggressive requests. Start minimal, upgrade when user understands value.
Time cost: 10 min to add handling, prevents confused users.
Anti-Pattern 5: Wrong Accuracy for Use Case
Wrong (battery drain for weather app):
// Weather app using navigation accuracyCLLocationUpdate.liveUpdates(.automotiveNavigation)
Right (match accuracy to need):
// Weather: city-level is fineCLLocationUpdate.liveUpdates(.default)// or .fitness for runners// Navigation: needs high accuracyCLLocationUpdate.liveUpdates(.automotiveNavigation)
Use Case
Configuration
Accuracy
Battery
Navigation
.automotiveNavigation
~5m
Highest
Fitness tracking
.fitness
~10m
High
Store finder
.default
~10-100m
Medium
Weather
.default
~100m+
Low
Time cost: 1 min to change, significant battery savings.
Anti-Pattern 6: Not Stopping Updates
Wrong (battery drain, location icon persists):
funcviewDidLoad(){Task{fortryawait update inCLLocationUpdate.liveUpdates(){updateMap(update.location)}}}// User navigates away, updates continue forever
funcrequestAuth(){switch manager.authorizationStatus {case.notDetermined: manager.requestWhenInUseAuthorization()case.authorizedWhenInUse:if needsFullAccuracy { manager.requestTemporaryFullAccuracyAuthorization(...)}// Complex state machine...}}
Right (declarative goals):
// Just declare what you need - Core Location handles the restlet session =CLServiceSession(authorization:.whenInUse)// For feature needing full accuracylet navSession =CLServiceSession( authorization:.whenInUse, fullAccuracyPurposeKey:"Navigation")// Monitor diagnostics if neededfortryawait diag in session.diagnostics {if diag.authorizationDenied {handleDenial(
✓
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
