Interview
alirezarezvani/claude-skills
Phase 1 of building a Claude Managed Agent — interview the founder about the one job the agent should do, then produce a build sheet (CMA primitives table + v1/v2 deferrals + eval plan) WITHOUT…
Respond to an Upwork "Invitation to Interview" fast and well.
MITAuto-check passed
Install Upwork Invitation Responder
$ npx skills add abullaisi/upwork-skills --skill upwork-invitation-responder -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install abullaisi/upwork-skills upwork-invitation-responder --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/abullaisi/upwork-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/upwork-invitation-responder .claude/skills/upwork-invitation-responder && 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 "upwork-invitation-responder" agent skill from https://github.com/abullaisi/upwork-skills/tree/main/upwork-invitation-responder into .claude/skills/upwork-invitation-responder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upwork-invitation-responder", 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/abullaisi/upwork-skills/tree/main/upwork-invitation-responderType 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 abullaisi/upwork-skills --skill upwork-invitation-responder -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install abullaisi/upwork-skills upwork-invitation-responder --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/abullaisi/upwork-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/upwork-invitation-responder .agents/skills/upwork-invitation-responder && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "upwork-invitation-responder" agent skill from https://github.com/abullaisi/upwork-skills/tree/main/upwork-invitation-responder into .agents/skills/upwork-invitation-responder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upwork-invitation-responder", 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 abullaisi/upwork-skills --skill upwork-invitation-responder -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install abullaisi/upwork-skills upwork-invitation-responder --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/abullaisi/upwork-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/upwork-invitation-responder .cursor/skills/upwork-invitation-responder && 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 "upwork-invitation-responder" agent skill from https://github.com/abullaisi/upwork-skills/tree/main/upwork-invitation-responder into .cursor/skills/upwork-invitation-responder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upwork-invitation-responder", 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/abullaisi/upwork-skills.git --path upwork-invitation-responder--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 abullaisi/upwork-skills --skill upwork-invitation-responder -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install abullaisi/upwork-skills upwork-invitation-responder --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/abullaisi/upwork-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/upwork-invitation-responder .gemini/skills/upwork-invitation-responder && 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 "upwork-invitation-responder" agent skill from https://github.com/abullaisi/upwork-skills/tree/main/upwork-invitation-responder into .gemini/skills/upwork-invitation-responder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upwork-invitation-responder", 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 abullaisi/upwork-skills upwork-invitation-responderInstalls 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 abullaisi/upwork-skills --skill upwork-invitation-responder -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/abullaisi/upwork-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/upwork-invitation-responder .github/skills/upwork-invitation-responder && 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 "upwork-invitation-responder" agent skill from https://github.com/abullaisi/upwork-skills/tree/main/upwork-invitation-responder into .github/skills/upwork-invitation-responder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upwork-invitation-responder", 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 abullaisi/upwork-skills --skill upwork-invitation-responder -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install abullaisi/upwork-skills upwork-invitation-responder --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/abullaisi/upwork-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/upwork-invitation-responder .opencode/skills/upwork-invitation-responder && 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 "upwork-invitation-responder" agent skill from https://github.com/abullaisi/upwork-skills/tree/main/upwork-invitation-responder into .opencode/skills/upwork-invitation-responder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "upwork-invitation-responder", 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
upwork-invitation-responder- GitHub stars
- 114
- Used in
- 1 other repo
- Token cost
- ~1.4k tokens
- SKILL.md length
- 843 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Respond to an Upwork "Invitation to Interview" fast and well.
- Works in 3 steps: The invitation (job post or invite… → The user's decision: accept, decline, or… → For accepts: one portfolio link matched…
- The user pastes a job invitation they received on Upwork and wants to accept it
- SKILL.md covers Inputs, Rule zero: always respond,…, Triage (when the user is unsure) and Accept, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Upwork Invitation Responder is an agent skill from abullaisi/upwork-skills. Respond to an Upwork "Invitation to Interview" fast and well. Use when the user pastes a job invitation they received on Upwork and wants to accept it, decline it, or decline it while referring another freelancer. Triggers include "got an Upwork invite", "decline this invitation", "reply to this invite", "client invited me", "should I take this invitation". Drafts the reply; helps triage borderline invitations first. Companion to upwork-proposal-writer (which handles the full proposal after an accept).
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: AI agent skills for Upwork freelancers, from a real Top Rated Plus playbook. Free, open, community-written. Not affiliated with Upwork. The licence is MIT.
When your agent uses it
- The user pastes a job invitation they received on Upwork and wants to accept it
- Decline it while referring another freelancer
- Include got an Upwork invite
- Decline this invitation
Example prompts
- “Invitation to Interview”
- “got an Upwork invite”
- “decline this invitation”
- “/upwork-invitation-responder”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- The invitation (job post or invite message), pasted.
- The user's decision: accept, decline, or unsure. If unsure, run the triage below first.
- For accepts: one portfolio link matched to the job. For decline-with-referral: the referral's name and whether the user has already told…
What it can do on your machine
Read from SKILL.md and the folder at commit dd06254. 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
Links to these hosts (documentation or services it may open):
upwork.com
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
Upwork Invitation Responder loads about 1.4k tokens when it runs. Until then it costs about 134 tokens; SKILL.md has 843 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 abullaisi/upwork-skills at commit dd06254, republished under its MIT licence (© abullaisi). 843 words, ~1,448 tokens.
Download SKILL.mdSave it as
.claude/skills/upwork-invitation-responder/SKILL.md (or your agent's skills folder).- name
- upwork-invitation-responder
- description
- Respond to an Upwork "Invitation to Interview" fast and well. Use when the user pastes a job invitation they received on Upwork and wants to accept it, decline it, or decline it while referring another freelancer. Triggers include "got an Upwork invite", "decline this invitation", "reply to this invite", "client invited me", "should I take this invitation". Drafts the reply; helps triage borderline invitations first. Companion to upwork-proposal-writer (which handles the full proposal after an accept).
Upwork Invitation Responder
Invitations are not job applications. The client already handpicked this freelancer's profile and is asking for a proposal. That changes the reply's job: the credibility argument is half-won, speed and clarity do the rest. Method extracted from a Top Rated Plus freelancer's real invitation threads plus Upwork's published guidance.
Inputs
- The invitation (job post or invite message), pasted.
- The user's decision: accept, decline, or unsure. If unsure, run the triage below first.
- For accepts: one portfolio link matched to the job. For decline-with-referral: the referral's name and whether the user has already told them.
Profile shortcut: if a stored profile file exists (upwork-profile.md in the working directory or ~/.claude/), read identity, niche, and links from it and ask only for what's missing or not stated concretely (a rate line that says "ask me" means ask).
Rule zero: always respond, same day
Silence is the worst possible reply, and it is not private: the job's activity panel shows clients a counted "Unanswered invites" stat next to "Invites sent." An ignored invitation is a visible number on the client's screen. Every invitation gets an answer, even a two-line decline. If invitations arrive faster than the freelancer can handle, the fix is the profile availability setting ("Not Available"), never silence.
Triage (when the user is unsure)
Three questions, thirty seconds:
- Would you do this work at your current rate? If the answer needs a rate raise to become yes, it's a decline.
- Does your portfolio already prove this niche? If proving fit requires explaining, the client picked the wrong person; decline or refer.
- Do you have capacity inside their timeline? Busy-but-interested is still a decline (or a referral), never a slow maybe.
Two or three yeses: accept. Otherwise pick the decline move that fits.
Question 1 is a hard gate. If getting to yes needs a rate raise, it's a decline no matter how the other two land.
Accept
Three or four sentences maximum. No sales copy: the client already chose this profile.
Shape: thank them for the invite, name the specific thing in their brief you'd start with (proves you read it), attach one matched portfolio link, close with one clarifying question or availability for a quick chat. If the client proposed a call, agree immediately and offer two time slots. The full proposal, when required, hands off to the upwork-proposal-writer skill.
Two mechanics worth knowing on accepts: Upwork's own UI states a video reply gets proposals noticed up to 31% more often (it costs extra Connects, so reserve it for invitations worth winning), and Uma now drafts invitation replies for everyone, which means a generic grateful reply is the baseline. Specificity about THEIR brief is what a handpicked freelancer's reply must add.
Show full SKILL.md (383 more words)Show less
Decline: three moves
All three share the same skeleton: thank first, decline in the first sentence, give the real reason plainly, never apologize twice, never invent an excuse. One or two sentences plus the closer.
Move 1: decline and refer (the goodwill machine). For good jobs you can't take. Thank them, say you're committed to other projects, refer a specific freelancer you can vouch for, and vouch in one line ("we've worked together; they have my full backing"). This converts a lost job into goodwill with the client AND a favor to a peer. Two rules: only refer someone whose work you'd stake your name on, and message the referred freelancer first so the handoff lands warm, not cold.
Move 2: decline, not a fit. For mismatched jobs. Thank them, say plainly the job isn't a fit for your skills, and leave the door open: "I hope we can work together on something closer to my lane." No fake busyness; clients respect an honest not-my-thing and remember it when the right job comes. Not a fit covers budget as well as skills. When the skills match but the budget can't reach your rate, say the job isn't a fit at this budget; never claim a skills mismatch that isn't true.
Move 3: decline, at capacity. For fine jobs at the wrong time. Thank them, say you're fully booked, keep the door open for future work. If they're worth staying visible to, invite them to reach out for the next project.
Upwork's decline flow also asks for a dropdown reason; tell the user which one matches the move (for example "Budget too low" or "Not a good fit").
Voice rules (hard)
- One to two sentences per move plus the closer. An invitation decline is not an essay.
- Write like a person: contractions, plain words, warm but unapologetic.
- No em dashes. No "unfortunately" more than once. No "I'm honored."
- Never include contact information in the reply (platform policy).
- Never name-drop other clients or their projects in a decline.
Sources and provenance
Method extracted from a Top Rated Plus freelancer's real invitation threads (design/dev niche); decline moves generalized from templates used across dozens of invitations. Official guidance:
- How To Reply to an Upwork Job Invitation: https://www.upwork.com/resources/job-invitation-reply
This skill is not affiliated with or endorsed by Upwork.
© abullaisi, 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 upwork-invitation-responder of abullaisi/upwork-skills.
Open the folder on GitHubat commit dd06254
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in abullaisi/upwork-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Upwork Invitation Responder 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 |
|---|---|---|---|---|---|---|
| Upwork Invitation Responder this skillabullaisi/upwork-skills | 114 | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Interviewalirezarezvani/claude-skills | 28k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Interviewcodewhale-hq/Codewhale | 41k | — | ~232 | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 104k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Interview Prepreactive-resume/reactive-resume | 44k | — | ~10k | Automated safety check: Pass | MIT | |
| Interview Coachsickn33/agentic-awesome-skills | 47k | 2 repos | ~751 | Automated safety check: Pass | MIT |
Similar skills
Interview
codewhale-hq/Codewhale
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec.
Interview Me
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
Interview Prep
reactive-resume/reactive-resume
Prepares the user for a specific interview from their real experience.
Interview Coach
sickn33/agentic-awesome-skills
Full job search coaching system — JD decoding, resume, storybank, mock interviews, transcript analysis, comp negotiation.
Mock Interview
reactive-resume/reactive-resume
Runs a mock interview for a specific job description. An agent skill from reactive-resume/reactive-resume.
More from abullaisi/upwork-skills
Upwork Client Messenger
abullaisi/upwork-skills
Draft mid-contract messages to a freelance client on Upwork or similar platforms.
Upwork Job Qualifier
abullaisi/upwork-skills
Decide whether an Upwork job post is worth applying to before spending Connects.
Upwork Profile Optimizer
abullaisi/upwork-skills
Audit and improve an Upwork freelancer profile. An agent skill from abullaisi/upwork-skills.
Upwork Proposal Writer
abullaisi/upwork-skills
Draft or review an Upwork proposal (cover letter) using the five-move method extracted from a Top Rated Plus freelancer's winning proposals, corrected for the AI era.
Questions about Upwork Invitation Responder
What does Upwork Invitation Responder do?
Respond to an Upwork "Invitation to Interview" fast and well. Upwork Invitation Responder is an agent skill from abullaisi/upwork-skills. Respond to an Upwork "Invitation to Interview" fast and well.
When should I use Upwork Invitation Responder?
Upwork Invitation Responder fits situations like: the user pastes a job invitation they received on Upwork and wants to accept it; decline it while referring another freelancer; include got an Upwork invite; decline this invitation.
How do I install Upwork Invitation Responder in Claude Code?
Run `npx skills add abullaisi/upwork-skills --skill upwork-invitation-responder -a claude-code`. Or copy the skill folder (upwork-invitation-responder in abullaisi/upwork-skills) into .claude/skills/upwork-invitation-responder in your project. Claude Code loads it when a task matches its description.
How do I install Upwork Invitation Responder in Codex?
Run `npx skills add abullaisi/upwork-skills --skill upwork-invitation-responder -a codex`. Or copy the skill folder (upwork-invitation-responder in abullaisi/upwork-skills) into .agents/skills/upwork-invitation-responder in your project. Codex loads it when a task matches its description.
Can I use Upwork Invitation Responder 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 abullaisi/upwork-skills --skill upwork-invitation-responder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/upwork-invitation-responder, .gemini/skills/upwork-invitation-responder, .github/skills/upwork-invitation-responder and .opencode/skills/upwork-invitation-responder in your project.
What does Upwork Invitation Responder need to run?
SKILL.md names no scripts, command-line tools or credentials: Upwork Invitation Responder is instructions for the agent only.
Does Upwork Invitation Responder access the network?
SKILL.md names 1 domain. As links in the text: upwork.com. This is read from the text; nothing was executed.
Is Upwork Invitation Responder 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 Upwork Invitation Responder use?
Upwork Invitation Responder 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 Upwork Invitation Responder use?
About 1.4k tokens (SKILL.md is roughly 5.8k 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 Upwork Invitation Responder?
Skills that share tags, products or a category with Upwork Invitation Responder: Interview (alirezarezvani/claude-skills, 28k stars), Interview (codewhale-hq/Codewhale, 41k stars), Interview Me (addyosmani/agent-skills, 104k stars) and Interview Prep (reactive-resume/reactive-resume, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Upwork Invitation Responder?
abullaisi (a GitHub user) maintains it in abullaisi/upwork-skills, which has 114 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 5, 2026.
Source: abullaisi/upwork-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.