claude-plugins

My own engineering contributions to the exciting and brand new field of cognitive instructions describing how to do a thing.

Version: 1.16.1 · Site: cportka.github.io/claude-plugins · License: MIT · Changelog: CHANGELOG.md · Roadmap: IMPROVEMENTS.md · Maintainers: docs/HANDOFF.md · Privacy: PRIVACY.md · Security: SECURITY.md

The portka-tools Claude Code plugin marketplace. Add it once; plugins then work in your local CLI and in ephemeral web sessions.

Plugins

Plugin	Version	What it does
video-bug-analyzer	1.16.1	Analyze a screen recording — or reason over any clip's look + motion. Extract frames (contact sheet, scene cuts, per-timestamp zoom + before/after strips, ROI time-stack --stack, deduped distinct poses + cadence --unique) plus analysis modes: black-screen detection, ROI OCR, feature measurement, palettes (--palette, --palette --over-time for the colour arc), --loop-check (seamless-loop seam diff), cross-clip diff/compare, stutter / dropped-frame + freeze gaps (--stutter), hang/loop detection (--stall), blown-highlight + dropout (--whiteout), frame-pacing jitter (--pacing), motion, swirl-vs-suck flow (--flow), subject extent (--occupancy) & saturation timelines — with a coord-free --edge side:px crop for edge-clipping questions. Doubles as an art/colour-reference tool (GIF input works everywhere). Runs never overwrite a previous extraction; --check-update spots a stale install.
repo-bootstrap	1.16.1	Onboard a repo to this marketplace — safely merge .claude/settings.json (+ optional CI), with --list/--dry-run/--print-only and a one-paste /plugin CLI fallback. With --portka-standard, install the Portka contract: describe a feature and it's understood Claude branches fresh from main, builds + tests, opens the PR, merges on CI green, and hands the link back (branch deletion = confirmation). Ships a version-stamped workflow CLAUDE.md (a SessionStart hook flags stale copies), a committed .claude/commit-identity applied to git config immediately at bootstrap and again each session, a permissions allowlist for the loop plus a deny list for what it forbids, an enforced SemVer sync bound to the repo's existing version + tests (native node:test/unittest for JS/Python), and the corrected stop-hook that ends squash-merge authorship false-flags.
app-website-evaluator	1.16.1	Evaluate an app/website with a standardized, coverage-honest scorecard — each dimension 0–100 + letter grade, a weighted overall that's starred when unassessed weight is excluded, and optional --json. Scores a live --url, a local --dir build, or pre-fetched --html (a file or stdin, optionally --headers) so an agent behind a sandbox egress proxy still gets the full scorecard without curl reaching the origin. Security now credits source-visible controls a static host can ship (a <meta> CSP, security.txt, zero third-party <script> origins). AI-readiness parse-validates JSON-LD and credits rich schema types. Covers SEO, crawlability, AI-readiness, social/sharing, security, performance, and growth — tailored to the site's type and community.
tab-chord-formatter	1.13.0	Format a messy guitar tab/chord sheet into a clean, readable layout for screen, or render a consistent monospace PDF songbook (one or many songs, a target songs-per-page) — standardized [Section] labels, chords aligned over the right lyrics, a tidy metadata header, and well-formed 6-line ASCII tab blocks.

Add a plugin

You never copy plugin code into your repo — only a marketplace reference.

• All local repos (CLI): /plugin marketplace add cportka/claude-plugins, then /plugin install video-bug-analyzer@portka-tools (or any <name>@portka-tools). Persists in ~/.claude.
• A specific repo / web session: commit .claude/settings.json (below). Web containers start fresh each session, so this committed file is what loads the plugin. Let repo-bootstrap write it, or add it by hand.

{
  "extraKnownMarketplaces": {
    "portka-tools": { "source": { "source": "github", "repo": "cportka/claude-plugins" } }
  },
  "enabledPlugins": { "video-bug-analyzer@portka-tools": true }
}

Generate that with repo-bootstrap:

plugins/repo-bootstrap/skills/repo-bootstrap/scripts/bootstrap-repo.sh --plugin video-bug-analyzer --ci

Onboarding another repo or session? Drop in docs/INTEGRATE.md — a portable guide with enable steps, verification, and ffmpeg troubleshooting.

Onboard a new repo onto the Portka standard

Cold-starting a fresh repo? Run repo-bootstrap --portka-standard — it's the one entry point that scaffolds the whole standard in a single command: the marketplace + enabled plugins, a workflow CLAUDE.md (branch-per-change → PR → merge-on-green, with tool feedback funneled to issues), a permissions allow/deny rules, and an enforced SemVer version-sync suite + CI.

plugins/repo-bootstrap/skills/repo-bootstrap/scripts/bootstrap-repo.sh \
  --portka-standard --scope project --plugin video-bug-analyzer   # add --dry-run to preview

Add --print-only for a classifier-safe manual paste when a hosted session blocks the settings write. See the repo-bootstrap usage below for every flag.

Usage

video-bug-analyzer — give Claude a screen recording and roughly when the bug happens; it runs the video-bug-analysis skill (invoke explicitly with Skill(skill="video-bug-analyzer:video-bug-analysis")). Or extract frames directly:

S=plugins/video-bug-analyzer/skills/video-bug-analysis/scripts/extract-frames.sh
"$S" --video bug.mov --fps 2 --contact            # 1) cheap overview contact sheet
"$S" --video bug.mov --timestamps 0:12,0:34 --fps 8  # 2) zoom + before/after strip per moment

Needs ffmpeg and ffprobe (the distro package ships both; an npm/static ffmpeg-only install does not, and the --probe/--list-scenes/--pacing/--stutter modes need ffprobe). The plugin never installs it for you — it reports what's missing and stops. Install it yourself (sudo apt-get install -y ffmpeg / brew install ffmpeg), or opt in explicitly per run with VBA_ALLOW_INSTALL=1 (add VBA_ALLOW_DOWNLOAD=1 to allow a checksum-verified static build when there's no package manager). See docs/INTEGRATE.md and SECURITY.md. If none of that is possible, give Claude a still screenshot of the bad moment instead — that always works.

Beyond the two core modes, extract-frames.sh has ~20 focused analysis modes (stutter/hang/ whiteout/content-flicker detectors, motion/flow/palette timelines, OCR, measurement, A/B compare, and more) — the full list with one-liners is in --help; interpretation guides and misread traps are in the skill's reference.md.

Not installed (web/headless/CI)? Plugins load at session start, so if the skill isn't in the registry yet, the script is fully standalone — the repo is public, so an agent can fetch and run just extract-frames.sh (it reports its own version and what it needs):

curl -fsSL https://raw.githubusercontent.com/cportka/claude-plugins/main/plugins/video-bug-analyzer/skills/video-bug-analysis/scripts/extract-frames.sh -o /tmp/extract-frames.sh
bash /tmp/extract-frames.sh --video bug.mov --intro     # or add --dry-run to just print the commands

app-website-evaluator — ask Claude to audit a site/app; it runs the app-evaluation skill (classify → gather evidence → prioritized report). Or run the checker directly:

E=plugins/app-website-evaluator/skills/app-evaluation/scripts/evaluate-site.sh
"$E" --url https://example.com     # live: crawlability, SEO, social, security headers, …
"$E" --dir ./dist                  # a local build (no network)
curl -sSL https://example.com | "$E" --html -   # score pre-fetched HTML (sandbox proxy blocks --url)
"$E" --html page.html --headers resp-headers.txt  # …and score the live security headers too

Behind a sandbox egress proxy that 403s arbitrary hosts (web/remote Claude Code), --url can't reach the origin — fetch the page some other way (an MCP tool, headless browser, web_fetch) and feed it to --html; add --headers (e.g. curl -sSI output) to still score HSTS/CSP/nosniff. Point --dir at the built/deployed output, not source — robots.txt / sitemap.xml / security.txt are often generated at build time (the tool warns if --dir looks like a source tree).

tab-chord-formatter — paste or link a messy guitar tab / chord sheet and ask Claude to clean it up; it runs the tab-formatting skill (normalize → re-align chords → output standard plain text). Or run the deterministic normalizer directly:

F=plugins/tab-chord-formatter/skills/tab-formatting/scripts/format-tab.py
"$F" messy-tab.txt        # decode HTML/entities, standardize [Section]s, tidy whitespace
cat messy-tab.txt | "$F"  # or from stdin

The script does only the safe mechanical cleanup (it never touches a line's internal alignment); the skill does the judgment — re-aligning chords over the right syllables and inferring structure. Needs python3.

repo-bootstrap — see Add a plugin. Flags: --plugin (repeatable), --marketplace-name, --marketplace-repo, --ci, --dir, --force, --list, --dry-run, --print-only (print the files for a classifier-safe manual write — see Updating), --auto-update (sets autoUpdate on the marketplace — see Updating for the caveat), --portka-standard (install the Portka standard: a workflow CLAUDE.md + permissions allow/deny rules matched to the loop + an enforced SemVer version sync that binds to the repo's existing version, with a basic test suite + CI), --scope (user|project|both, default both), --home. Needs python3.

Tests

bash tests/run-tests.sh

Self-contained: validates manifests, marketplace↔plugin consistency, versions, skill frontmatter, hooks, script behavior, and the bootstrap scaffolding; ffmpeg/shellcheck steps run when available, else SKIP. Powers the validate CI.

Updating

Plugins are pinned by version, so after a new release you need to pull it in:

• Per plugin: claude plugin update <name>@portka-tools, then /reload-plugins (or start a new session). This is the reliable path — use it when a fix has shipped.
• Auto-update (per marketplace): toggle it in /plugin → Marketplaces → portka-tools → Enable auto-update, or have repo-bootstrap write it with --auto-update. Caveat: as of mid-2026, auto-update on a third-party marketplace is reported to refresh the catalog but not re-install plugin code (anthropics/claude-code#61854) — so claude plugin update is still the dependable move.
• For a whole repo/team: commit a project-scope .claude/settings.json (let repo-bootstrap write it, optionally --auto-update) so collaborators pick up the marketplace.
• Kill switches: DISABLE_AUTOUPDATER (disable all auto-update); FORCE_AUTOUPDATE_PLUGINS=1 (update plugins while freezing the CLI). Re-verify settings against the docs before relying on them.

Feedback

Hit a problem? Open a Plugin feedback issue (Issues → New issue → Plugin feedback) with the plugin version, environment, ffmpeg -version, command, and error. It's triaged into a fix and a new version.

Versioning

SemVer — every PR bumps the version and adds a CHANGELOG entry. Known gaps and ideas: IMPROVEMENTS.md. Cutting a release: RELEASING.md. Getting it discovered by the community (directories, awesome-lists, announcements) — a verified playbook + a scripts/publish.sh helper: docs/DISTRIBUTION.md.

License

MIT — free to use, with attribution to Chris Portka preserved.