Geo Fundamentals
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
Sets up PawBytes Upwork Suite module in a project. An agent skill from pawbytes/skill-suites.
$ npx skills add pawbytes/skill-suites --skill paw-upwork-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pawbytes/skill-suites paw-upwork-setup --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/pawbytes/skill-suites.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/upwork/paw-upwork-setup .claude/skills/paw-upwork-setup && 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 "paw-upwork-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/upwork/paw-upwork-setup into .claude/skills/paw-upwork-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-upwork-setup", 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/pawbytes/skill-suites/tree/main/src/upwork/paw-upwork-setupType 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 pawbytes/skill-suites --skill paw-upwork-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pawbytes/skill-suites paw-upwork-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/upwork/paw-upwork-setup .agents/skills/paw-upwork-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "paw-upwork-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/upwork/paw-upwork-setup into .agents/skills/paw-upwork-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-upwork-setup", 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 pawbytes/skill-suites --skill paw-upwork-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pawbytes/skill-suites paw-upwork-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/upwork/paw-upwork-setup .cursor/skills/paw-upwork-setup && 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 "paw-upwork-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/upwork/paw-upwork-setup into .cursor/skills/paw-upwork-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-upwork-setup", 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/pawbytes/skill-suites.git --path src/upwork/paw-upwork-setup--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 pawbytes/skill-suites --skill paw-upwork-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pawbytes/skill-suites paw-upwork-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/upwork/paw-upwork-setup .gemini/skills/paw-upwork-setup && 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 "paw-upwork-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/upwork/paw-upwork-setup into .gemini/skills/paw-upwork-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-upwork-setup", 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 pawbytes/skill-suites paw-upwork-setupInstalls 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 pawbytes/skill-suites --skill paw-upwork-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/upwork/paw-upwork-setup .github/skills/paw-upwork-setup && 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 "paw-upwork-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/upwork/paw-upwork-setup into .github/skills/paw-upwork-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-upwork-setup", 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 pawbytes/skill-suites --skill paw-upwork-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pawbytes/skill-suites paw-upwork-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pawbytes/skill-suites.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/upwork/paw-upwork-setup .opencode/skills/paw-upwork-setup && 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 "paw-upwork-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/upwork/paw-upwork-setup into .opencode/skills/paw-upwork-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-upwork-setup", 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.
paw-upwork-setupSets up PawBytes Upwork Suite module in a project. An agent skill from pawbytes/skill-suites.
Paw Upwork Setup is an agent skill from pawbytes/skill-suites. Sets up PawBytes Upwork Suite module in a project. Use when the user requests to 'install upwork module', 'configure PawBytes Upwork Suite', or 'setup paw-upwork'.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files, including scripts and assets (for example `assets/module.yaml`, `scripts/merge-config.py` and `scripts/merge-help-csv.py`).
It sits in Marketing & SEO. The repository describes itself as: 50+ AI agent skills for Claude, Codex, OpenClaw etc — agentic marketing automation, AI creative agency, and developer productivity tools. The licence is MIT.
2 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 547a6df. It shows what the files ask for, not the result of running them.
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.
Ships 8 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3gituvFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comAlso links to:
pawbytes.ioFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Paw Upwork Setup loads about 2.4k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 986 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.
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); the scripts in this folder are not scanned.
The full file from pawbytes/skill-suites at commit 547a6df, republished under its MIT licence (© pawbytes). 986 words, ~2,402 tokens.
.claude/skills/paw-upwork-setup/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.Installs and configures the PawBytes Upwork Suite into a project in a single guided pass: writes config, checks for (and offers to install) the browser-harness dependency that powers live market research, and scaffolds the per-freelancer workspace. Module identity (name, code, version) comes from assets/module.yaml.
Writes to:
{project-root}/.pawbytes/config/config.yaml — shared ecosystem config: core settings at root plus an upwork section. User-only keys (user_name, communication_language) are never written here.{project-root}/.pawbytes/config/config.user.yaml — gitignore-intended personal settings: user_name, communication_language, and any module variable marked user_setting: true (default_freelancer, research_mode).{project-root}/.pawbytes/config/module-help.csv — registers module capabilities for the help system.Both config scripts use an anti-zombie pattern — existing entries for this module are removed before writing fresh ones, so stale values never persist.
{project-root} is a literal token in config values — never substitute it with an actual path. It signals to the consuming LLM that the value is relative to the project root, not the skill root.
A setup specialist for the PawBytes Upwork Suite. Efficient and user-friendly during first-time installation and updates, and honest about the one real dependency (browser-harness) — installing it when wanted, falling back gracefully when not.
research_mode: manual and continue. The suite always works.assets/module.yaml for module metadata and variable definitions (the code field, upwork, is the module identifier).{project-root}/.pawbytes/config/config.yaml has an upwork section — if present, inform the user this is an update.If the user provides arguments (e.g. accept all defaults, --headless/-H, or inline values like my name is Alex, language is Spanish, research mode manual), map provided values to config keys, use defaults for the rest, and skip interactive prompting. Still display the full confirmation summary at the end.
Ask the user for values. Show defaults in brackets. Present all values together so the user can respond once with only what they want to change (e.g. "research mode manual, rest are fine"). Never tell the user to "press enter" or "leave blank" — in a chat interface they must type something to respond.
Default priority (highest wins): existing config values > assets/module.yaml defaults.
Core config (only if no core keys exist yet): user_name (default: Pawbytes), communication_language and document_output_language (default: English — ask as a single language question, both keys get the same answer). Of these, user_name and communication_language are written exclusively to config.user.yaml.
Module config: Read each variable in assets/module.yaml that has a prompt field and ask using that prompt with its default. Note that research_mode may be overridden to manual by the dependency check below, regardless of the user's stated preference.
The paw-upwork-research skill drives the freelancer's own logged-in Chrome via browser-harness (CDP) for live Upwork market research. This is the suite's only external dependency, and it is optional — research falls back to pasted listings without it.
Check for the command and act on the result:
command -v browser-harnessresearch_mode as the user chose (default local-browser).uv and git; verify both first (command -v uv, command -v git) and instruct the user to install whichever is missing before proceeding. With both present, install into a durable path (not a temp dir):git clone https://github.com/browser-use/browser-harness ~/Developer/browser-harness
cd ~/Developer/browser-harness && uv tool install -e .
command -v browser-harness After install, mention the one-time Chrome step: the first live-research run will guide the remote-debugging toggle (chrome://inspect/#remote-debugging) — it does not need doing now. The browser skill's install.md carries the full attach/escalate flow if a deeper problem surfaces.
uv/git, no network, user says no) → set research_mode: manual and tell the user research will run from job listings they paste. Do not stop setup.Record the resolved research_mode and carry it into the written config.
Write a temp JSON file with the collected answers structured as {"core": {...}, "module": {...}} (omit core if it already exists). Then run both scripts:
python3 scripts/merge-config.py \
--config-path "{project-root}/.pawbytes/config/config.yaml" \
--user-config-path "{project-root}/.pawbytes/config/config.user.yaml" \
--module-yaml assets/module.yaml \
--answers {temp-file}
python3 scripts/merge-help-csv.py \
--target "{project-root}/.pawbytes/config/module-help.csv" \
--source assets/module-help.csv \
--module-code upworkBoth scripts output JSON to stdout. If either exits non-zero, surface the error and stop. Run either script with --help for full usage.
Resolve the {project-root} token to the actual project root for directories on disk; the config files keep the literal token. Create the suite root and reports folder, then scaffold the per-freelancer workspace.
mkdir -p "{project-root}/.pawbytes/upwork-suites/reports"If the user named a freelancer (via default_freelancer or inline), scaffold their workspace skeleton; otherwise create just the freelancers/ parent and leave per-freelancer scaffolding to the coach on first onboarding. For a slug {slug}:
mkdir -p "{project-root}/.pawbytes/upwork-suites/freelancers/{slug}/research"
mkdir -p "{project-root}/.pawbytes/upwork-suites/freelancers/{slug}/profile"
mkdir -p "{project-root}/.pawbytes/upwork-suites/freelancers/{slug}/proposals"
mkdir -p "{project-root}/.pawbytes/upwork-suites/freelancers/{slug}/daily"Then write {project-root}/.pawbytes/upwork-suites/freelancers/{slug}/index.md as the orientation doc every skill reads first:
# Upwork Workspace — {slug}
## Status
| Niche | Positioning brief | Profile | Proposals sent | Last updated |
|-------|-------------------|---------|----------------|--------------|
| (TBD) | (none) | (none) | 0 | |
## Files
- `freelancer-context.md` — identity, raw skills/history, voice/tone (coach)
- `positioning-brief.md` — canonical niche + angle + headline (coach, source of truth)
- `research/` — niche opportunity reports + rate observations
- `profile/` — profile drafts + variations, portfolio descriptions
- `proposals/` — per-job tailored proposals + scores
- `kit.md` — reusable intros, snippets, case-study blurbs
- `outcomes.md` — feedback loop: sent/replies/wins per proposal style
- `daily/YYYY-MM-DD.md` — append-only session log, tagged by skill
## Next step
Talk to `paw-upwork-agent-coach` to capture your context and discover your niche.Use the script JSON output to display what was written — config values set, user settings written to config.user.yaml (user_keys in result), help entries added, fresh install vs update, and the resolved research_mode (note if it fell back to manual and why). Report the workspace scaffolded. Then display the module_greeting from assets/module.yaml.
Once the user's user_name and communication_language are known (from collected input, arguments, or existing config), use them consistently for the rest of the session: address the user by their configured name and communicate in their configured language.
© pawbytes, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 10 other files (scripts, assets) in src/upwork/paw-upwork-setup of pawbytes/skill-suites.
Open the folder on GitHubat commit 547a6df
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 pawbytes/skill-suites, which our catalogue first saw on October 7, 2026.
Paw Upwork Setup 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 |
|---|---|---|---|---|---|---|
| Paw Upwork Setup this skillpawbytes/skill-suites | 110 | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Geo Fundamentalswasp-lang/wasp | 19k | 8 repos | ~861 | Automated safety check: Pass | MIT | |
| Hreflang and International SEOAgriciDaniel/claude-seo | 18k | 5 repos | ~3.4k | Automated safety check: Pass | MIT | |
| SEO GeoReScienceLab/opc-skills | 1.8k | 4 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Ad CreativeLeoYeAI/openclaw-marketing-skills | 1k | 8 repos | ~3.4k | Automated safety check: Pass | Custom licence | |
| Google SEO APIsAgriciDaniel/claude-seo | 18k | 1 repos | ~4.2k | Automated safety check: Pass | MIT |
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
AgriciDaniel/claude-seo
Audits, validates and generates hreflang tags for multi-language and multi-region sites in HTML, HTTP headers or XML sitemaps, flagging common code and return-tag mistakes.
ReScienceLab/opc-skills
SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.
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.
AgriciDaniel/claude-seo
Pulls real Google data for SEO work: Search Console, PageSpeed Insights, CrUX field data, the Indexing API and GA4 organic traffic, through /seo google commands.
Nexus-JPF/note-companion
When the user wants to set up, improve, or audit analytics tracking and measurement.
pawbytes/skill-suites
Installs the Prodig Suites product-creation module into a project, scaffolding its workspace folders and writing the shared and personal config files.
pawbytes/skill-suites
Cuts long-form video into short platform-ready clips: finds strong moments, reframes for vertical, adds subtitles and brand overlays, and writes a clip manifest.
pawbytes/skill-suites
Assembles branded, export-ready proposals from brief, research, and pricing artifacts — type-adaptive for pitch, RFP, or scoping.
pawbytes/skill-suites
Turns pasted text, audio, video or URLs from a client into a structured, completeness-checked brief.md for the first stage of a proposal pipeline.
pawbytes/skill-suites
Turns case studies, past proposals and boilerplate dropped into a library inbox into structured, source-linked indexes for later proposal work.
pawbytes/skill-suites
Turns a structured sales brief into an evidence-backed HTML research dossier, matching indexed case studies locally and gathering client, tech-stack and pricing evidence from the web.
Categories
Sets up PawBytes Upwork Suite module in a project. An agent skill from pawbytes/skill-suites. Paw Upwork Setup is an agent skill from pawbytes/skill-suites. Sets up PawBytes Upwork Suite module in a project.
Paw Upwork Setup fits situations like: the user requests to install upwork module; configure PawBytes Upwork Suite; setup paw-upwork.
Run `npx skills add pawbytes/skill-suites --skill paw-upwork-setup -a claude-code`. Or copy the skill folder (src/upwork/paw-upwork-setup in pawbytes/skill-suites) into .claude/skills/paw-upwork-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add pawbytes/skill-suites --skill paw-upwork-setup -a codex`. Or copy the skill folder (src/upwork/paw-upwork-setup in pawbytes/skill-suites) into .agents/skills/paw-upwork-setup in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pawbytes/skill-suites --skill paw-upwork-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/paw-upwork-setup, .gemini/skills/paw-upwork-setup, .github/skills/paw-upwork-setup and .opencode/skills/paw-upwork-setup in your project.
Going by SKILL.md and its folder, Paw Upwork Setup needs Python for the scripts in its folder and the command-line tools its instructions call (python3, git and uv). Our summary lists: Python 3.
SKILL.md names 2 domains. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. As links in the text: pawbytes.io. This is read from the text; nothing was executed.
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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Paw Upwork Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Paw Upwork Setup: Geo Fundamentals (wasp-lang/wasp, 19k stars), Hreflang and International SEO (AgriciDaniel/claude-seo, 18k stars), SEO Geo (ReScienceLab/opc-skills, 1.8k 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.
pawbytes (a GitHub organization) maintains it in pawbytes/skill-suites, which has 110 GitHub stars. The repository holds 71 skills in this directory. The repository was last updated on October 3, 2026.
Source: pawbytes/skill-suites on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.