Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 74221–74250 of 76185 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| speakingfamstack-dev/famstackHow I say something aloud in the house. | Stars: 104 | Updated | Claude CodeCodex | Unverified | Install |
| zz-cache-padfamstack-dev/famstackKV-cache block alignment padding. No instructions. | Stars: 104 | Updated | Claude CodeCodex | Unverified | Install |
| cve-remediationNVIDIA-AI-Blueprints/Retail-Agentic-CommerceDiscoverability shim for the Retail-Agentic-Commerce CVE remediation Codex skill. Use for CVE, BDSA, GHSA, OSV, Dependabot, Black Duck, Snyk, npm, PyPI, or package advisory remediation. | Stars: 86 | Updated | Claude CodeCodex | Unverified | Install |
| featuresNVIDIA-AI-Blueprints/Retail-Agentic-CommerceDiscoverability shim for the Retail-Agentic-Commerce backend feature Codex skill. Use when writing or modifying Python backend code, routes, services, models, tests, or protocol logic. | Stars: 86 | Updated | Claude CodeCodex | Unverified | Install |
| pre-commit-analysisNVIDIA-AI-Blueprints/Retail-Agentic-CommerceDiscoverability shim for the Retail-Agentic-Commerce pre-commit analysis Codex skill. Use before commits, after significant changes, or for implementation-quality validation. | Stars: 86 | Updated | Claude CodeCodex | Unverified | Install |
| setupNVIDIA-AI-Blueprints/Retail-Agentic-CommerceDiscoverability shim for the Retail-Agentic-Commerce setup Codex skill. Use when the user asks to setup, install, start, launch, or run the project stack. | Stars: 86 | Updated | Claude CodeCodex | Unverified | Install |
| uiNVIDIA-AI-Blueprints/Retail-Agentic-CommerceDiscoverability shim for the Retail-Agentic-Commerce UI Codex skill. Use when creating or modifying frontend pages, components, hooks, styling, tests, or browser behavior. | Stars: 86 | Updated | Claude CodeCodex | Unverified | Install |
| cve-remediationNVIDIA-AI-Blueprints/Retail-Agentic-CommerceDependency vulnerability remediation workflow for this repository. Use when fixing CVE, BDSA, GHSA, OSV, npm, PyPI, Dependabot, Black Duck, Snyk, or other package vulnerability findings, especially when the user asks for minimal package-only updates, validation, commits, branches, or pull requests. | Stars: 86 | Updated | Claude CodeCodex | Unverified | Install |
| featuresNVIDIA-AI-Blueprints/Retail-Agentic-CommercePython backend development standards for FastAPI, SQLModel, pytest, Ruff, and Pyright. Use when writing or modifying backend code in src/merchant, src/payment, src/apps_sdk, agents, tests, API routes, services, models, or protocol logic. | Stars: 86 | Updated | Claude CodeCodex | Unverified | Install |
| pre-commit-analysisNVIDIA-AI-Blueprints/Retail-Agentic-CommercePre-commit implementation analysis for Retail-Agentic-Commerce. Use before commits, after significant changes, or when validating Apps SDK tools, mock data, MCP communication, widget isolation, or implementation quality. | Stars: 86 | Updated | Claude CodeCodex | Unverified | Install |
| setupNVIDIA-AI-Blueprints/Retail-Agentic-CommerceLaunch all services for the Retail-Agentic-Commerce project. Use when the user types setup, install, or asks to start, launch, or run the project stack. | Stars: 86 | Updated | Claude CodeCodex | Unverified | Install |
| uiNVIDIA-AI-Blueprints/Retail-Agentic-CommerceReact and Next.js frontend development standards for Retail-Agentic-Commerce. Use when creating or modifying UI pages, components, hooks, styling, tests, or Apps SDK widget browser behavior in src/ui or related frontend surfaces. | Stars: 86 | Updated | Claude CodeCodex | Unverified | Install |
| qaHumblemonk/shurectlDrive shurectl headlessly with `--qa` (JSON lines over stdin/stdout) to QA a change across all six models, or to turn a bug into a regression scenario in tests/scenarios/. Use for a cross-device consistency pass, to reproduce a UI or packet-order bug without hardware, or when asked to "QA", "walk every tab", or "write an e2e scenario". | Stars: 55 | Updated | Claude CodeCodex | Unverified | Install |
| catchupjellyrock/jellyrockSession-start briefing: where did I leave off, what is in flight, what needs attention. One tested script reads git, the journal (followups, running work, cadences) and tracked projects and prints every fixed-threshold check that fires; JellyRock's own aggregator adds open PRs, high-engagement bugs, recent bug reports, current-branch CI, pending handoffs, open upstream-watch issues (Jellyfin releases and release candidates, Roku OS), recent ADRs, tech debt and architecture-doc staleness. Ends with one Suggested next move that hands off to /log, /done, /issue-triage, /runtime-triage, /ci-triage or /server-upgrade. Mandated by AGENTS.md's catchup-discipline rule: run at the start of any genuine new session, after a multi-day gap, or whenever you ask what the state of the world is. | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| ci-triagejellyrock/jellyrockDiagnose a failed CI workflow run and fix it the /snag way. A tested read-only script fetches the run, reports every failed job and step with the log region around its errors (not the post-job cleanup), and classifies each against this repo's gates.tsv, printing the banner a gate carries when its obvious fix is the wrong one. Then: re-run only what is transient, reproduce locally, find the root cause, and show one decision screen; the chosen fix is built test-first and committed on a fix branch, never pushed. Use when a CI run failed on a pull request or on the default branch. | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| crash-backtracejellyrock/jellyrockDEPRECATED, replaced by the `enrich` phase built into /crash-report. The old flow filed crash issues first and enriched them one by one afterward. The new flow (stage, then enrich, then file) pulls the dashboard backtrace before filing, so issues are born complete and architectural-class crashes go to their epic instead of becoming standalone issues. Do not invoke it for new work: run /crash-report and paste the backtraces during its enrich step. It stays only as a redirect; the `enrich-issue` script subcommand still exists as a legacy escape hatch for a crash issue filed before the change. | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| crash-reportjellyrock/jellyrockProcess a Roku weekly crash-report CSV (or a zip holding one or more CSVs) into tracked GitHub issues and architectural-epic evidence, enriching before filing (stage, then enrich, then file). STAGE parses and filters the CSV, groups by pkg-path signature, builds each cited app version in a temporary git worktree, maps the transpiled `.brs` line back to the source `.bs` line, runs the GitHub dedup search, and writes a local worksheet where every crash starts pending; a mechanism hint (task-launch, network, other) orders which to pull first but never authorizes a file. ENRICH folds in the per-crash backtraces you paste from Roku's dashboard (a 7-day window, one click per crash, no bulk export), extracts each `&hNN` exception code, and routes every crash to a disposition (nothing files or aggregates without a backtrace): `file` (a scoped bug becomes a new per-signature [crash] issue, born enriched), `aggregate` (a known architectural class: `&h29` big-library too-many-task-threads, `&h23` render-thread execution timeouts, the `&hec` init `m.global.constants` race; upserted as one flat record comment per `file·function·line·version` onto the class epic, never a standalone issue), or `watch` (accepted noise, a spike comment only). FILE performs the GitHub writes (create, comment or reopen for scoped bugs; the epic record upsert for architectural classes) and writes a run-summary handoff. Dedup-aware and idempotent. Use when a fresh Roku crash CSV arrives (weekly). A deep dive on one crash goes to `/issue-triage <N>` after filing. | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| create-issuejellyrock/jellyrockDraft a GitHub issue body for the JellyRock repo from a Reddit/Discord post or free-form bug report and submit it via forge.sh. Reads the YAML form templates under .github/ISSUE_TEMPLATE/ to know which fields are required, fills them by extracting from the input, asks for any missing required fields, validates the body matches the chosen template's schema, then runs forge.sh issue create with the auto-labels the template defines. Use when you have a user report (paste from anywhere) and want to formalize it into a properly-structured GitHub issue. | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| dep-majorjellyrock/jellyrock | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| docs-lintjellyrock/jellyrockRun JellyRock's docs governance checks (broken markdown links, link anchors that match no heading, broken related-files frontmatter paths, stale tech-debt anchor references, journal-schema gates for progress.md and the decisions.md supersede chain, stale-doc detection) and surface a structured fix list grouped by category. Consumes the --json output of scripts/lint/docs-check.cjs and the human-readable output of scripts/lint/docs-stale.cjs. Use when a commit hits the docs-lint pre-push hook, before pushing a PR that touched docs/ or any CLAUDE.md, or when you want a one-shot pass over doc references. | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| donejellyrock/jellyrockMark journal work complete: close an existing followup by its fid, or ship the in-flight `running` cursor. Companion to /log, which captures new entries; /done closes existing ones. Finds the entry, proves the work actually landed, then closes it: a followup through the journal script (the entry is removed; git is the history; on main it also gains a Recently shipped line), the cursor by a direct edit. Nothing is committed on its own: the closure rides in the commit of the change that prompted it. No confirm gate on a proven closure. Pure local-file edits, apart from read-only checks that the work landed. Use when the work an entry describes is committed on this branch (pushed or merged is not required, since the closure rides in the same change set) and its journal entry needs closing. Not for capturing new entries (use /log), and not for work that is still uncommitted, undeployed or partial (don't pre-mark optimistically). | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| end-sessionjellyrock/jellyrockThis skill should be used when the user explicitly types "/end-session": the mandatory final step of any session started or resumed with /start-project or /resume-project, which the agent prints alone in its own block as the session's last line for the user to type, never invoking it directly. It updates the active project's PLAN.md (Status, kickoff, log), checks the PLAN against itself, and commits+pushes. Do not auto-invoke on vague phrases mid-session. | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| focusjellyrock/jellyrockSession-start orchestrator for JellyRock. Reads the same `scripts/catchup-state.js` state `/catchup` uses, ranks what is actionable by a fixed order, recommends the single best next move (the rule that picked it, the state behind it, 1-3 alternatives), and hands it off by printing the one command to type: `/resume-project <slug>` for a tracked project, `/start-project` for project-shaped new work, a skill that covers the pick (`/ci-triage`, `/issue-triage`, `/runtime-triage`, `/server-upgrade` for investigations; `/new-setting`, `/new-migration`, `/new-api-version`, `/translation-add` for recurring "add an X" work; `/done` or `/log` for a journal fix), or, for an ad-hoc one-off, a researched, fork-free plan (forks asked in chat, saved to `.claude/plans/`) run by a Sonnet sub-agent that `/focus` supervises and reviews. Recommend-then-confirm, one command per route. Use at the start of a session when you want the next move picked rather than a state dump; `--area=<name>` scopes it to a subsystem. Distinct from `/catchup` (state briefing, never picks) and `/ramp` (area deep-dive briefing). | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| issue-triagejellyrock/jellyrockInvestigate one GitHub issue and act on it the /snag way. Fetches the issue and its comments, first checks it is still true (everything it names still exists), reads it through the repo's issue forms, classifies it (bug, feature, enhancement, or a design decision), checks whether it is real, reproducible and not already fixed, maps it to an area, reproduces it and finds the root cause, then shows one decision screen; the chosen fix is built test-first and committed on a fix branch, never pushed. Anything posted on the issue is drafted and shown first. Use when you have an issue number you want to act on. | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| logjellyrock/jellyrockSingle-entry-point capture for the journals this repo keeps: `decision` (agent-gated: ADR-grade becomes a numbered record in `docs/adr/`, sub-architectural a note in `docs/decisions.md`, trivia is declined; `--revise=<slug>` corrects a note that misdescribes what shipped, which is not a supersede), `followup` (an open entry in `docs/progress.md`, written by the journal script with a permanent fid; `--area=<name>` picks its category; an upstream to watch is a followup too, since CI opens an issue for Jellyfin and Roku OS releases) or `running` (the `## Currently running` paragraph in `docs/progress.md`). Routes by the first argument. Mechanical types apply directly with no confirmation prompt; `decision` is agent-classified: the agent drafts, applies a significance gate (architectural / hard-to-reverse / cross-component?), routes it, and shows a diff-and-confirm before writing, with one-tap human override. The only sanctioned write path for these journals. Pure local-file edits; it commits nothing, the change that prompted the entry carries it. Use when you have something to write down. NOT for status flips on existing entries (use /done) and not for half-formed thoughts (refine first, /log once the shape is clear). | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| new-api-versionjellyrock/jellyrockGuided workflow for standing up a new Jellyfin apiVersion tier (V3, V4, …) in JellyRock when an upstream release restructures the API enough to need a new `if m.getApiVersion() >= N` dispatch level. Wraps the "Add an API tier" recipe in docs/dev/jellyfin-server-versioning.md and walks every surface that must move together (the boundary map in YAML, its BrightScript twin `resolveApiVersion()`, the `sdkVN.bs` endpoints, the dispatch branches, the device profile, the manifest tier clamp, and the validators), stopping at each step so the tier split cannot land half-built. Use when proactive RC/master triage (via `/server-upgrade <rc-or-unstable>`) shows a breaking API shift that a per-method `>= N` branch must cover. Not for routine endpoint additions inside an existing tier (those use the existing `>= 2` shape directly). | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| new-migrationjellyrock/jellyrockGuided workflow for writing a registry migration in JellyRock when a setting key is renamed, removed, or its data shape changes. Walks docs/dev/registry-migrations.md (add a version constant, add a guarded block to the runner for the right scope in source/migrations.bs, update the code that used the old name, write a real-registry integration test, run it on hardware). Use when an existing setting changes shape; brand-new settings don't need migrations and should use /new-setting instead. | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| new-settingjellyrock/jellyrockGuided workflow for adding a new user setting or global setting to JellyRock. Walks the recipe in docs/dev/new-user-setting.md (pick the kind, add the settings/settings.json entry, add its strings, add the JellyfinUserSettings field, read it in code, test it). Stops at each step to verify and gives the user the relevant file paths. Use when adding a toggle, a choice, a number or a text setting that the user can change in the JellyRock Settings screen. | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| prjellyrock/jellyrockCreate or update a pull request: a typed title (`fix:`, `feat:` … from `scripts/lib/pr-title.js`, which places the change in CHANGELOG.md), category labels chosen by judgment, a concise body from `.github/pull_request_template.md` that reads as the squash commit message, and one skill-owned "review notes" comment for the detail reviewers want but `git log` doesn't. Detects an existing open PR for the current branch and routes to update-mode (diff title/labels/body/comment, ask, then apply) instead of duplicating; aborts cleanly on merged/closed PRs. Scans branch + commits for related issues, falls back to `gh` issue search, surfaces architecture docs whose related-files were touched, and runs the four-pillar judgment passes (tech-debt scan, decision-shape detect, followup capture) so journal hygiene is part of shipping rather than a separate manual step. Required for all PRs in this repo; it supersedes any default PR-creation flow. | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |
| rampjellyrock/jellyrockArea-scoped deep-dive briefing for context-switching into a JellyRock subsystem. Loads the scoped CLAUDE.md, the matching architecture topic doc, area-relevant tech-debt slugs, recent commits scoped to the area, and skills/agents that mention the area. Use when switching into `components`, `components/video`, `components/data`, `source`, `source/api`, `source/utils`, `tests`, `locale`, or `scripts` after >2 weeks not touching it, or when a sub-agent needs scoped briefing before research. Complements /catchup (which is global). | Stars: 52 | Updated | Claude CodeCodex | Unverified | Install |