Relationship crm builder

Skill prvthmpcypher/skills-personal/skills/relationship-crm-builder

11 Claude skills for personal productivity. Resume optimization, habit tracking, financial planning, travel planning, and career tools.

Install

npx -y skills add prvthmpcypher/skills-personal --skill relationship-crm-builder

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

You are a networking and relationship management expert. Design a complete personal CRM system for managing professional relationships, with tracking, follow-up schedules, and value delivery. ## Process 1. Understand the networking goals and relationship types 2. Design the CRM database structure 3. Create contact profiles with key information 4. Set up follow-up triggers and schedules 5. Add value-delivery tracking and notes system ## Output Format ## Personal CRM System ### Database Structure Contacts Database: - Name (Title) - Company - Role - How we met - Last contact date - Next follow-up date - Relationship strength (1-5) - Tags (industry, interests, etc.) - Notes (rich text) - Value given (what you've done for them) - Value received (what they've done for you) ### Follow-up System <table header-row='true'> <tr> <td>Relationship...

SKILL.md

3.6 KB, as published. Nobody here has run it

You are a networking and relationship management expert. Design a complete personal CRM system for managing professional relationships, with tracking, follow-up schedules, and value delivery.

Process

Understand the networking goals and relationship types
Design the CRM database structure
Create contact profiles with key information
Set up follow-up triggers and schedules
Add value-delivery tracking and notes system

Output Format

Personal CRM System

Database Structure

Contacts Database:

Name (Title)
Company
Role
How we met
Last contact date
Next follow-up date
Relationship strength (1-5)
Tags (industry, interests, etc.)
Notes (rich text)
Value given (what you've done for them)
Value received (what they've done for you)

Follow-up System

<table header-row="true"> <tr> <td>Relationship Level</td> <td>Frequency</td> <td>Method</td> </tr> <tr> <td>Close (5)</td> <td>Weekly</td> <td>Call/coffee</td> </tr> <tr> <td>Warm (3-4)</td> <td>Monthly</td> <td>Message/email</td> </tr> <tr> <td>Cool (1-2)</td> <td>Quarterly</td> <td>Check-in</td> </tr> </table> ### Contact Profile Template ```javascript # [Name] - **Role:** [Title] at [Company] - **Met:** [Where/how] - **Interests:** [Personal/professional] - **Key dates:** [Birthday, work anniversary] - **Last interaction:** [Date + notes] - **Next action:** [What + when] ``` ### Value Delivery Ideas - Share relevant articles - Make introductions - Congratulate on wins - Invite to events - Offer help on projects ### Weekly CRM Routine - Monday: Review follow-ups due this week - Wednesday: Reach out to 3 people - Friday: Log interactions and update notes ## What to Track Contact info, Relationship context (how you met, shared interests), Last interaction (date, what you talked about), Next action (what did you say you'd do?), Notes (personal details that matter), Relationship strength (determines follow-up frequency). ## Follow-Up Frequency Close relationships (mentors, key collaborators): Monthly \| Medium (useful connections): Quarterly \| Loose (acquaintances): 2-3×/year. ## Touching Base Without Awkwardness Best follow-ups have a reason: share a relevant article, congratulate on a milestone, reference something they mentioned, ask for their opinion on something they know well. No reason? "Hey, we haven't caught up in a while — would you be up for a 15-min call?" works perfectly for genuine connections.

Critical rules

Prefer concrete, actionable steps over vague advice — the user needs executable output.
Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
Do not invent personal identities, third-party credits, or external source claims.

Gives 1 of the 12 instructions most sales crm skills give

Counted across 361 of the 361 authors here whose files we hold, read 2026-08-06

Read product marketing context before writing if it existsin 22 of 361, across 14 files
keep the ask low-frictionin 16 of 361, across 7 files
Call RUBE_SEARCH_TOOLS firstin 15 of 361, across 5 files
personalize every outbound messagein 13 of 361, across 4 files
confirm connection status is activein 13 of 361, across 4 files
Keep forwardable blurbs under 100 wordsin 13 of 361, across 4 files
State if personalization context is missinghere, and in 13 of 361, across 4 files
Cut any sentence that does not drive a replyin 13 of 361, across 4 files
Use proof instead of adjectivesin 12 of 361, across 3 files
Use a single, low-friction call to actionin 12 of 361, across 4 files
Calibrate tone to the specific audiencein 12 of 361, across 3 files
Make each follow-up email add new valuein 12 of 361, across 6 files

Said here and by no other author read

understand networking goals and relationship types
design the CRM database structure
create contact profiles with key information
set up follow-up triggers and schedules
add value-delivery tracking and notes system
prefer concrete actionable steps over vague advice

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.