Manage Settings
asgeirtj/system_prompts_leaks
Any explicit Muse Code setting question or change (model, reasoning effort, /settings) requires a silent readskill call for bundled:manage-settings as FIRST ACTION—no assistant text or other tool…
Sets up Pawbytes Tools module in a project. An agent skill from pawbytes/skill-suites.
$ npx skills add pawbytes/skill-suites --skill paw-tools-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pawbytes/skill-suites paw-tools-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/tools/paw-tools-setup .claude/skills/paw-tools-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-tools-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/tools/paw-tools-setup into .claude/skills/paw-tools-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-tools-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/tools/paw-tools-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-tools-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pawbytes/skill-suites paw-tools-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/tools/paw-tools-setup .agents/skills/paw-tools-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-tools-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/tools/paw-tools-setup into .agents/skills/paw-tools-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-tools-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-tools-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pawbytes/skill-suites paw-tools-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/tools/paw-tools-setup .cursor/skills/paw-tools-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-tools-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/tools/paw-tools-setup into .cursor/skills/paw-tools-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-tools-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/tools/paw-tools-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-tools-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pawbytes/skill-suites paw-tools-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/tools/paw-tools-setup .gemini/skills/paw-tools-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-tools-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/tools/paw-tools-setup into .gemini/skills/paw-tools-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-tools-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-tools-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-tools-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/tools/paw-tools-setup .github/skills/paw-tools-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-tools-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/tools/paw-tools-setup into .github/skills/paw-tools-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-tools-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-tools-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-tools-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/tools/paw-tools-setup .opencode/skills/paw-tools-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-tools-setup" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/tools/paw-tools-setup into .opencode/skills/paw-tools-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-tools-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-tools-setupSets up Pawbytes Tools module in a project. An agent skill from pawbytes/skill-suites.
Paw Tools Setup is an agent skill from pawbytes/skill-suites. Sets up Pawbytes Tools module in a project. Use when the user requests to 'install paw tools', 'configure Pawbytes Tools', or 'setup utility tools'.
Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including assets (for example `assets/module.yaml`).
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.
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.
No URLs in SKILL.md.
From 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 Tools Setup loads about 639 tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 306 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); files beside SKILL.md are not scanned.
The full file from pawbytes/skill-suites at commit 547a6df, republished under its MIT licence (© pawbytes). 306 words, ~639 tokens.
.claude/skills/paw-tools-setup/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Installs and configures Pawbytes Tools module into a project. Collects user preferences and writes them to:
{project-root}/.pawbytes/config/config.yaml — shared Pawbytes ecosystem configuration{project-root}/.pawbytes/config/config.user.yaml — personal settings (gitignored, contains API keys){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.
./assets/module.yaml for module metadata and variable definitions{project-root}/.pawbytes/config/config.yaml exists — if present, inform the user this is an updateIf the user provides arguments (e.g. accept all defaults, --headless, or inline values), map provided values to config keys, use defaults for the rest, and skip interactive prompting.
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 config values > ./assets/module.yaml defaults.
Module config: Read each variable in ./assets/module.yaml that has a prompt field. Ask using that prompt with its default value (or existing value if available).
Write the collected configuration to:
{project-root}/.pawbytes/config/config.yamlUser-specific settings (API keys) go to:
{project-root}/.pawbytes/config/config.user.yamlCreate directories if they don't exist.
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 that does not yet exist. Use mkdir -p or equivalent.
Display what was written — config values set, fresh install vs update. Then display the greeting from ./assets/module.yaml to the user.
Once the user's communication_language is known (from collected input, arguments, or existing config), use it consistently for the remainder of the session.
© 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 2 other files (assets) in src/tools/paw-tools-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 Tools 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 Tools Setup this skillpawbytes/skill-suites | 110 | 1 repos | ~639 | Automated safety check: Pass | MIT | |
| Manage Settingsasgeirtj/system_prompts_leaks | 69k | — | ~3.1k | Automated safety check: Pass | CC0-1.0 | |
| Warp Settings Editorwarpdotdev/warp | 65k | 1 repos | ~675 | Automated safety check: Pass | AGPL-3.0 | |
| Es Modulesthedaviddias/Front-End-Checklist | 74k | — | ~482 | Automated safety check: Pass | MIT | |
| Warp Settings Page Builderwarpdotdev/warp | 65k | 1 repos | ~4.5k | Automated safety check: Pass | AGPL-3.0 | |
| Add Server Env Var for User Settinglobehub/lobehub | 83k | — | ~644 | Automated safety check: Pass | Custom licence |
asgeirtj/system_prompts_leaks
Any explicit Muse Code setting question or change (model, reasoning effort, /settings) requires a silent readskill call for bundled:manage-settings as FIRST ACTION—no assistant text or other tool…
warpdotdev/warp
Finds and changes Warp application settings by searching a bundled JSON schema and editing the matching TOML settings file at the right nesting depth.
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Use ES modules (import/export).
warpdotdev/warp
How to build a settings page in the Warp desktop client so widgets, page titles and settings search behave correctly, and which common mistakes to avoid.
lobehub/lobehub
Adds a server-side environment variable that sets the default for a user setting in LobeHub, wired from the env schema through server config to the user store and docs.
simstudioai/sim
Add a new Sim settings page, or audit existing settings pages for design-system compliance with the shared SettingsPanel layout.
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.
Sets up Pawbytes Tools module in a project. An agent skill from pawbytes/skill-suites. Paw Tools Setup is an agent skill from pawbytes/skill-suites. Sets up Pawbytes Tools module in a project.
Paw Tools Setup fits situations like: the user requests to install paw tools; configure Pawbytes Tools; setup utility tools.
Run `npx skills add pawbytes/skill-suites --skill paw-tools-setup -a claude-code`. Or copy the skill folder (src/tools/paw-tools-setup in pawbytes/skill-suites) into .claude/skills/paw-tools-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add pawbytes/skill-suites --skill paw-tools-setup -a codex`. Or copy the skill folder (src/tools/paw-tools-setup in pawbytes/skill-suites) into .agents/skills/paw-tools-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-tools-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-tools-setup, .gemini/skills/paw-tools-setup, .github/skills/paw-tools-setup and .opencode/skills/paw-tools-setup in your project.
SKILL.md names no scripts, command-line tools or credentials: Paw Tools Setup is instructions for the agent only.
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.
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.
Paw Tools 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 639 tokens (SKILL.md is roughly 2.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 Tools Setup: Manage Settings (asgeirtj/system_prompts_leaks, 69k stars), Warp Settings Editor (warpdotdev/warp, 65k stars), Es Modules (thedaviddias/Front-End-Checklist, 74k stars) and Warp Settings Page Builder (warpdotdev/warp, 65k 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.