Publish
code-yeongyu/oh-my-openagent
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts.
Evaluate whether a product is production-ready, publish-ready, or sellable-ready.
$ npx skills add pawbytes/skill-suites --skill paw-ps-publish-ready-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pawbytes/skill-suites paw-ps-publish-ready-check --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-publish-ready-check .claude/skills/paw-ps-publish-ready-check && 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-publish-ready-check" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-publish-ready-check into .claude/skills/paw-ps-publish-ready-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-publish-ready-check", 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-publish-ready-checkType 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-publish-ready-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pawbytes/skill-suites paw-ps-publish-ready-check --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-publish-ready-check .agents/skills/paw-ps-publish-ready-check && 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-publish-ready-check" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-publish-ready-check into .agents/skills/paw-ps-publish-ready-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-publish-ready-check", 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-publish-ready-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pawbytes/skill-suites paw-ps-publish-ready-check --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-publish-ready-check .cursor/skills/paw-ps-publish-ready-check && 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-publish-ready-check" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-publish-ready-check into .cursor/skills/paw-ps-publish-ready-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-publish-ready-check", 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-publish-ready-check--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-publish-ready-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pawbytes/skill-suites paw-ps-publish-ready-check --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-publish-ready-check .gemini/skills/paw-ps-publish-ready-check && 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-publish-ready-check" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-publish-ready-check into .gemini/skills/paw-ps-publish-ready-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-publish-ready-check", 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-publish-ready-checkInstalls 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-publish-ready-check -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-publish-ready-check .github/skills/paw-ps-publish-ready-check && 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-publish-ready-check" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-publish-ready-check into .github/skills/paw-ps-publish-ready-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-publish-ready-check", 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-publish-ready-check -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-publish-ready-check --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-publish-ready-check .opencode/skills/paw-ps-publish-ready-check && 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-publish-ready-check" agent skill from https://github.com/pawbytes/skill-suites/tree/main/src/prodig/paw-ps-publish-ready-check into .opencode/skills/paw-ps-publish-ready-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paw-ps-publish-ready-check", 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-publish-ready-checkEvaluate whether a product is production-ready, publish-ready, or sellable-ready.
Paw Ps Publish Ready Check is an agent skill from pawbytes/skill-suites. Evaluate whether a product is production-ready, publish-ready, or sellable-ready. Triggers: 'publish ready', 'ready check', 'readiness review', 'quality check', 'production ready', 'sellable ready', 'can I publish', 'release check', 'final review'.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `references/01-load-bundle.md`, `references/02-assess-quality.md` and `references/03-check-gaps.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.
4 steps, taken from the step headings 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 Ps Publish Ready Check loads about 1.7k tokens when it runs, and up to ~7.9k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 641 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). 641 words, ~1,680 tokens.
.claude/skills/paw-ps-publish-ready-check/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.A rigorous quality evaluation workflow that determines whether a product meets the threshold for production, publication, or sale. This workflow protects the suite from overclaiming readiness by applying clear quality bars rather than superficial approval.
Args: Accepts --headless / -H for non-interactive execution.
Output: Readiness report (HTML), gap analysis, final verdict with fix list if applicable.
Load ./references/01-load-bundle.md
Gather the packaged product bundle and locate all relevant standards and context files. Establish what type of product is being evaluated and which standards apply.
Progression: Proceed when product bundle is located and product type is identified.
Load ./references/02-assess-quality.md
Apply quality standards systematically across all dimensions: functionality, completeness, clarity, usability, and documentation. Score each dimension against defined criteria.
Progression: Proceed when all quality dimensions have been assessed and scored.
Load ./references/03-check-gaps.md
Identify what specifically blocks release. Classify gaps as critical (must fix), important (should fix), or minor (nice to have). Generate actionable fix list.
Progression: Proceed when all gaps are documented with severity classification.
Load ./references/04-generate-verdict.md
Make final determination: production-ready, publish-ready, sellable-ready, or not-ready. Apply the appropriate threshold based on the target readiness level.
Progression: Complete when verdict is issued and documented.
{project-root}/.pawbytes/prodig-suites/.pawbytes/prodig-suites/active-product.md if it exists| Level | Definition | Quality Bar |
|---|---|---|
| Production-ready | Complete, functional, usable by intended audience | Core functionality works, documentation adequate, no critical bugs |
| Publish-ready | Formatted, polished, ready for publication platform | Production-ready + professional presentation, platform requirements met |
| Sellable-ready | Complete, polished, has all selling assets | Publish-ready + marketing assets, pricing, support materials |
Hierarchy: Sellable-ready requires publish-ready, which requires production-ready.
| Source | File Path | Purpose |
|---|---|---|
| Product Bundle | .pawbytes/prodig-suites/products/{product-slug}/bundle/ | Packaged product files |
| Output Standards | .pawbytes/prodig-suites/memory/paw-ps-sidecar/curated/output-standards.md | Quality criteria |
| Product Context | .pawbytes/prodig-suites/products/{product-slug}/product-context.md | Product type and requirements |
| Product Brief | .pawbytes/prodig-suites/products/{product-slug}/product-brief.md | Scope and promises |
| Product Decisions | .pawbytes/prodig-suites/products/{product-slug}/product-decisions.md | Prior decisions |
Minimum Requirement: Product bundle must exist. Standards may be loaded from references if not in workspace.
.pawbytes/prodig-suites/products/{product-slug}/
├── readiness-report.html # Structured assessment (HTML)
├── readiness-report.md # Plain text version
├── gap-analysis.md # Detailed gap breakdown
├── fix-list.md # Actionable fixes (if not ready)
└── product-decisions.md # Appended verdictDaily log entry at:
.pawbytes/prodig-suites/memory/paw-ps-sidecar/daily/YYYY-MM-DD.md./references/readiness-criteria.csv — lightweight index of criteria by product type./references/frameworks/ only when neededEvery execution delivers:
readiness-report.html — Structured assessmentreadiness-report.md — Plain text versiongap-analysis.md — Gap breakdownfix-list.md — (If not ready) Actionable fixes.pawbytes/prodig-suites/products/{product-slug}/When invoked with --headless or -H:
.pawbytes/prodig-suites/active-product.mdpublish-ready unless specified via args| Stage | Gate Condition |
|---|---|
| Load Bundle | Product bundle located, product type identified |
| Assess Quality | All quality dimensions scored |
| Check Gaps | All gaps documented with severity |
| Generate Verdict | Verdict issued with justification |
This workflow must apply clear quality bars, not superficial approval:
| Signal | Routes To | Why |
|---|---|---|
| Quality issues found | paw-ps-agent-product-builder | Coordinate fixes with specialists |
| Standards unclear | paw-ps-strategist | Clarify quality requirements |
| Multiple products to check | paw-ps-agent-product-builder | Batch coordination |
© 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 5 other files (references) in src/prodig/paw-ps-publish-ready-check of pawbytes/skill-suites.
Open the folder on GitHubat commit 547a6df
Paw Ps Publish Ready Check 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 Publish Ready Check this skillpawbytes/skill-suites | 113 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Publishcode-yeongyu/oh-my-openagent | 70k | — | ~5.5k | Automated safety check: Warn | Custom licence | |
| Social Publisheraffaan-m/ECC | 277k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Arize Evaluatorgithub/awesome-copilot | 40k | 1 repos | ~8.1k | Automated safety check: Notes | MIT | |
| Publishyc-software/qm | 15k | — | ~2.2k | Automated safety check: Warn | MIT | |
| LLM Evaluationdavila7/claude-code-templates | 33k | 12 repos | ~3.5k | Automated safety check: Pass | MIT |
code-yeongyu/oh-my-openagent
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts.
affaan-m/ECC
Agent-driven scheduling and publishing of social media posts across 13 platforms via SocialClaw.
github/awesome-copilot
Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and…
yc-software/qm
Publish a long-lived internal web app, site, or dashboard from the agent computer.
davila7/claude-code-templates
Master comprehensive evaluation strategies for LLM applications, from automated metrics to human evaluation and A/B testing.
sickn33/agentic-awesome-skills
Evaluate agent behavior with versioned cases and explicit verifiers.
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.
Evaluate whether a product is production-ready, publish-ready, or sellable-ready. Paw Ps Publish Ready Check is an agent skill from pawbytes/skill-suites. Evaluate whether a product is production-ready, publish-ready, or sellable-ready.
Run `npx skills add pawbytes/skill-suites --skill paw-ps-publish-ready-check -a claude-code`. Or copy the skill folder (src/prodig/paw-ps-publish-ready-check in pawbytes/skill-suites) into .claude/skills/paw-ps-publish-ready-check in your project. Claude Code loads it when a task matches its description.
Run `npx skills add pawbytes/skill-suites --skill paw-ps-publish-ready-check -a codex`. Or copy the skill folder (src/prodig/paw-ps-publish-ready-check in pawbytes/skill-suites) into .agents/skills/paw-ps-publish-ready-check 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-publish-ready-check -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-publish-ready-check, .gemini/skills/paw-ps-publish-ready-check, .github/skills/paw-ps-publish-ready-check and .opencode/skills/paw-ps-publish-ready-check in your project.
SKILL.md names no scripts, command-line tools or credentials: Paw Ps Publish Ready Check 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 Publish Ready Check 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.7k tokens (SKILL.md is roughly 6.7k 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 6.2k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Paw Ps Publish Ready Check: Publish (code-yeongyu/oh-my-openagent, 70k stars), Social Publisher (affaan-m/ECC, 277k stars), Arize Evaluator (github/awesome-copilot, 40k stars) and Publish (yc-software/qm, 15k 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.