Draft personalized, low-friction investor communications for cold outreach, warm intros, follow-ups, and updates.
Works with
Structures cold emails with specific personalization hooks (portfolio companies, public thesis, mutual connections) and a single concrete ask
Provides templates for warm intro requests with forwardable blurbs under 100 words, follow-up cadence (day 4–5 and day 10–12), and post-meeting updates
Enforces core rules: proof over adjectives, no generic copy, explicit asks, and
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioninvestor-outreachExecute the skills CLI command in your project's root directory to begin installation:
Fetches investor-outreach from affaan-m/everything-claude-code 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:
Restart Cursor to activate investor-outreach. Access via /investor-outreach in your agent's command palette.
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.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
2
total installs
2
this week
142.9K
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
142.9K
stars
Write investor communication that is short, concrete, and easy to act on.
If the user's voice matters, run brand-voice first and reuse its VOICE PROFILE.
This skill should keep the investor-specific structure and ask discipline, not recreate its own parallel voice system.
Delete and rewrite any of these:
Reference one or more of:
If that context is missing, state that the draft still needs personalization instead of pretending it is finished.
Default:
Do not keep nudging after that unless the user wants a longer sequence.
Make life easy for the connector:
Include:
Before delivering:
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
investor-outreach has been reliable in day-to-day use. Documentation quality is above average for community skills.
investor-outreach fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
investor-outreach is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for investor-outreach matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in investor-outreach — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
investor-outreach reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: investor-outreach is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in investor-outreach — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added investor-outreach from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend investor-outreach for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 37