Banner Design System
nextlevelbuilder/ui-ux-pro-max-skill
Walks through designing a banner for social media, ads, a website hero or print, from gathering requirements to building 2 or 3 art-direction options in HTML and CSS.
Secure strong references after a departure — who to ask, the ask messages, the briefing sheet that makes their reference specific, and the LinkedIn recommendation swap.
MITAuto-check passed
Install Reference Request Kit
$ npx skills add mohitagw15856/pm-claude-skills --skill reference-request-kit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills reference-request-kit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/reference-request-kit .claude/skills/reference-request-kit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "reference-request-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/reference-request-kit into .claude/skills/reference-request-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reference-request-kit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/reference-request-kitType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill reference-request-kit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills reference-request-kit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/reference-request-kit .agents/skills/reference-request-kit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "reference-request-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/reference-request-kit into .agents/skills/reference-request-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reference-request-kit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill reference-request-kit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills reference-request-kit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/reference-request-kit .cursor/skills/reference-request-kit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "reference-request-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/reference-request-kit into .cursor/skills/reference-request-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reference-request-kit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/reference-request-kit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill reference-request-kit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills reference-request-kit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/reference-request-kit .gemini/skills/reference-request-kit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "reference-request-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/reference-request-kit into .gemini/skills/reference-request-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reference-request-kit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills reference-request-kitInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill reference-request-kit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/reference-request-kit .github/skills/reference-request-kit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "reference-request-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/reference-request-kit into .github/skills/reference-request-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reference-request-kit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill reference-request-kit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills reference-request-kit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/reference-request-kit .opencode/skills/reference-request-kit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "reference-request-kit" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/reference-request-kit into .opencode/skills/reference-request-kit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reference-request-kit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
reference-request-kit- GitHub stars
- 1.4k
- Token cost
- ~1k tokens
- SKILL.md length
- 531 words
- Files
- 1
- Skills in repo
- 1,334
- Repo updated
- First seen
- Licence
- MIT
At a glance
Secure strong references after a departure — who to ask, the ask messages, the briefing sheet that makes their reference specific, and the LinkedIn recommendation swap.
- Works in 5 steps: Coverage, not seniority: pick referees… → The lukewarm test: if you're not certain… → The ask has an out: every request… → …
- Asked to help me get references
- SKILL.md covers What This Skill Produces, Required Inputs, Framework and Output Format, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Reference Request Kit is an agent skill from mohitagw15856/pm-claude-skills. Secure strong references after a departure — who to ask, the ask messages, the briefing sheet that makes their reference specific, and the LinkedIn recommendation swap. Use when asked to help me get references, write a reference request, prep my referee, or ask my old manager for a recommendation. Produces the referee shortlist with rationale, tailored ask messages, a one-page referee briefing sheet, and the follow-up etiquette.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with LinkedIn. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to help me get references
- Write a reference request
- Prep my referee
- Ask my old manager for a recommendation
Example prompts
- “/reference-request-kit”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Coverage, not seniority: pick referees per claim — one for craft, one for collaboration, one for outcomes. A direct manager who watched…
- The lukewarm test: if you're not certain the reference is enthusiastic, it isn't. Ask candidates first: "would you be comfortable giving a…
- The ask has an out: every request includes a graceful no ("totally understand if the timing's wrong"). Cornered referees give cornered…
- The briefing sheet is the skill: referees improvise badly. One page: the target role, the two witnessed stories with numbers, the claim…
- Per-use heads-up: referees get warned before each company calls — name, role, what to emphasize. A surprised referee sounds like an…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Reference Request Kit loads about 1k tokens when it runs. Until then it costs about 114 tokens; SKILL.md has 531 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 531 words, ~1,026 tokens.
Download SKILL.mdSave it as
.claude/skills/reference-request-kit/SKILL.md (or your agent's skills folder).- name
- reference-request-kit
- description
- Secure strong references after a departure — who to ask, the ask messages, the briefing sheet that makes their reference specific, and the LinkedIn recommendation swap. Use when asked to help me get references, write a reference request, prep my referee, or ask my old manager for a recommendation. Produces the referee shortlist with rationale, tailored ask messages, a one-page referee briefing sheet, and the follow-up etiquette.
Reference Request Kit Skill
A reference is a performance by someone else on your behalf — and performers do better with a script. This skill picks the right referees, makes the ask easy to say yes to, and (the step everyone skips) briefs them so the reference is specific instead of warmly vague.
What This Skill Produces
- The referee shortlist — who, for which claim, with the risk notes (the lukewarm reference is worse than none)
- Ask messages — tailored per relationship, each with an easy out
- The briefing sheet — one page per referee: the role, the two stories to tell, the numbers to cite
- Logistics — timing, the heads-up-per-use rule, and the LinkedIn swap
Required Inputs
Ask for these if not provided:
- The circumstances — layoff, resignation, complicated exit (this shapes who's safe to ask)
- Candidate referees — names, roles, relationship, and honestly: how warm is each?
- The target roles — references are chosen per claim the next job needs proven
- The stories — 2–3 achievements each referee actually witnessed (a referee can't cite what they never saw)
Framework
- Coverage, not seniority: pick referees per claim — one for craft, one for collaboration, one for outcomes. A direct manager who watched the work beats a VP who recognizes the name.
- The lukewarm test: if you're not certain the reference is enthusiastic, it isn't. Ask candidates first: "would you be comfortable giving a strong reference?" — the wording that lets tepid people decline.
- The ask has an out: every request includes a graceful no ("totally understand if the timing's wrong"). Cornered referees give cornered references.
- The briefing sheet is the skill: referees improvise badly. One page: the target role, the two witnessed stories with numbers, the claim this reference supports, and what the checker will likely ask.
- Per-use heads-up: referees get warned before each company calls — name, role, what to emphasize. A surprised referee sounds like an unprepared one.
Output Format
Show full SKILL.md (215 more words)Show less
Reference Kit: [name] → [target role type]
Shortlist
| Referee | Covers the claim | Warmth (honest) | Risk note |
|---|
The asks
[Per referee: the message, in their relationship's register, with the out built in]
Briefing sheet — [referee]
Role I'm pursuing: … The claim you can speak to: … Two stories you saw: [with numbers] They may ask: …
Logistics
[Timing, the per-use heads-up template, the thank-you regardless of outcome, the LinkedIn recommendation swap offer]
Quality Checks
- Every target-role claim has a referee who witnessed it
- Warmth is assessed honestly and lukewarm candidates are cut or comfort-tested
- Every ask contains a graceful out
- Each briefing sheet cites only what that referee actually saw
- The per-use heads-up template exists
Anti-Patterns
- Do not rank referees by title — checkers discount name-recognizers who can't give specifics
- Do not send one generic ask to everyone — the relationship register is the persuasion
- Do not skip the briefing sheet — unprepared enthusiasm comes out as "great person to work with," which checkers hear as nothing
- Do not put words in a referee's mouth they can't own — briefing is reminding, not scripting fiction
- Do not burn a complicated-exit bridge by asking the wrong person — the risk notes exist to be read
Example Trigger Phrases
- "Help me get references."
- "Write a reference request."
- "Prep my referee."
- "Ask my old manager for a recommendation."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/reference-request-kit of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Reference Request Kit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Reference Request Kit this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1k | Automated safety check: Pass | MIT | |
| Banner Design Systemnextlevelbuilder/ui-ux-pro-max-skill | 134k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Agent ReachPanniantong/Agent-Reach | 93k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Social Contentfreekmurze/dotfiles | 1k | 22 repos | ~2.1k | Automated safety check: Pass | None | |
| Ad CreativeLeoYeAI/openclaw-marketing-skills | 1k | 8 repos | ~3.4k | Automated safety check: Pass | Custom licence | |
| Linkedin Marketingsergebulaev/linkedin-skills | 4.3k | 1 repos | ~3.2k | Automated safety check: Notes | MIT |
Similar skills
Agent Reach
Panniantong/Agent-Reach
Routes web research and platform lookups across 16 sites, including Twitter, Reddit, YouTube, Bilibili, Xiaohongshu and GitHub, through one command-line tool.
Social Content
freekmurze/dotfiles
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms.
Ad Creative
LeoYeAI/openclaw-marketing-skills
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform.
Linkedin Marketing
sergebulaev/linkedin-skills
Plan, draft, audit, and publish LinkedIn posts and comments.
LinkedIn Job Search
MadsLorentzen/ai-job-search
Searches LinkedIn's public job listings for any location or remote work and fetches the full description of a posting, with no login or API key.
More from mohitagw15856/pm-claude-skills
All 1,334 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Offer Comparison
mohitagw15856/pm-claude-skills
Compare two or more job offers as total-comp curves over four years — vesting cliffs, bonuses, 401(k) match, and the crossover year computed, not vibed.
Related
Works with
Questions about Reference Request Kit
What does Reference Request Kit do?
Secure strong references after a departure — who to ask, the ask messages, the briefing sheet that makes their reference specific, and the LinkedIn recommendation swap. Reference Request Kit is an agent skill from mohitagw15856/pm-claude-skills. Secure strong references after a departure — who to ask, the ask messages, the briefing sheet that makes their reference specific, and the LinkedIn recommendation swap.
When should I use Reference Request Kit?
Reference Request Kit fits situations like: asked to help me get references; write a reference request; prep my referee; ask my old manager for a recommendation.
How do I install Reference Request Kit in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill reference-request-kit -a claude-code`. Or copy the skill folder (skills/reference-request-kit in mohitagw15856/pm-claude-skills) into .claude/skills/reference-request-kit in your project. Claude Code loads it when a task matches its description.
How do I install Reference Request Kit in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill reference-request-kit -a codex`. Or copy the skill folder (skills/reference-request-kit in mohitagw15856/pm-claude-skills) into .agents/skills/reference-request-kit in your project. Codex loads it when a task matches its description.
Can I use Reference Request Kit in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill reference-request-kit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reference-request-kit, .gemini/skills/reference-request-kit, .github/skills/reference-request-kit and .opencode/skills/reference-request-kit in your project.
What does Reference Request Kit need to run?
SKILL.md names no scripts, command-line tools or credentials: Reference Request Kit is instructions for the agent only.
Does Reference Request Kit access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Reference Request Kit safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Reference Request Kit use?
Reference Request Kit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Reference Request Kit use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Reference Request Kit?
Skills that share tags, products or a category with Reference Request Kit: Banner Design System (nextlevelbuilder/ui-ux-pro-max-skill, 134k stars), Agent Reach (Panniantong/Agent-Reach, 93k stars), Social Content (freekmurze/dotfiles, 1k stars) and Ad Creative (LeoYeAI/openclaw-marketing-skills, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Reference Request Kit?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,429 GitHub stars. The repository holds 1,334 skills in this directory. The repository was last updated on October 6, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.