Relationship crm builder

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

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...From its SKILL.md

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.

One thing to look at

1 stars1 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.

SKILL.md

3.6 KB, 662 tokens by cl100k_base, 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.

What ships with it: 2 files

1.3 KB alongside SKILL.md

assets/

NOTE.md588 B

references/

NOTE.md732 B

Gives 0 of the 12 instructions most sales audience skills give in 662 tokens

Counted across 401 of the 401 authors here whose files we hold, read 2026-08-07

Read product marketing context before asking questionsin 21 of 401, across 11 files
Acknowledge competitor strengths honestlyin 18 of 401, across 7 files
Start every page with a summaryin 15 of 401, across 4 files
Use a single, low-friction call to actionin 15 of 401, across 7 files
Create a single source of truth for each competitorin 14 of 401, across 3 files
Make each follow-up email add new valuein 11 of 401, across 5 files
Cut any sentence that does not drive a replyin 10 of 401, across 4 files
Tie personalization directly to the problemin 10 of 401, across 4 files
Write paragraph comparisons for each dimensionin 9 of 401, across 3 files
Link between related competitor pagesin 9 of 401, across 3 files
Keep subject lines short and lowercasein 9 of 401, across 3 files
Define ideal customer profile from top customersin 9 of 401, across 3 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. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.