How do I install the Om Auto Publish Pr skill?

Run npx skillmds@latest add open-mercato/om-auto-publish-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Om Auto Publish Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Om Auto Publish Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Om Auto Publish Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Om Auto Publish Pr?

open-mercato (@open-mercato) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Om Auto Publish Pr by open-mercato — Agent Skill

Name: Om Auto Publish Pr
Author: open-mercato

Om Auto Publish Pr

Publish pkg.pr.new package previews for a same-repository Open Mercato PR by dispatching the Package Previews GitHub Actions workflow with gh. Use when a maintainer asks to publish, republish, or trigger a PR package preview. Does not publish npm snapshots.

open-mercato Updated Sep 17, 2026

File contents

Auto Publish PR Preview

Dispatch the Package Previews workflow for a PR. This publishes pkg.pr.new previews only; do not invoke NPM Snapshot Preview from this skill.

Arguments

{pr_number} (required) - Pull request number to publish previews for.
--repo <owner/name> (optional) - Defaults to the current repository.
--ref <branch> (optional) - Workflow definition ref. Default: develop.

Procedure

Resolve inputs and confirm the PR exists:

REPO="${REPO:-$(gh repo view --json nameWithOwner --jq .nameWithOwner)}"
PR_NUMBER="{pr_number}"
WORKFLOW_REF="${WORKFLOW_REF:-develop}"

gh pr view "$PR_NUMBER" --repo "$REPO" \
  --json number,title,headRepositoryOwner,headRefName,headRefOid,isCrossRepository

If isCrossRepository is true, stop. The workflow rejects fork PRs because it runs publish-capable automation from a trusted workflow context.
Dispatch the preview workflow:

gh workflow run package-previews.yml \
  --repo "$REPO" \
  --ref "$WORKFLOW_REF" \
  -f "pr_number=$PR_NUMBER"

Find the newest run for the workflow and report it:

sleep 3
gh run list \
  --repo "$REPO" \
  --workflow package-previews.yml \
  --limit 5

Final response must include:

PR number and title.
The workflow ref used.
The dispatch command result.
The newest relevant run URL when available.

Guardrails

Do not commit, push, label, or merge anything.
Do not dispatch npm-snapshot-preview.yml; that is intentionally a separate manual path.
If the workflow is not found on develop, tell the user to pass --ref <branch-with-workflow> or wait until the workflow change is merged.

---name: om-auto-publish-prdescription: Publish pkg.pr.new package previews for a same-repository Open Mercato PR by dispatching the Package Previews GitHub Actions workflow with gh. Use when a maintainer asks to publish, republish, or trigger a PR package preview. Does not publish npm snapshots.---# Auto Publish PR PreviewDispatch the `Package Previews` workflow for a PR. This publishes pkg.pr.new previews only; do not invoke `NPM Snapshot Preview` from this skill.## Arguments- `{pr_number}` (required) - Pull request number to publish previews for.- `--repo <owner/name>` (optional) - Defaults to the current repository.- `--ref <branch>` (optional) - Workflow definition ref. Default: `develop`.## Procedure1. Resolve inputs and confirm the PR exists:```bashREPO="${REPO:-$(gh repo view --json nameWithOwner --jq .nameWithOwner)}"PR_NUMBER="{pr_number}"WORKFLOW_REF="${WORKFLOW_REF:-develop}"gh pr view "$PR_NUMBER" --repo "$REPO" \ --json number,title,headRepositoryOwner,headRefName,headRefOid,isCrossRepository```2. If `isCrossRepository` is `true`, stop. The workflow rejects fork PRs because it runs publish-capable automation from a trusted workflow context.3. Dispatch the preview workflow:```bashgh workflow run package-previews.yml \ --repo "$REPO" \ --ref "$WORKFLOW_REF" \ -f "pr_number=$PR_NUMBER"```4. Find the newest run for the workflow and report it:```bashsleep 3gh run list \ --repo "$REPO" \ --workflow package-previews.yml \ --limit 5```5. Final response must include:- PR number and title.- The workflow ref used.- The dispatch command result.- The newest relevant run URL when available.## Guardrails- Do not commit, push, label, or merge anything.- Do not dispatch `npm-snapshot-preview.yml`; that is intentionally a separate manual path.- If the workflow is not found on `develop`, tell the user to pass `--ref <branch-with-workflow>` or wait until the workflow change is merged.

Frequently asked questions