Framework-based guidance for hiring and scaling sales teams from zero to repeatable revenue.
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
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add refoundai/lenny-skills --skill building-sales-teamCompatible with
Supported agents
Emphasizes proving founder-led repeatability (50-100 at-bats at 15-25% win rate) before hiring any salespeople
Recommends always hiring sales reps in pairs to validate process and create performance baselines, not single hires
Matches sales archetypes (hunters for outbound, growers for inbound/PLG) to your specific motion and buyer profile
Delays VP of Sales hires until you have two reps c
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbuilding-sales-teamExecute the skills CLI command in your project's root directory to begin installation:
epx add refoundai/lenny-skills --skill building-sales-teamFetches building-sales-team from refoundai/lenny-skills 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:
.cursor/skills/building-sales-team
Restart Cursor to activate building-sales-team. Access via /building-sales-teamin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
high-end-visual-design
leonxlnx/taste-skill · Frontend · same category
ui-animation
mblode/agent-skills · Frontend · same category
premium-frontend-ui
github/awesome-copilot · Frontend · same category
frontend-ui-ux
code-yeongyu/oh-my-opencode · Frontend · same category
frontend-security
schalkneethling/webdev-agent-skills · Frontend · same category
html-to-pdf
aviz85/claude-skills-library · Frontend · same category
I recommend building-sales-team for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added building-sales-team from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
building-sales-team reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: building-sales-team is focused, and the summary matches what you get after install.
Keeps context tight: building-sales-team is the kind of skill you can hand to a new teammate without a long onboarding doc.
building-sales-team reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added building-sales-team from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
building-sales-team fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
building-sales-team is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for building-sales-team matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 58