skill-upstream-pr
Improve an open-source GitHub skill and open a friendly suggestion PR upstream: fork, run skill-auto-improver, attach asm eval before/after metrics. Don't use for local-only skills, authoring from scratch, bulk repos, or registry publish.
npx skills add luongnv89/asm --skill skill-upstream-pr --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Skill Upstream PR You are contributing quality improvements to someone else's open-source skill. The workflow is: fork → clone → improve via `skill-auto-improver` → push to fork → open a friendly suggestion PR upstream. You do not own the target repo. Every step assumes you are a polite contributor, not a maintainer. ## Repo Sync Before Edits (mandatory) Before any modification to the cloned fork, pull the latest from the fork's tracked branch: ```bash branch="$(git rev-parse --abbrev-ref HEAD)" git fetch origin git pull --rebase origin "$branch" ``` If the working tree is dirty: stash, sync, pop. If `origin` is missing or conflicts occur: stop and ask the user. A stale fork that PRs yesterday's tree is worse than no PR. ## When to Use - User shares a GitHub URL to a public skill repo and asks to "improve", "level up", or "contribute to" it - User says "open a PR to this skill" or "suggest improvements upstream" - The target skill scores below 85/8 on `asm eval` and the user wants the upstream author to benefit Do **not** trigger for: editing a local skill with no upstream, authoring a brand-new skill, publishing to the ASM registry, or bulk-improving many repos in one pass. One
- Repo Sync Before Edits (mandatory)
- When to Use
- Prerequisites
- Input
- Workflow
- Phase 0 — Fork and clone
- Phase 1 — Locate the target SKILL.md
- Phase 2 — Delegate to skill-auto-improver
- Phase 3 — Harvest metrics for the PR
- Phase 4 — Build the PR body
- Phase 5 — Last-mile confirmation (mandatory)
- Phase 6 — Push and open the PR
- Step Completion Reports (mandatory)
- Acceptance Criteria
git fetch origin git pull --rebase origin "$branch" cd "$(mktemp -d)" gh repo fork "$OWNER/$REPO" --clone --remote cd "$REPO" If a ref was provided: git checkout "$REF" git checkout -b "skill-upstream-pr/improve-$(date +%Y%m%d-%H%M%S)" find . -maxdepth 5 -name "SKILL.md" -type f Commit the changes
What does the skill-upstream-pr skill do?
Improve an open-source GitHub skill and open a friendly suggestion PR upstream: fork, run skill-auto-improver, attach asm eval before/after metrics. Don't use for local-only skills, authoring from scratch, bulk repos, or registry publish.
How do I install it?
Run `npx skills add luongnv89/asm --skill skill-upstream-pr --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From luongnv89/asm, a repository with 782 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
