Install
$ agentstack add skill-abullaisi-upwork-skills-upwork-profile-optimizer ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Upwork Profile Optimizer
The proposal's only job is to earn a profile visit. The profile does the actual closing, and it also decides search visibility before any proposal is sent: Upwork's AI search ranks freelancers on profile relevance, buyer intent, the client's history, and price fit, and clients can preview the whole profile from search results without clicking through. A half-filled profile loses twice: weaker preview, weaker ranking. Method from Upwork's published guidance plus a Top Rated Plus profile as the worked example.
Inputs
- Title, exact text.
- Overview, full text.
- Portfolio list: titles and niche of each piece, in their current order.
- Skills tags, as listed.
- Stats and badges: JSS if visible, badge tier, total earnings bracket, response stats.
- The user's niche and the kind of client they want next. The audit is against that target, not against a generic ideal.
Profile shortcut: if a stored profile file exists (upwork-profile.md in the working directory or ~/.claude/), read it first and audit against it; ask only for sections the file lacks or states vaguely (a rate line that says "ask me" means ask). If a stored profile file and a fresh paste both exist, the paste is ground truth for scoring and the file is background context. Flag any mismatch between the two as a finding.
When tags or stats are missing from both sources, audit what's present now and end by requesting exactly those two. Don't block the audit waiting for them.
Audit, in funnel order
1. Title (the search surface, 70-character cap)
The proven formula: role + specialty + result or credential ("UI/UX Designer | SaaS Dashboards | Top Rated Plus"). An outcome-led variant works when it's specific (the method author runs "Making Complex Things Simple and Easier to Use"), but it's the advanced move: it trades searchability for memorability, so pair it with skills tags that carry the search load. Instant fails: "Jack of all trades," "Hire me," anything that names no specialty.
2. Overview (the pitch, not the resume)
Proof first: open with the strongest credential or outcome in one line ("Top 3% on Upwork, 5+ years in SaaS design"), then two or three concrete outcomes, then tools. Clients scan; the first two lines do the work. A chronology of past jobs is a resume, and nobody hires a resume. Every profile section filled, because search previews expose the gaps.
3. Portfolio (the close)
- Lead with the 4 best pieces matched to the target client, order is part of the argument.
- Three pieces minimum before expecting invitations at all.
- Niche the portfolio harder than feels comfortable: a logos-only portfolio wins logo work faster than a we-do-everything portfolio wins anything.
- Photo: in focus, high resolution, plain background, an actual photograph (illustrated avatars violate policy).
4. The specialist question (be honest with the user here)
Three independent sources in Upwork's own guidance converge on the same claim: clients trust specialists over generalists, in both hiring and search ranking. If the user's profile lists four unrelated service lines, say so plainly and recommend either narrowing or splitting via specialized profiles (separate profile per category, built for exactly this). The one legitimate exception: operators deliberately running an agency-style breadth, who accept weaker search fit as the cost of range. Name the tradeoff, let the user choose it consciously.
5. Mechanics (the score behind the score)
- JSS recalculates every two weeks. The private "would you recommend, 1-10" question feeds it alongside the public stars, which is why a politely unhappy client can dent a score without a bad public review.
- The badge ladder (Rising Talent → Top Rated → Top Rated Plus → Expert-Vetted) shows next to every proposal. Protecting it beats decorating it: declining bad-fit work protects the score better than any overview edit, which is the job of the upwork-job-qualifier skill.
- Rate is a signal, not just a price. A rate far below the niche's range reads as a quality warning to exactly the clients worth having.
- Activity feeds visibility: regular logins, proposals, and fast invitation responses (see upwork-invitation-responder; unanswered invites are a visible stat).
6. The machine readers (AEO, the layer nobody else audits)
A profile now has three readers, not one: the classic keyword search, Upwork's AI ranking (Uma: relevance, buyer intent, client history, price fit), and, since Upwork's official ChatGPT app, an LLM synthesizing talent recommendations inside a chat window where the client never sees the search results page at all. The exact retrieval mechanics are not public; the writing principles that win LLM retrieval are stable anyway:
- Entity density beats vibes. Named tools, industries, deliverables, and credentials in natural sentences ("SaaS dashboard design in Figma for fintech clients") are what a model extracts and quotes. Clever positioning language extracts as nothing.
- This demotes the outcome-led title. A poetic title works on a human scanning a page; it is nearly invisible to a model matching "find me a [niche] designer." In the AI-search era, the role + specialty + credential formula is no longer just the default, it is the machine-legible option.
- Answer-shaped first lines. The overview's opening should literally answer "who is this and what are they best at" in extractable form, which is the proof-first structure already required above; the machine reader just raises the price of getting it wrong.
- Consistency across surfaces. Models cross-reference: the title, overview, skills tags, and portfolio piece names should tell one story in the same vocabulary. Contradictions that a human skims past read as noise to a retriever.
Audit note: label this layer honestly when reporting. The principles are sound inference from how LLM retrieval works; nobody outside Upwork has verified the connector's internals, so present it as "the direction the platform is moving," not as measured ranking factors.
Output format
Score each section strong / weak / missing, then a prioritized fix list, biggest lever first, maximum five items, each with the reason in one sentence. Rewrite the title and the overview's first two lines yourself as part of the audit; those two edits move more than everything else combined for most profiles.
Voice rules (hard)
- Specific rewrites, not adjectives. "Change X to Y because Z," never "make it more compelling."
- No em dashes. Plain words.
- If the profile is already strong, say so and stop. Manufactured critique erodes trust in the real critique.
Sources and provenance
Worked example: a Top Rated Plus (top 3%) profile. Official guidance, recommended reading:
- 15 Tips To Make Your Freelancer Profile Stand Out: https://www.upwork.com/resources/freelancer-profile-tips
- Freelancer Headlines: https://www.upwork.com/resources/freelancer-headlines
- Designer Profile Tips: https://www.upwork.com/resources/designer-profile-tips
- How To Differentiate Yourself as a Freelancer: https://www.upwork.com/resources/how-to-differentiate-yourself-as-a-freelancer
- Top Rated Freelancer Tips: https://www.upwork.com/resources/top-rated-freelancer-tips
- Upwork's algorithm explainer video (2026), on Upwork's official channel.
This skill is not affiliated with or endorsed by Upwork.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: abullaisi
- Source: abullaisi/upwork-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.