paw-tools-setup
Sets up Pawbytes Tools module in a project. Use when the user requests to 'install paw tools', 'configure Pawbytes Tools', or 'setup utility tools'.
How do I install this agent skill?
npx skills add https://github.com/pawbytes/skill-suites --skill paw-tools-setupIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill installs and configures project utility tools for the Pawbytes ecosystem. It handles configuration and API keys by storing them in designated local files. It also includes a utility script for migrating legacy project file structures to current formats. No malicious patterns or data exfiltration attempts were detected.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Pawbytes Tools Setup
Overview
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: core keys at the root, this module's keys in thetoolssection (thecodeinmodule.yaml){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. {skill-root} is this skill's folder; run its scripts as uv run {skill-root}/scripts/<name>.py.
On Activation
- Read
./assets/module.yamlfor module metadata and variable definitions - Check if
{project-root}/.pawbytes/config/config.yamlexists — if present, inform the user this is an update. Older installs may have left these keys at the root of the file (or underpaw); move them into thetoolssection and treat them as existing values.
If 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.
Collect Configuration
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 Files
Write the collected configuration to:
{project-root}/.pawbytes/config/config.yaml
User-specific settings (API keys) go to:
{project-root}/.pawbytes/config/config.user.yaml
Write communication_language and document_output_language at the root and every other module key under tools: (in config.user.yaml for the user_setting keys). Create directories if they don't exist.
Create Output Directories
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.
Migrate Legacy Files
Output lives in {project-root}/paw-suites/tools/ (presentations/, releases/, a generated README.md); older releases wrote to .pawbytes/tools-output/. Run uv run {skill-root}/scripts/paw-paths.py detect. When it reports legacy or both, run paw-paths.py plan, show its summary along with any conflicts, and run paw-paths.py apply once the user confirms (it also rewrites the old default folders in the tools section). Report what moved and what stayed (MOVED.md in the old folder lists it), then run paw-paths.py index.
Confirm
Display what was written — config values set, fresh install vs update, and any migration. Then display the greeting from ./assets/module.yaml to the user.
Outcome
Once the user's communication_language is known (from collected input, arguments, or existing config), use it consistently for the remainder of the session.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/pawbytes/skill-suites/paw-tools-setup">View paw-tools-setup on skillZs</a>