AGENT SKILL

reference-list-builder

Format professional references properly and prepare reference materials. Use when the user mentions references, reference list, references page, or preparing referees for a job application.

License 许可
MIT
最近更新
2026-07-29
Stars
★ 0
Forks
0

01 前言 Front Matter

name
reference-list-builder
description
Format professional references properly and prepare reference materials. Use when the user mentions references, reference list, references page, or preparing referees for a job application.

03 SKILL.md 正文

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:

  1. Most Valuable: Recent direct supervisor
  2. Very Valuable: Senior leaders who know your work
  3. Valuable: Peers and cross-functional partners
  4. Acceptable: Clients, vendors, professors
  5. 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: jane.smith@techcorp.com
Relationship: Direct supervisor for 3 years (2020-2023)

John Doe
VP of Engineering
Previous Company
Phone: (555) 234-5678
Email: john.doe@previous.com
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

  1. Application: "References available upon request" (optional on resume)
  2. First Interview: Have list ready but don't offer
  3. Final Rounds: "Can you provide references?" → Share list
  4. Reference Check: Company contacts your references
  5. 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

04 同仓库更多 Skills

KrismithReddy12
KrismithReddy12/claude-code-templates

zapier-make-patterns

No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power

★ 0
KrismithReddy12
KrismithReddy12/claude-code-templates

yeet

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

★ 0
KrismithReddy12
KrismithReddy12/claude-code-templates

workflow-automation

Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off. This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation. Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility

★ 0
KrismithReddy12
KrismithReddy12/claude-code-templates

trigger-dev

Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.

★ 0
KrismithReddy12
KrismithReddy12/claude-code-templates

slack-automation

Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.

★ 0
KrismithReddy12
KrismithReddy12/claude-code-templates

planning-with-files

Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.

★ 0