Bundle product artifacts into a coherent, production-ready package.
$ npx skills add pawbytes/skill-suites --skill paw-ps-product-package-assembler -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pawbytes/skill-suites paw-ps-product-package-assembler --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/prodig/paw-ps-product-package-assembler .claude/skills/paw-ps-product-package-assembler && 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-ps-product-package-assembler" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-product-package-assembler into .claude/skills/paw-ps-product-package-assembler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-product-package-assembler", 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/prodig/paw-ps-product-package-assemblerType 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-ps-product-package-assembler -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pawbytes/skill-suites paw-ps-product-package-assembler --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/prodig/paw-ps-product-package-assembler .agents/skills/paw-ps-product-package-assembler && 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-ps-product-package-assembler" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-product-package-assembler into .agents/skills/paw-ps-product-package-assembler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-product-package-assembler", 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-ps-product-package-assembler -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pawbytes/skill-suites paw-ps-product-package-assembler --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/prodig/paw-ps-product-package-assembler .cursor/skills/paw-ps-product-package-assembler && 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-ps-product-package-assembler" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-product-package-assembler into .cursor/skills/paw-ps-product-package-assembler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-product-package-assembler", 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/prodig/paw-ps-product-package-assembler--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-ps-product-package-assembler -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pawbytes/skill-suites paw-ps-product-package-assembler --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/prodig/paw-ps-product-package-assembler .gemini/skills/paw-ps-product-package-assembler && 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-ps-product-package-assembler" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-product-package-assembler into .gemini/skills/paw-ps-product-package-assembler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-product-package-assembler", 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-ps-product-package-assemblerInstalls 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-ps-product-package-assembler -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/prodig/paw-ps-product-package-assembler .github/skills/paw-ps-product-package-assembler && 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-ps-product-package-assembler" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-product-package-assembler into .github/skills/paw-ps-product-package-assembler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-product-package-assembler", 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-ps-product-package-assembler -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-ps-product-package-assembler --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/prodig/paw-ps-product-package-assembler .opencode/skills/paw-ps-product-package-assembler && 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-ps-product-package-assembler" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-product-package-assembler into .opencode/skills/paw-ps-product-package-assembler/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-product-package-assembler", 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-ps-product-package-assemblerBundle product artifacts into a coherent, production-ready package.
Paw Ps Product Package Assembler is an agent skill from pawbytes/skill-suites. Bundle product artifacts into a coherent, production-ready package. Use when the user requests 'package product', 'bundle artifacts', 'assemble deliverables', 'create product package', or 'finalize outputs'.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/01-gather-artifacts.md`, `references/02-check-completeness.md` and `references/03-organize-bundle.md`).
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.
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 (its code samples are yaml).
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 Ps Product Package Assembler loads about 1.5k tokens when it runs, and up to ~5.8k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 491 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). 491 words, ~1,525 tokens.
.claude/skills/paw-ps-product-package-assembler/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.This workflow bundles product artifacts from the execution phase into a coherent, production-ready package. It ensures outputs feel like one unified product, not scattered drafts, by gathering executor outputs, verifying completeness against product-type requirements, organizing into a structured bundle, and generating a comprehensive manifest.
Args: Accepts --headless / -H for non-interactive execution.
Output: Packaged product bundle with organized directory structure, completeness report, and packaging manifest.
The Non-Negotiable: Must ensure outputs feel like one product, not scattered drafts.
Load available config from {project-root}/.pawbytes/config/config.yaml and {project-root}/.pawbytes/config/config.user.yaml (root level and ps section). If config is missing, let the user know paw-ps-setup can configure the module at any time. Resolve:
{user_name} (null) — address the user by name{communication_language} (English) — use for all communications{document_output_language} (English) — use for generated document content{output_directory} (.pawbytes/prodig-suites) — base output pathLoad shared memory from {project-root}/.pawbytes/prodig-suites/index.md. Load output standards from {project-root}/.pawbytes/prodig-suites/output-standards.md.
Product context resolution: Identify the active product from memory or accept a product slug as argument. The product workspace is expected at .pawbytes/prodig-suites/products/{product-slug}/. If no product can be resolved, ask the user.
If --headless or -H is passed, run the full pipeline without interaction: gather artifacts, check completeness, organize bundle, generate manifest.
Otherwise, greet the user, confirm the target product, and proceed through the stages below.
This workflow progresses through four stages. Each stage updates the packaging status file using the document-as-cache pattern for compaction survival.
| Stage | Purpose | Reference |
|---|---|---|
| 1. Gather Artifacts | Collect all execution artifacts from executors | Load ./references/01-gather-artifacts.md |
| 2. Check Completeness | Verify against product-type requirements | Load ./references/02-check-completeness.md |
| 3. Organize Bundle | Structure into coherent package | Load ./references/03-organize-bundle.md |
| 4. Generate Manifest | Create package manifest and notes | Load ./references/04-generate-manifest.md |
Progression: Each stage updates packaging-status.md with its results before loading the next stage. If interrupted, resume from the last completed stage by reading packaging-status.md.
All progress is written to {project-root}/.pawbytes/prodig-suites/products/{product-slug}/packaging-status.md. This file is both the output artifact and the recovery cache.
---
product: '{product-slug}'
status: 'in-progress' # pending | in-progress | complete | incomplete
current_stage: '01-gather-artifacts'
created: 'ISO-8601'
updated: 'ISO-8601'
artifacts_found: 0
artifacts_packaged: 0
missing_items: []
---Artifacts are collected from executor outputs:
| Source | Contains | Manifest File |
|---|---|---|
| Discovery agents | Research reports, briefs, specs | discovery-manifest.json |
| Strategist | Strategy documents, plans | strategy-manifest.json |
| Executor agents | Content, code, designs, media | executor-manifest.json |
| Synthesis workflows | Integrated deliverables | synthesis-manifest.json |
Different product types have different required artifacts:
| Product Type | Required Artifacts |
|---|---|
| Document | Main document, outline, research notes |
| Application | Code package, README, documentation |
| Campaign | Creative assets, copy, strategy brief |
| Report | Report document, data sources, methodology |
| Presentation | Slide deck, speaker notes, handouts |
.pawbytes/prodig-suites/products/{product-slug}/package/
├── manifest.json # Package manifest
├── completeness-report.md # What's present, what's missing
├── packaging-notes.md # Special considerations
├── artifacts/ # All gathered artifacts
│ ├── {artifact-1}
│ ├── {artifact-2}
│ └── ...
└── metadata/ # Supporting metadata
├── source-manifests/
└── audit-trail.jsonReads:
{project-root}/.pawbytes/prodig-suites/index.md — module state{project-root}/.pawbytes/prodig-suites/output-standards.md — output standards{project-root}/.pawbytes/prodig-suites/products/{product-slug}/product-context.md — product contextWrites:
{project-root}/.pawbytes/prodig-suites/products/{product-slug}/packaging-status.md — packaging progress{project-root}/.pawbytes/prodig-suites/products/{product-slug}/package/ — packaged bundle{project-root}/.pawbytes/prodig-suites/daily/{date}.md — daily log (append, tagged [Packaging])| Signal | Routes To |
|---|---|
| Missing executor outputs | paw-ps-agent-product-builder (to rerun execution) |
| Incomplete artifacts | Appropriate executor agent |
| Quality issues | paw-ps-quality-reviewer |
| Export needs | paw-ps-export-handler |
Every packaging deliverable includes:
© 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 4 other files (references) in src/prodig/paw-ps-product-package-assembler of pawbytes/skill-suites.
Open the folder on GitHubat commit 547a6df
Paw Ps Product Package Assembler 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 Ps Product Package Assembler this skillpawbytes/skill-suites | 113 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Rig Bundles And Shareable Artifactsmvschwarz/openrig | 6.2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Web Artifacts Builderanthropics/skills | 180k | 41 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| Cohere Debug Bundlejeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| FHIR Bundle Assemblermaziyarpanahi/openmed | 5.5k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Artifacts Buildernexu-io/open-design | 100k | — | ~347 | Automated safety check: Pass | Apache-2.0 |
mvschwarz/openrig
A skill your agent uses when authoring or installing a rig bundle (packaged, shareable artifact that instantiates an opinionated OpenRig topology + workflow), reasoning about the bundle vs extension…
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
jeremylongshore/tons-of-skills-marketplace
Collect a minimal redacted Cohere diagnostic bundle with versions, request shape, timing, status, and reproduction evidence.
maziyarpanahi/openmed
Packages standalone FHIR R4 resources from OpenMed output into one transaction Bundle with stable fullUrls and rewritten references, ready to post to a FHIR server.
nexu-io/open-design
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).
nexu-io/open-design
Build complex claude.ai HTML artifacts with React and Tailwind.
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.
Bundle product artifacts into a coherent, production-ready package. Paw Ps Product Package Assembler is an agent skill from pawbytes/skill-suites. Bundle product artifacts into a coherent, production-ready package.
Paw Ps Product Package Assembler fits situations like: the user requests package product; bundle artifacts; assemble deliverables; create product package.
Run `npx skills add pawbytes/skill-suites --skill paw-ps-product-package-assembler -a claude-code`. Or copy the skill folder (src/prodig/paw-ps-product-package-assembler in pawbytes/skill-suites) into .claude/skills/paw-ps-product-package-assembler in your project. Claude Code loads it when a task matches its description.
Run `npx skills add pawbytes/skill-suites --skill paw-ps-product-package-assembler -a codex`. Or copy the skill folder (src/prodig/paw-ps-product-package-assembler in pawbytes/skill-suites) into .agents/skills/paw-ps-product-package-assembler 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-ps-product-package-assembler -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-ps-product-package-assembler, .gemini/skills/paw-ps-product-package-assembler, .github/skills/paw-ps-product-package-assembler and .opencode/skills/paw-ps-product-package-assembler in your project.
SKILL.md names no scripts, command-line tools or credentials: Paw Ps Product Package Assembler 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 Ps Product Package Assembler is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.2k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Paw Ps Product Package Assembler: Rig Bundles And Shareable Artifacts (mvschwarz/openrig, 6.2k stars), Web Artifacts Builder (anthropics/skills, 180k stars), Cohere Debug Bundle (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and FHIR Bundle Assembler (maziyarpanahi/openmed, 5.5k 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 113 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.
