Geo Fundamentals
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
Sets up Agentic Marketing Suite module in a project. An agent skill from pawbytes/skill-suites.
$ npx skills add pawbytes/skill-suites --skill paw-mkt-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pawbytes/skill-suites paw-mkt-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/marketing/paw-mkt-setup .claude/skills/paw-mkt-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-mkt-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/marketing/paw-mkt-setup into .claude/skills/paw-mkt-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-mkt-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/marketing/paw-mkt-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-mkt-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pawbytes/skill-suites paw-mkt-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/marketing/paw-mkt-setup .agents/skills/paw-mkt-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-mkt-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/marketing/paw-mkt-setup into .agents/skills/paw-mkt-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-mkt-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-mkt-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pawbytes/skill-suites paw-mkt-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/marketing/paw-mkt-setup .cursor/skills/paw-mkt-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-mkt-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/marketing/paw-mkt-setup into .cursor/skills/paw-mkt-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-mkt-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/marketing/paw-mkt-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-mkt-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pawbytes/skill-suites paw-mkt-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/marketing/paw-mkt-setup .gemini/skills/paw-mkt-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-mkt-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/marketing/paw-mkt-setup into .gemini/skills/paw-mkt-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-mkt-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-mkt-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-mkt-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/marketing/paw-mkt-setup .github/skills/paw-mkt-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-mkt-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/marketing/paw-mkt-setup into .github/skills/paw-mkt-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-mkt-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-mkt-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-mkt-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/marketing/paw-mkt-setup .opencode/skills/paw-mkt-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-mkt-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/marketing/paw-mkt-setup into .opencode/skills/paw-mkt-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-mkt-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-mkt-setupSets up Agentic Marketing Suite module in a project. An agent skill from pawbytes/skill-suites.
Paw Mkt Setup is an agent skill from pawbytes/skill-suites. Sets up Agentic Marketing Suite module in a project. Use when the user requests to 'install ams module', 'configure Agentic Marketing Suite', or 'setup Agentic Marketing Suite'.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 20 other files, including scripts and assets (for example `assets/module.yaml`, `assets/scripts/chrome-profiles.sh` and `assets/scripts/tool-discovery.sh`).
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.
3 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 9 files in scripts/ (Python, Batch and Shell), which the agent can run.
Shell commands in SKILL.md call:
python3From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
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 Mkt Setup loads about 2.3k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 867 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). 867 words, ~2,274 tokens.
.claude/skills/paw-mkt-setup/SKILL.md (or your agent's skills folder). This skill also uses 15 other files; get the full folder from GitHub.Installs and configures the Agentic Marketing Suite into a project. Module identity (name, code, version) comes from ./assets/module.yaml. Collects user preferences and writes them to:
{project-root}/.pawbytes/config/config.yaml — shared ecosystem config: core settings at root plus a section per module with metadata and module-specific values. User-only keys (user_name, communication_language) are never written here.{project-root}/.pawbytes/config/config.user.yaml — personal settings intended to be gitignored: user_name, communication_language, and any module variable marked user_setting: true. These values live exclusively here.{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 and configuration specialist for the Agentic Marketing Suite. Efficient, thorough, and user-friendly during first-time installation and configuration updates.
Warm but efficient. Guides users through configuration with clear prompts and sensible defaults. Summarizes all choices before writing files. Uses the user's name once configured.
Example interaction:
"Hi! I'll set up the Agentic Marketing Suite for you. I found 2 existing brands that I'll migrate to the new structure. I need a few details — defaults shown in brackets. Ready when you are!"
./assets/module.yaml for module metadata and variable definitions (the code field is the module identifier){project-root}/.pawbytes/config/config.yaml exists — if a section matching the module's code is already present, inform the user this is an update{project-root}/.pawbytes/marketing-suites/config/ → {project-root}/.pawbytes/config/{project-root}/brands/ → {project-root}/.pawbytes/marketing-suites/brands/{project-root}/reports/ → {project-root}/.pawbytes/marketing-suites/reports/If the user provides arguments (e.g. accept all defaults, --headless, or inline values like user name is BMad, I speak Swahili), map any provided values to config keys, use defaults for the rest, and skip interactive prompting. Still display the full confirmation summary at the end.
Before collecting configuration, check for legacy directories and automatically migrate them:
# Create new directory structure
mkdir -p "{project-root}/.pawbytes/config"
mkdir -p "{project-root}/.pawbytes/marketing-suites/brands"
mkdir -p "{project-root}/.pawbytes/marketing-suites/reports"
# Migrate legacy config folder (marketing-suites specific to ecosystem shared)
if [ -d "{project-root}/.pawbytes/marketing-suites/config" ]; then
mv "{project-root}/.pawbytes/marketing-suites/config/"* "{project-root}/.pawbytes/config/" 2>/dev/null || true
rmdir "{project-root}/.pawbytes/marketing-suites/config" 2>/dev/null || true
fi
# Migrate legacy brands folder
if [ -d "{project-root}/brands" ]; then
mv "{project-root}/brands/"* "{project-root}/.pawbytes/marketing-suites/brands/" 2>/dev/null || true
rmdir "{project-root}/brands" 2>/dev/null || true
fi
# Migrate legacy reports folder
if [ -d "{project-root}/reports" ]; then
mv "{project-root}/reports/"* "{project-root}/.pawbytes/marketing-suites/reports/" 2>/dev/null || true
rmdir "{project-root}/reports" 2>/dev/null || true
fi
# Also check skills folder for stray reports folder
if [ -d "{project-root}/skills/reports" ]; then
mv "{project-root}/skills/reports/"* "{project-root}/.pawbytes/marketing-suites/reports/" 2>/dev/null || true
rmdir "{project-root}/skills/reports" 2>/dev/null || true
fiInform the user of any migration performed: "Migrated 3 brands from brands/ to .pawbytes/marketing-suites/brands/" etc.
Ask the user for values. Show defaults in brackets. Present all values together so the user can respond once with only the values they want to change (e.g. "change language to Swahili, 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 new config values > migrated legacy 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. Ask using that prompt with its default value.
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 mktBoth scripts output JSON to stdout with results. If either exits non-zero, surface the error and stop.
Run ./scripts/merge-config.py --help or ./scripts/merge-help-csv.py --help for full usage.
After writing config, create any output directories that were configured. Resolve the {project-root} token to the actual project root and create each path-type value from config.yaml that does not yet exist:
mkdir -p "{project-root}/.pawbytes/marketing-suites/brands"
mkdir -p "{project-root}/.pawbytes/marketing-suites/reports"The paths stored in the config files must continue to use the literal {project-root} token; only the directories on disk should use the resolved paths.
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. Report any migrations performed. Then display the module_greeting from ./assets/module.yaml to the user.
Once the user's user_name and communication_language are known (from collected input, arguments, or existing config), use them consistently for the remainder of the session: address the user by their configured name and communicate in their configured communication_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 15 other files (scripts, assets) in src/marketing/paw-mkt-setup of pawbytes/skill-suites.
Open the folder on GitHubat commit 547a6df
Paw Mkt 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 Mkt Setup this skillpawbytes/skill-suites | 110 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Geo Fundamentalswasp-lang/wasp | 19k | 9 repos | ~861 | Automated safety check: Pass | MIT | |
| Ab Testingcoreyhaines31/marketingskills | 54k | 3 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Hreflang and International SEOAgriciDaniel/claude-seo | 18k | 5 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Referralscoreyhaines31/marketingskills | 54k | 2 repos | ~2.4k | Automated safety check: Pass | MIT | |
| SEO GeoReScienceLab/opc-skills | 1.8k | 4 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 |
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.
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.
coreyhaines31/marketingskills
When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.
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.
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 Agentic Marketing Suite module in a project. An agent skill from pawbytes/skill-suites. Paw Mkt Setup is an agent skill from pawbytes/skill-suites. Sets up Agentic Marketing Suite module in a project.
Paw Mkt Setup fits situations like: the user requests to install ams module; configure Agentic Marketing Suite; setup Agentic Marketing Suite.
Run `npx skills add pawbytes/skill-suites --skill paw-mkt-setup -a claude-code`. Or copy the skill folder (src/marketing/paw-mkt-setup in pawbytes/skill-suites) into .claude/skills/paw-mkt-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add pawbytes/skill-suites --skill paw-mkt-setup -a codex`. Or copy the skill folder (src/marketing/paw-mkt-setup in pawbytes/skill-suites) into .agents/skills/paw-mkt-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-mkt-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-mkt-setup, .gemini/skills/paw-mkt-setup, .github/skills/paw-mkt-setup and .opencode/skills/paw-mkt-setup in your project.
Going by SKILL.md and its folder, Paw Mkt Setup needs Python, Windows cmd and a shell for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3; A Bash shell.
SKILL.md names 1 domain. 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 Mkt 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.3k tokens (SKILL.md is roughly 9.1k 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 Mkt Setup: Geo Fundamentals (wasp-lang/wasp, 19k stars), Ab Testing (coreyhaines31/marketingskills, 54k stars), Hreflang and International SEO (AgriciDaniel/claude-seo, 18k stars) and Referrals (coreyhaines31/marketingskills, 54k 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.