persona-sales-ops
Sales workflow management with deal tracking, call scheduling, and client communication integration.
Works with
0
total installs
0
this week
23.9K
GitHub stars
0
upvotes
Install Skill
Run in your terminal
0
installs
0
this week
23.9K
stars
What it does
Requires four Google Workspace skills (Gmail, Calendar, Sheets, Drive) to operate as a unified sales operations persona
Includes five pre-built workflows: meeting prep, email-to-task conversion, weekly pipeline digests, deal logging, and proposal sharing
Supports deal tracking via spreadsheet append, client email filtering, and centralized Drive folder organization for proposals and d
Installation Guide
How to use persona-sales-ops on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
persona-sales-ops
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches persona-sales-ops from googleworkspace/cli and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate persona-sales-ops. Access via /persona-sales-ops 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.
Documentation
22:T51a,<h1>Sales Operations</h1>
<blockquote> <p><strong>PREREQUISITE:</strong> Load the following utility skills to operate as this persona: <code>gws-gmail</code>, <code>gws-calendar</code>, <code>gws-sheets</code>, <code>gws-drive</code></p> </blockquote> <p>Manage sales workflows — track deals, schedule calls, client comms.</p> <h2>Relevant Workflows</h2> <ul> <li><code>gws workflow +meeting-prep</code></li> <li><code>gws workflow +email-to-task</code></li> <li><code>gws workflow +weekly-digest</code></li> </ul> <h2>Instructions</h2> <ul> <li>Prepare for client calls with <code>gws workflow +meeting-prep</code> to review attendees and agenda.</li> <li>Log deal updates in a tracking spreadsheet with <code>gws sheets +append</code>.</li> <li>Convert follow-up emails into tasks with <code>gws workflow +email-to-task</code>.</li> <li>Share proposals by uploading to Drive with <code>gws drive +upload</code>.</li> <li>Get a weekly sales pipeline summary with <code>gws workflow +weekly-digest</code>.</li> </ul> <h2>Tips</h2> <ul> <li>Use <code>gws gmail +triage --query 'from:client-domain.com'</code> to filter client emails.</li> <li>Schedule follow-up calls immediately after meetings to maintain momentum.</li> <li>Keep all client-facing documents in a dedicated shared Drive folder.</li> </ul>1d:["$","div",null,{"className":"prose prose-invert max-w-none prose-headings:font-semibold prose-headings:tracking-tight prose-h1:text-4xl prose-h1:mb-2 prose-h2:text-2xl prose-h2:mb-2 prose-h3:text-lg prose-h3:mb-2 prose-p:text-muted-foreground prose-li:text-muted-foreground prose-code:bg-muted prose-code:text-foreground prose-code:px-1 prose-code:py-0.5 prose-code:rounded-sm prose-code:text-sm prose-code:before:content-none prose-code:after:content-none prose-pre:bg-muted prose-pre:text-foreground prose-pre:border prose-pre:border-border prose-pre:rounded-md [&_table]:!border-[color:var(--border)] [&_th]:!border-[color:var(--border)] [&_td]:!border-[color:var(--border)]","dangerouslySetInnerHTML":{"__html":"$22"}}] 18:[["$","meta","0",{"charSet":"utf-8"}],["$","meta","1",{"name":"viewport","content":"width=device-width, initial-scale=1"}]] 16:nullList & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›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
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
388mattpocock/skills
premortem
197parcadei/continuous-claude-v3
deslop
118cursor/plugins
framer-motion
99pproenca/dot-skills
write-a-prd
91mattpocock/skills
travel-planner
90ailabs-393/ai-labs-claude-skills
Reviews
- DDhruvi Jain★★★★★Dec 24, 2024
Useful defaults in persona-sales-ops — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- FFatima Robinson★★★★★Dec 20, 2024
persona-sales-ops has been reliable in day-to-day use. Documentation quality is above average for community skills.
- OOshnikdeep★★★★★Nov 15, 2024
persona-sales-ops is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- EEmma Garcia★★★★★Nov 11, 2024
persona-sales-ops fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- GGanesh Mohane★★★★★Oct 6, 2024
Keeps context tight: persona-sales-ops is the kind of skill you can hand to a new teammate without a long onboarding doc.
- KKaira Torres★★★★★Oct 2, 2024
We added persona-sales-ops from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- SSakshi Patil★★★★★Sep 25, 2024
persona-sales-ops has been reliable in day-to-day use. Documentation quality is above average for community skills.
- EEmma Liu★★★★★Sep 21, 2024
persona-sales-ops reduced setup friction for our internal harness; good balance of opinion and flexibility.
- JJames Li★★★★★Sep 1, 2024
I recommend persona-sales-ops for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- EEmma Kapoor★★★★★Aug 20, 2024
Useful defaults in persona-sales-ops — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 34
Discussion
Comments — not star reviews- No comments yet — start the thread.