reference-list-builder▌
paramchoudhary/resumeskills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Use this skill when the user:
Reference List Builder
When to Use This Skill
Use this skill when the user:
- Needs to create a professional reference list
- Wants help choosing the right references
- Needs to format references properly
- Is preparing references for job applications
- Mentions: "references", "reference list", "professional references", "reference check"
Core Capabilities
- Format professional reference lists
- Guide reference selection strategy
- Prepare reference briefing materials
- Anticipate reference check questions
- Handle difficult reference situations
- Coordinate reference outreach
Reference Strategy
Who Makes a Good Reference?
Ideal References:
- Former direct managers (most important)
- Senior colleagues who observed your work
- Cross-functional partners
- Clients or customers
- Direct reports (for leadership roles)
- Professors or advisors (for recent graduates)
Reference Hierarchy:
- Most Valuable: Recent direct supervisor
- Very Valuable: Senior leaders who know your work
- Valuable: Peers and cross-functional partners
- Acceptable: Clients, vendors, professors
- Avoid: Friends, family, HR contacts only
Who to Avoid
- ❌ Current employer (without permission)
- ❌ People who barely know you
- ❌ References from 10+ years ago only
- ❌ Personal friends (unless specified)
- ❌ People who might give lukewarm feedback
- ❌ Anyone you haven't contacted in advance
Reference List Format
Standard Format
PROFESSIONAL REFERENCES
Jane Smith
Senior Director of Product
TechCorp Inc.
Phone: (555) 123-4567
Email: [email protected]
Relationship: Direct supervisor for 3 years (2020-2023)
John Doe
VP of Engineering
Previous Company
Phone: (555) 234-5678
Email: [email protected]
Relationship: Cross-functional partner on 5 major projects
Information to Include
Required:
- Full name
- Current job title
- Current company
- Phone number
- Professional email
- Your relationship to them
Optional:
- LinkedIn URL
- Best time to reach
- Preferred contact method
Formatting Guidelines
- Match the style of your resume (fonts, formatting)
- 3-5 references (more only if requested)
- Separate page from resume
- Header should match resume header
- Include "References" or "Professional References" as title
Reference Preparation
Step 1: Ask Permission
Before listing anyone:
- Call or email to ask permission
- Confirm their contact information
- Explain the role you're applying for
- Gauge their willingness and enthusiasm
Script:
"Hi [Name], I hope you're doing well! I'm applying for a [Role] position at [Company] and was wondering if you'd be comfortable serving as a reference for me. The role involves [brief description], and I think your perspective on [specific project/skill] would be particularly valuable. Would you be willing to speak with them if they reach out?"
Step 2: Brief Your References
Send them:
- Copy of your resume
- Job description
- Key points you want highlighted
- Specific projects to mention
- Timeline for when they might be contacted
Briefing Email Template:
Subject: Reference Preparation - [Role] at [Company]
Hi [Name],
Thank you so much for agreeing to be a reference! Here's some context to help:
**The Role:** [Job title] at [Company]
**What they're looking for:** [Key requirements]
**Points I'm emphasizing:**
- [Achievement 1]
- [Achievement 2]
- [Skill they should mention]
**Our work together they might ask about:**
- [Project 1]
- [Project 2]
I've attached my resume and the job description for reference. They may reach out in the next [timeframe].
Please let me know if you have any questions, and thank you again!
Best,
[Your name]
Step 3: Follow Up
After references are checked:
- Thank your references regardless of outcome
- Let them know the result
- Offer to reciprocate
Handling Special Situations
Current Employer Doesn't Know
Options:
- Ask if reference check can wait until later stage
- Use colleagues who've left the company
- Be upfront: "My current employer doesn't know I'm looking"
- Use other professional references
Manager Left the Company
Options:
- Track them down on LinkedIn
- Use their personal email/phone
- Include their new company in reference list
- Explain "Former manager, now at [New Company]"
Bad Relationship with Past Manager
Options:
- Use another supervisor from that role
- Use senior colleagues instead
- Choose references from different roles
- Be prepared to explain if asked
Limited Professional Experience
Options:
- Professors or academic advisors
- Internship supervisors
- Volunteer organization leaders
- Coaches or mentors
- Client contacts
Reference Won't Give Positive Review
Don't use them. It's better to have fewer references than a lukewarm or negative one.
What Reference Checkers Ask
Common Questions
Performance:
- "How would you describe [name]'s work?"
- "What were their primary responsibilities?"
- "How did they perform against expectations?"
Skills:
- "What are their greatest strengths?"
- "What areas could they improve?"
- "How would you rate their [specific skill]?"
Work Style:
- "How did they handle pressure/deadlines?"
- "How did they work with the team?"
- "How did they handle conflict?"
Character:
- "Would you rehire them?"
- "Is there anything else I should know?"
- "How do they compare to peers?"
The "Would You Rehire?" Question
Most important question. Brief your references that this may be asked and ensure they can answer enthusiastically.
Reference List Template
[YOUR NAME]
[Your Email] | [Your Phone]
PROFESSIONAL REFERENCES
[REFERENCE 1 - MOST SENIOR/RELEVANT]
[Name]
[Title]
[Company]
Phone: [Number]
Email: [Email]
Relationship: [How you worked together, dates]
[REFERENCE 2]
[Name]
[Title]
[Company]
Phone: [Number]
Email: [Email]
Relationship: [How you worked together, dates]
[REFERENCE 3]
[Name]
[Title]
[Company]
Phone: [Number]
Email: [Email]
Relationship: [How you worked together, dates]
---
References available upon request for additional contacts.
Reference Timing
When to Provide References
- Don't include with initial application (unless requested)
- Bring to interview (have them ready)
- Provide when asked (usually after final interview)
- Always ask before sharing (confirm permission each time)
Common Timeline
- Application: "References available upon request" (optional on resume)
- First Interview: Have list ready but don't offer
- Final Rounds: "Can you provide references?" → Share list
- Reference Check: Company contacts your references
- Offer: Follow up with references, thank them
Output Format
When building a reference list:
# REFERENCE LIST
## Reference Strategy
**Target Role:** [Position]
**Company:** [Company]
## Recommended References
### Primary References (Use These)
**Reference 1: [Name]**
- Current Title: [Title]
- Company: [Company]
- Contact: [Phone/Email]
- Relationship: [Description]
- Why: [What they can speak to]
- Key points to highlight: [Specific projects/skills]
**Reference 2: [Name]**
[Same format]
**Reference 3: [Name]**
[Same format]
### Backup References (If Needed)
**Reference 4: [Name]**
[Same format]
## Briefing Notes
### For Each Reference, Send:
- [ ] Resume
- [ ] Job description
- [ ] Key talking points
- [ ] Timeline
### Key Points to Emphasize
- [Point 1 - who should mention]
- [Point 2 - who should mention]
## Reference Outreach
### Permission Request Script
[Customized script]
### Briefing Email
[Draft briefing email]
### Thank You Template
[Post-check thank you message]
Reference Checklist
- ✅ Have 3-5 references ready
- ✅ All references have given permission
- ✅ Contact information is current and accurate
- ✅ References know about the specific role
- ✅ Each reference has your resume and talking points
- ✅ At least one direct supervisor included
- ✅ References span different aspects of your work
- ✅ References are enthusiastic (not just willing)
- ✅ Backup references identified
- ✅ Thank you notes planned
How to use reference-list-builder 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 development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add reference-list-builder
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches reference-list-builder from GitHub repository paramchoudhary/resumeskills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate reference-list-builder. Access the skill through slash commands (e.g., /reference-list-builder) or your agent's skill management interface.
Security & Verification 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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ 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.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★58 reviews- ★★★★★Ishan White· Dec 28, 2024
reference-list-builder reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Shikha Mishra· Dec 24, 2024
reference-list-builder fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Noor Robinson· Dec 24, 2024
reference-list-builder is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ganesh Mohane· Dec 16, 2024
Keeps context tight: reference-list-builder is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Isabella Kapoor· Dec 16, 2024
reference-list-builder has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Aanya Gonzalez· Dec 16, 2024
Registry listing for reference-list-builder matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ama Harris· Nov 19, 2024
I recommend reference-list-builder for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Daniel Dixit· Nov 15, 2024
Solid pick for teams standardizing on skills: reference-list-builder is focused, and the summary matches what you get after install.
- ★★★★★Sakshi Patil· Nov 7, 2024
reference-list-builder has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Olivia Kim· Nov 7, 2024
Keeps context tight: reference-list-builder is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 58