AGENT SKILLS · MISSION KIT
Useful agent skills ranked by real adoption
Browse verified skills from public repositories. Compare what each skill does, package contents, install activity, and source evidence before adding it to your agent.
- CATALOG SCOPE
- VERIFIED
- skills
- 23,248
- repositories
- 3589
- last synced
- Nov 4, 2026
goldsky-ioturbo-pipelines
Turbo pipeline YAML reference and architecture guide. Covers: YAML field syntax (startat, from, version, primarykey), source/transform/sink configuration, validation errors, resource sizing (xs–xxl), architecture decisions (dataset vs kafka, streaming vs job, fan-out vs fan-in, sink selection, pipeline splitting). Triggers on: 'what does field X do', 'what fields does a postgres sink need', 'what resource size', 'should I use kafka or dataset', 'how to structure my pipeline'. For writing transfo
- 1h installs
- 4
- GitHub stars
- 12
- Updated
- Nov 2
goldsky-ioturbo-transforms
Write SQL, TypeScript, and dynamic table transforms for Turbo pipelines. Covers: decoding EVM logs with gslogdecode, filtering/casting blockchain data, UNION ALL for combining events, TypeScript/WASM transforms (invoke function), dynamic lookup tables (dynamictablecheck), transform chaining, and Solana decoding. Triggers on: 'decode Transfer events', 'write a SQL transform', 'filter by contract', 'TypeScript transform', 'dynamic table', 'UNION ALL'. For pipeline YAML structure, use /turbo-pipeli
- 1h installs
- 4
- GitHub stars
- 12
- Updated
- Nov 2
samberapi-idempotency-retry
Design idempotency-key support and client retry guidance for a public API so integrators retry safely - key derivation and per-caller scoping, storage TTL and replay windows, atomic claim mechanisms (DB unique constraint, SERIALIZABLE row lock, conditional writes), payload-mismatch rejection, in-flight duplicate handling, exponential backoff with jitter, retry budgets, timeout propagation, and SDK retry defaults. Use whenever the user mentions an Idempotency-Key header, duplicate or double-submi
- 1h installs
- 4
- GitHub stars
- 9
- Updated
- Nov 1
paymoggroundcover-cli
Invoke the groundcover Go CLI to manage Groundcover resources (dashboards, monitors, silences, connected apps, notification routes, API keys, policies, integrations, pipelines, workflows) AND to answer production observability questions by querying logs, traces, metrics, k8s inventory, and k8s events. Use whenever a task needs an authenticated call against the Groundcover API or whenever the user is debugging a prod issue and asks things like "why is X erroring in prod", "show me logs for servic
- 1h installs
- 4
- GitHub stars
- 1
- Updated
- Aug 18
paymogincidentio-cli
Invoke the incidentio CLI to drive the incident.io API — incidents, actions, follow-ups, alerts/alert sources/routes, escalations & on-call schedules, catalog (types/entries/resources), custom fields, severities, incident types/roles/statuses/timestamps, status pages (including creating and managing public pages, components, layout, subscribers, templates), workflows, users, teams, API keys, heartbeats, maintenance windows, and settings. Uses the public Bearer API (OpenAPI-generated commands) pl
- 1h installs
- 4
- GitHub stars
- 0
- Updated
- Jul 21
paymogslack-cli
Invoke the slack-cli binary to read and act on a Slack workspace from the command line — list channels, read/search conversation history and threads, fetch unread messages, search users, manage user groups, post messages, add reactions, mark channels read, and manage saved items. Use whenever a task needs Slack data or actions, such as "what are the unread messages in incidents", "search Slack for the deploy thread", "who is @alice", "post a message to general", "list channels matching X", "reac
- 1h installs
- 4
- GitHub stars
- 0
- Updated
- Oct 20
gjkim42address-pr-review
Review the comments on a PR and address the findings that are valid and required. Use when the user says "address-pr-review", asks to address the PR review, handle or apply the review comments or review feedback on a PR, or fix what the reviewers asked for. Defaults to the PR for the current branch when none is named. This skill changes code; it is not a review pass.
- 1h installs
- 4
- GitHub stars
- 0
- Updated
- Oct 31
gjkim42api-review
Review the current Kelos branch, or an explicitly specified PR, issue, or diff, for Kubernetes API and CRD design quality. Use when asked for a Kelos API review, CRD/API compatibility review, Kubernetes API convention review, or review of changes under api/, generated CRDs, examples/, or self-development/ manifests. Default to the current branch when no target is specified. This skill is review-only.
- 1h installs
- 4
- GitHub stars
- 0
- Updated
- Oct 31
gjkim42design-cleanup
Sweep the current branch for leftovers of an abandoned design after a significant mid-work decision change, and rewrite the affected code, comments, tests, and docs so the result reads as if it had been designed this way from the beginning. Use when the user says "design cleanup", "clean up the old approach", "erase the journey", says a design decision changed and asks to clean up after it, or after a pivot in approach mid-branch. This is a rewrite pass over the code touched by the decision only
- 1h installs
- 4
- GitHub stars
- 0
- Updated
- Oct 31
gjkim42finish-pr
Finish a PR by repeatedly requesting a Kelos review, waiting for its check, addressing valid review findings, squashing commits, and updating the PR until a review approves and that iteration is finalized. Use when the user says "finish-pr" or asks for this review-and-fix loop. Defaults to the PR for the current branch.
- 1h installs
- 4
- GitHub stars
- 0
- Updated
- Oct 31
gjkim42gjkim-instruction
Create and maintain gjkiminstruction.md, the root document for a loop-engineering effort. The document holds only the minimum requirements and confirmed decisions, and deliberately leaves everything else open so that later iterations are not locked into early guesses. Use whenever the user mentions gjkiminstruction.md, a root document or root doc for a loop, loop engineering, starting a long-running agent loop on a goal, or asks to record a requirement or a confirmed decision for such an effort.
- 1h installs
- 4
- GitHub stars
- 0
- Updated
- Oct 31
gjkim42review-all
Run a two-agent code review: spawn two fresh, clean-context agents that examine the SAME committed branch diff in parallel. One agent runs Codex's native codex review --base command, while the other independently reviews the code against Google's "What to look for in a code review" guidance. Merge both outputs into one agreement-ranked report. Use this whenever the user asks for "review-all", a second-opinion review, a dual review, a cross-check before a PR, or a maximum-confidence review of com
- 1h installs
- 4
- GitHub stars
- 0
- Updated
- Oct 31
langchain-aideep-agents-memory
INVOKE THIS SKILL when your Deep Agent needs memory, persistence, or filesystem access. Covers StateBackend (ephemeral), StoreBackend (persistent), FilesystemMiddleware, and CompositeBackend for routing.
- 1h installs
- 4
- GitHub stars
- 1.3K
- Updated
- Oct 29
callstackincubatorreact-native-best-practices
Provides React Native performance optimization guidelines for FPS, TTI, bundle size, memory leaks, re-renders, and animations. Applies to tasks involving Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, or debugging jank and frame drops.
- 1h installs
- 4
- GitHub stars
- 1.7K
- Updated
- Oct 8
antfupnpm
Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces via pnpm-workspace.yaml, or managing dependencies with catalogs, patches, overrides, config dependencies, or the global virtual store.
- 1h installs
- 4
- GitHub stars
- 6K
- Updated
- Oct 30
callstackagent-device
Automates Apple-platform apps (iOS, tvOS, macOS), Android devices (including Android TV and Fire TV on Fire OS), and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
- 1h installs
- 4
- GitHub stars
- 5.2K
- Updated
- Nov 2
owl-listeneraccessibility-audit
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use accessibility-test-plan (prototyping-testing).
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
owl-listenercritique-color
Critique a rendered screen's colour — contrast ratios, palette coherence, and semantic meaning. Use when reviewing one screen. For a product-wide WCAG audit use accessibility-audit (design-systems); for building the palette use color-system (ui-design).
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
owl-listenercritique-information-density
Critique a rendered screen's density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure. Use when a screen feels overwhelming. For the underlying choice-count principle, use hicks-law (interaction-design).
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
owl-listenercritique-typography
Critique a rendered screen's typography — scale usage, readability, consistency, and token compliance. Use when reviewing type on a screen. For defining the scale itself, use typography-scale (ui-design).
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
owl-listenercritique-visual-hierarchy
Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use visual-hierarchy (ui-design).
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
owl-listenererror-handling-ux
Design error prevention, detection, and recovery across a product — message content, placement, and escape routes. Use when errors span multiple flows. For validation inside a single form, use form-design.
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
owl-listenerloading-states
Design waiting experiences — spinners, skeletons, optimistic updates, and progressive reveal. Use when content takes time to arrive. For the latency budget itself use doherty-threshold; for success confirmation use feedback-patterns.
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5
owl-listenerlocalization-design
Design for multiple languages, writing directions, and cultural contexts — text expansion, RTL mirroring, and locale formats. Use when shipping beyond one locale. For the words themselves, use ux-writing (designer-toolkit).
- 1h installs
- 4
- GitHub stars
- 3.2K
- Updated
- Sep 5