Skip to content

Explore skills

Search every indexed skill by name, description, repository or instructions, then narrow the results.

Showing 72781–72810 of 74274 skills

agilepoolYiming1997/agilePoolHigh-performance adaptive goroutine pool for Go (github.com/Yiming1997/agilePool/v2, Go 1.23.4) — Little's Law auto-scaling from sliding-window medians, sharded handoff queues plus a chunked overflow buffer, five idle-container backends (LinkedList/MinHeap/Slice/RingQueue/Treap), optional spinlock, retry with exponential backoff, context- and deadline-aware submission, panic handler and lifecycle hooks. Use when working in this codebase — adding features, fixing bugs, writing tests, reviewing changes, or answering questions about pool internals, configuration or API usage.Stars: 314Updated Claude CodeCodexUnverifiedInstall
admin-data-apibikeindex/bike_indexRead live production data from Bike Index through the admin OAuth token — Sidekiq and PgHero status, and the user-submitted bug reports — the same data as the cookie-gated dashboards, but agent-friendly JSON. Trigger when the user asks about production queue depth, job backlog, retries/dead jobs, running Sidekiq processes, or Postgres health (slow/blocked queries, index usage, unused/invalid indexes, connection counts, table/db sizes, vacuum/transaction-id danger) — and wants the *live* answer from production rather than logs or Honeybadger. Also trigger for anything about bug reports users have emailed in: what's been reported, searching/filtering them by status, tag or membership, or tagging one / linking it to the PR that fixes it. Also trigger when a request returns 401/expired and the AdminData token needs refreshing/re-authorizing. Not for reading log files (use production-log-inspection) or aggregated exception triage (bin/binx_hb).Stars: 309Updated Claude CodeCodexUnverifiedInstall
fixing-flaky-failuresbikeindex/bike_indexHow to fix a test that fails intermittently in Bike Index — one that passes locally but fails on CI, fails on one shard, passes on re-run, or is already tagged `:flaky`. **Read this before touching any spec that is failing intermittently, and before adding, raising, or relying on a `flaky:` tag or a `wait:` bump.** Trigger on a CI failure the user calls flaky, unreliable, intermittent, "green locally", "passes on retry", "fix CI", or a pasted `gh run`/Actions URL whose failure isn't reproducible; also whenever you catch yourself about to delete, skip, loosen, or retry an assertion to make a red build go green. **Equally: any spec that fails intermittently while you verify your own work** — deciding whether your change caused a flake, or whether to ship past one, is this skill's problem too, and it arrives with no CI run, no `:flaky` tag, and nobody but you calling it flaky.Stars: 309Updated Claude CodeCodexUnverifiedInstall
frontend-conventionsbikeindex/bike_indexBike Index's frontend conventions — Tailwind class prefixing (`tw:`), the standard `twinput`/`twlabel`/`twlink` form/link classes, the `number_display` helper for numbers, `Counts` for site-wide figures (bikes registered, recoveries, organizations), the UI component library rule (every button is `UI::Button`/`UI::ButtonLink`, every typeahead/autocomplete is `UI::Forms::Combobox`, every FAQ is `UI::Accordion`, never hand-rolled markup; existing components before new ones — never a wrapper around one to dodge asking for a new `UI::*` argument, which needs the user's permission), that **helpers are deprecated — render a view component taking full keyword arguments instead of adding or extending one**, ViewComponent rules (when to write a partial instead, keyword arguments, instance variables, `helpers.` prefix in templates), and `UI::Time::Component` for every date/time, and that a new marketing page's URL is spelled with dashes. Trigger when adding or modifying views (`.html.erb`), view components, Stimulus controllers, Tailwind classes, image or icon files under `app/assets/images` (which usually already exist), a page's route or a link's path, or any frontend code that touches styling or interactivity. Stimulus.js is the JavaScript framework; SCSS and CoffeeScript files exist but are deprecated.Stars: 309Updated Claude CodeCodexUnverifiedInstall
frontend-screenshotsbikeindex/bike_indexCapture desktop+mobile screenshots of Bike Index pages from the local `bin/dev` server via Playwright MCP, with a seeded-user identity gate that keeps PII out of uploaded images. Use whenever a task needs screenshots of local pages — PR documentation, bug repros, before/after comparisons across branches, design review, demos — including mid-interaction states like an open dropdown, a modal showing, a form mid-fill, or a hover. Use it even when the user just says "grab a screenshot" or "show me what this looks like" without naming Playwright. For a component that only renders under an env var / feature flag / hard-to-reach state (e.g. the review-app banner), screenshot its ViewComponent/Lookbook preview URL instead of a full page. **Also read the filename rule here before any `mcp__playwright__browser_take_screenshot` call**, including a one-off capture of some other site — it's what keeps PNGs out of the working tree.Stars: 309Updated Claude CodeCodexUnverifiedInstall
github-pr-imagesbikeindex/bike_indexEmbed a local image file into an existing GitHub PR — either in the PR body or as a comment. Trigger when a request pairs a local image (screenshot, .png/.jpg, CleanShot capture, before/after) with an existing PR (by #number, URL, branch name, or "the open PR"), regardless of verb — attach, embed, add, put, post, drop, show, document. Also covers visually documenting test runs, bug repros, UI states, or CI failures on an existing PR. Uploads through `gh`'s `--attach` flag — except in the Claude Code web sandbox, where `gh` doesn't work and images are hosted through the PR branch's history instead. It also owns the PR's one `## Screenshots` comment — finding, creating, editing and verifying it — so other workflows (the `pr` skill's screenshot phase) hand it a composed body that references local image paths, and it posts it.Stars: 309Updated Claude CodeCodexUnverifiedInstall
honeybadger-debuggingbikeindex/bike_indexInvestigate and fix a specific Honeybadger exception in the Bike Index app — pull the fault, read its backtrace, find the offending code, write the fix. Trigger whenever a request names one Honeybadger error: a pasted fault URL (`app.honeybadger.io/projects/…/faults/…`), a fault ID, an error class plus "in production" (`Vips::Error`, `NoMethodError in AfterStolenRecordSaveJob`), or phrasings like "fix this Honeybadger error", "why is this erroring in prod", "what's causing this exception", "look at this HB fault". Use `bin/binx_hb` for fault and notice detail; it is the only Honeybadger reader this repo uses. Not for a broad production health sweep across many sources, and not for reading raw log files (that's production-log-inspection).Stars: 309Updated Claude CodeCodexUnverifiedInstall
integration-testingbikeindex/bike_indexBike Index conventions for browser specs (`type: :system, :js`) — **drive every step through the real UI** (no FactoryBot or `execute_script` shortcuts to skip what a user would do), every example pays a browser boot cost so bias toward fewer, denser examples that walk through state via clicks, prefer named-element matchers over CSS selectors, and combine same-setup work into one `it` even when scenarios feel independent. **Consult this skill any time you create or modify a `:js, type: :system` spec** — that includes everything under `spec/integration/` AND component system specs at `spec/components/**/*_system_spec.rb`. Read alongside the `rspec-testing` skill for the project's general `context`/`let` style.Stars: 309Updated Claude CodeCodexUnverifiedInstall
merge-conflictsbikeindex/bike_indexHow to bring a branch up to date and resolve git merge conflicts the way this repo expects — merge (never rebase or force-push), understand each side's intent before choosing, ask when a resolution isn't clear-cut, keep the merge commit to just the merge, and audit what merged *cleanly* before committing. Trigger whenever you're about to run `git merge`/`git pull`, sync a branch with `main`, "update from main", or resolve conflict markers left by a merge, cherry-pick, or interrupted pull — including bare phrasings like "fix the conflicts", "merge main in", or "this branch is behind". Not for merging data/files (PDFs, CSVs) or algorithms (merge sort) — this is strictly about git branch integration.Stars: 309Updated Claude CodeCodexUnverifiedInstall
prbikeindex/bike_indexCreate or update a pull request for the current branch. Trigger when the user asks to create/open/make a PR, or to edit/update/rewrite/fix the PR description, body, summary, or title — including bare phrasings like "update pr" or "update the PR" with no other object — for both new PRs and existing ones. Also trigger when the ask is to re-host, recreate, or duplicate an existing PR under this repo (e.g. "close this PR and open a new one of the same changes, not a fork") — that's still creating a PR even with no new diff to write. Note this runs `/simplify`, `bin/lint`, an AGENTS.md conformance pass and a merge from the base before writing the body — skipped when the ask is only to reword the description — and pushes the result. For frontend diffs, delegates the screenshot phase to `references/screenshots.md`, which captures desktop+mobile shots and posts them as a `## Screenshots` PR comment.Stars: 309Updated Claude CodeCodexUnverifiedInstall
production-log-inspectionbikeindex/bike_indexInspect the Bike Index production Rails logs downloaded by `binx_logs` and streamed with `binx_cat web` / `binx_cat worker` — JSON-per-request (Lograge) on web plus free-form background-job lines on worker, far too large to read end-to-end. Trigger when the user asks to review, investigate, audit, or pull stats from a production log file (slow requests, error spikes, status-code distribution, exception stack traces, per-endpoint hit counts, suspicious traffic, failing background jobs). Also triggers when chasing a specific incident from logs (e.g. "what happened at 04:42 UTC?", "why did `/search/registrations` 500?"). For one named exception use honeybadger-debugging, and for *aggregated* exception triage across time `bin/binx_hb`; this skill is for ad-hoc analysis of log files already on disk.Stars: 309Updated Claude CodeCodexUnverifiedInstall
rspec-testingbikeindex/bike_indexBike Index's RSpec testing conventions — how to structure specs with `context` and `let`, what kinds of tests to write, and what to avoid (mocks, controller specs, testing private methods). Trigger when writing or modifying any `*_spec.rb` file, adding test coverage for new code, refactoring tests, or designing the test layout for a new feature. Includes Good/Bad examples of the project's preferred style.Stars: 309Updated Claude CodeCodexUnverifiedInstall
sandbox-test-setupbikeindex/bike_indexBike Index Ruby + RSpec environment setup for each place this repo runs: a local macOS Conductor workspace, a spawned `.claude/worktrees/…` git worktree, and Claude Code's Linux web sandbox — getting `ruby`, `bundle`, `bin/lint`, a database, seeds, a dev server and a browser working there. **Read it before the first command in a spawned worktree**, which starts with `bin/workspace_setup` (without it `bin/env` hands back the main checkout's port, database and Redis). Read it whenever a session runs RSpec, `bundle` or `bin/lint`, needs a dev server or seeded data, or hits: a missing `.workspace_id` or `node_modules`, a `$BASE_URL` serving another branch, `Could not find 'bundler' (4.0.x)`, `command not found: rspec`, `uninitialized constant Pathname` or `undefined method 'intersect?' for Array` from a `bin/` script, `Sprockets::Rails::Helper::AssetNotFound`, `tailwind.css is not present`, `LoadError: Could not open library 'vips.so.42'`, `executable not found: "identify"`, or a Playwright browser-not-found, build-number mismatch, `Playwright::Error: timeout: expected float, got undefined` or `Running as root without --no-sandbox is not supported`. The fix is almost never a reinstall or a Gemfile edit — it's a PATH, an env var, or a service that isn't running.Stars: 309Updated Claude CodeCodexUnverifiedInstall
use-existing-markupbikeindex/bike_indexConvert a branch's hand-written markup to the components that already render it. Covers marketing and landing pages on `SharedBlocks::Marketing` and the donate form, `UI::*` and `Atoms::*` everywhere else, icons and images the repo already has, buttons snapped to existing colors, shadows, and hover states to report. Trigger when a branch adds or redesigns a page's markup, especially a marketing, landing, donate or "how it works" page or a design handoff built from a mockup. Also trigger on "use existing components", "reuse the markup", "is this hand-rolled", and from the `pr` skill's markup audit. It replaces without asking.Stars: 309Updated Claude CodeCodexUnverifiedInstall
numina-lean-agentproject-numina/numina-lean-agentLean 4 theorem proving toolkit: search lemmas, verify proofs, repair/simplify code, and get LLM-assisted informal proofsStars: 293Updated Claude CodeCodexUnverifiedInstall
code-transformproject-numina/numina-lean-agentCode transformation tools for repairing, simplifying, and extracting Lean proofsStars: 293Updated Claude CodeCodexUnverifiedInstall
llmproject-numina/numina-lean-agentLLM-assisted tools for informal proofs, proof strategy discussion, and code simplificationStars: 293Updated Claude CodeCodexUnverifiedInstall
searchproject-numina/numina-lean-agentSearch tools for finding Lean theorems, lemmas, and definitions in MathlibStars: 293Updated Claude CodeCodexUnverifiedInstall
sorrifierproject-numina/numina-lean-agentIsolates failing proof steps by replacing them with `sorry` and extracting them into standalone lemmas to modularize and decouple complex Lean 4 proofs.Stars: 293Updated Claude CodeCodexUnverifiedInstall
verificationproject-numina/numina-lean-agentVerification tools for compiling, validating, and disproving Lean theoremsStars: 293Updated Claude CodeCodexUnverifiedInstall
fbaethersdr/AetherSDRFix an AetherSDR bug end-to-end and prove the fix with the agent automation bridge. Use when the user says $fb or /fb ISSUE_NUMBER (e.g. /fb 2211), or asks to "fix bug 2211", "take the next bug", "reproduce and fix issue 3340", or otherwise wants a GitHub issue investigated, root-caused, fixed in a worktree, built, proven via the bridge, and turned into a PR. This is the dogfooding loop for the agent automation bridge — reach for it whenever a UX, meter, transmit, audio, or control bug is reported with an issue number.Stars: 264Updated Claude CodeCodexUnverifiedInstall
mergewatchaethersdr/AetherSDRReport release-cycle GitHub merge counts and compare CI build and test times with five merges from the previous release. Use for /mergewatch, $mergewatch, release-cycle merge reports, or CI timing baseline comparisons. Read-only.Stars: 264Updated Claude CodeCodexUnverifiedInstall
papercutsaethersdr/AetherSDRRead-only AetherSDR issue triage that surfaces the UX papercuts, bugs, and regressions you can fix AND prove today with the agent automation bridge. Use when the user says $papercuts or /papercuts, or asks to "find papercuts", "what can I fix and prove today", "triage bridge-provable issues", "what UX bugs can the bridge close", "sort issues by priority I can knock out", or otherwise wants a curated, lifecycle-aware (design→code→prove) shortlist of issues — NOT the label-and-respond /triage workflow. This is the discovery step that feeds /fb. Strictly read-only: it never labels, comments, closes, or edits issues.Stars: 264Updated Claude CodeCodexUnverifiedInstall
pr-landaethersdr/AetherSDRPost-review remediation pass for AetherSDR — takes a PR whose proposed change the maintainer has already accepted, fixes every outstanding finding with proof, answers and resolves every review thread, dismisses blocking reviews with evidence, posts the approving review and arms auto-merge. Every judgment call goes to the maintainer through AskUserQuestion. Use after /pr-review, e.g. "/pr-land 5601".Stars: 264Updated Claude CodeCodexUnverifiedInstall
pr-reviewaethersdr/AetherSDRFull adversarial PR review for AetherSDR — red-teams the PR against its linked issue, tests every claim in the body, audits scope creep and undisclosed changes, checks governance and code quality, posts one GitHub review with every finding in its body, and reports blockers/nits/recommendation as markdown. Use when asked to review a PR (e.g. "/pr-review 4609").Stars: 264Updated Claude CodeCodexUnverifiedInstall
release-prepaethersdr/AetherSDRThe AetherSDR release-prep pass — takes a CalVer version and drives the release from "main is where we want to cut" to "the prep PR is merged on main and ready to tag". Maps the range through the commit-to-PR API, writes the CHANGELOG section from PR bodies, refreshes README and ROADMAP, edits the six release files, validates, opens the prep PR, folds in what merges after the cutoff, and hands the merged squash commit to /tag-release for the tag, the release and the asset verification. Every judgment call goes to the maintainer through AskUserQuestion. Use when the user says "/release-prep 26.9.4", "/release-prep v26.9.4", "prep the release", "release prep", "write the changelog for 26.9.4", or otherwise wants a version prepped; the cut itself is "/tag-release".Stars: 264Updated Claude CodeCodexUnverifiedInstall
tag-releaseaethersdr/AetherSDRThe AetherSDR cut pass — takes a CalVer version whose prep PR has merged on main and drives it from "the prep is on main" to "the release is published, every asset is signed and verified, the Store submission is committed, the website post is up and the report is written". Finds the squash-merge commit, checks the six release files at that SHA, tags it with a signed annotated tag, creates the release before CI attaches anything, watches the three build workflows, the signing runs and Release Offload, verifies the assets on the files (the fourteen-file page and what Release Offload moved to updates.aethersdr.com), reads the Store publish step, drafts the website post, and reports the first 48 hours. Every judgment call goes to the maintainer through AskUserQuestion. Use when the user says "/tag-release 26.9.5", "/tag-release v26.9.5", "tag the release", "cut the tag", "publish v26.9.5", "the prep merged, tag it", or otherwise wants a prepped version tagged and published. /release-prep ends where this begins.Stars: 264Updated Claude CodeCodexUnverifiedInstall
skillsAriestar/sivtrVerify sivtr environment and diagnose issues. Run when sivtr commands fail or return empty results.Stars: 259Updated Claude CodeCodexUnverifiedInstall
sivtr-memoryAriestar/sivtrRetrieve shared local work memory: terminal activity, AI conversation history, prior decisions, validation evidence, debugging trails, recaps, and handoff context. Use before asking the user to repeat local work context.Stars: 259Updated Claude CodeCodexUnverifiedInstall
adaptzacharyfmarion/openscad-studioAdapt designs to work across different screen sizes, devices, contexts, or platforms. Ensures consistent experience across varied environments.Stars: 253Updated Claude CodeCodexUnverifiedInstall