What is skillshare-app-pr?

A workflow for taking a requested change in the Skillshare desktop app through a branch, implementation, checks, review, and merge. A pull request is a proposed code change that others review before it is merged.

Use it for code, user-interface, icon, or documentation changes that need a tested pull request and merge.

It reduces missed checks and incomplete updates by requiring related code, tests, documentation, and visible changes to be handled together.

skillshare-app-pr — Skill for Claude Code and Codex by runkids

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add runkids/skillshare-app --skill skillshare-app-pr

Clone the repo

git clone --depth 1 https://github.com/runkids/skillshare-app

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/runkids/skillshare-app/skillshare-app-pr/github.svg)](https://agentmods.dev/skills/runkids/skillshare-app/skillshare-app-pr)

Your own site

<a href="https://agentmods.dev/skills/runkids/skillshare-app/skillshare-app-pr"><img src="https://agentmods.dev/badge/skills/runkids/skillshare-app/skillshare-app-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/runkids/skillshare-app/skillshare-app-pr"><img src="https://agentmods.dev/badge/skills/runkids/skillshare-app/skillshare-app-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 143 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 750 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00143	$0.00750
Opus 5.5	$0.00057	$0.00300
Sonnet 5.5	$0.00029	$0.00150
Haiku 4.5	$0.00014	$0.00075

Measured 12d ago against content hash e801ffb51368, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

skillshare-app-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.skillshare/skills/skillshare-app-pr/SKILL.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Land a change in skillshare-app

The facts and rules live in the wiki. This skill only orders the steps. Before step 1, load python3 scripts/ai-context.py development, plus the one topic for the area you are changing (frontend, architecture, background-services).

Steps

1. Branch

Run git fetch and check git status in the main checkout. Leave the user's uncommitted work alone.
Create a worktree on a new branch from origin/main, as "Shipping a change" describes.
If several requests arrive together, handle them in one PR only when they touch the same files. Otherwise use one PR each.

2. Change

Before editing, rg every use of anything you will change or remove: commands, the bridge, settings fields, capabilities, tests, wiki and README.
When you remove a feature, remove all of it: UI, Rust commands, plugins, capabilities, CliMeta fields, lockfiles, tests and docs. Then rg again until nothing is left.
Update the wiki topics and README that describe the old behavior in the same change.

3. Verify

Run every command in the "Verifying a change" table and fix whatever fails.
For anything visible, apply the branch to the main checkout and take screenshots in noVNC. Read each image before you call it verified. Then revert the main checkout.
If the user sends a screenshot, read it first. Convert it with sips when it is not a real PNG.

4. Pull request

Commit, push and run gh pr create with the What/Verification body.
The user has delegated merging, so run scripts/merge-pr.sh <pr> in the background and keep working.
On a real failure, read gh run view <id> --log-failed, fix it, push a new commit, and run the script again.

5. Finish

Pull main into the main checkout and remove the worktree.
Tell the user, in their language:
- what changed and the PR link
- what was verified, and how: tests or screenshots
- anything assumed or left out
Offer a release in one line. Release only when they ask, using skillshare-app-release.

Read the full file on GitHub · 71 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 71 lines · 143 tokens per session scan A e801ffb51368

Subscribe to this mod's changes

skillshare-app-pr is a skill published in the GitHub repository runkids/skillshare-app (24 stars, last pushed yesterday), licensed MIT. It adds 143 tokens to every session and 750 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-04.

Commits Git and workflow automation desktop-app developer-tools macos package-manager tauri

oz-report-pr

Report a pull request back to the Oz platform after creating one.

warpdotdev/warp · 17 tokens

app-release

Use when the user asks to release a new version, ship a build, or publish a Skill Zoo release. Also use when a tag push results in Homebrew 404 errors or missing artifact failures.

luochang212/skill-zoo · 43 tokens

commit

Use when making any git commit. Pass the failure, false claim, or risk the changes fix as the argument; for an addition or a filled gap, pass what it adds — never an invented why.

vinta/hal-9000 · 43 tokens

npm-release

Use when publishing or preparing to publish an npm package from this repository, especially the Skill Zoo CLI package under packages/cli. Also use when npm publish fails because of duplicate versions, npm authentication, browser authentication, dist-tag propagation, tarball contents, bin entry issues, or…

luochang212/skill-zoo · 66 tokens

vellum-github-app-setup

Create and configure a GitHub App so the assistant can push commits, open PRs, and comment under its own bot identity. Use when the user wants the assistant to have its own GitHub identity, or when setting up git push access for the first time.

vellum-ai/vellum-assistant · 61 tokens

avatar-contribution-pr

Turn an avatar GitHub issue (from the in-app avatar-editor easter egg) into a merged sprite — validate the art, then either add a new module or replace an existing one, and open a PR that closes the issue. Handles both "Avatar contribution: " (a brand-new sprite) and "Avatar edit: " (a hand-redraw of an existing…

khromov/codebay · 0 tokens