Set up and use Google Cloud Error Reporting in Node.js applications. Explains when to rely on automatic error capture (Cloud Run / Cloud Run functions) vs the @google-cloud/error-reporting client library, and how to format Cloud Logging entries so Error Reporting ingests them. Use when the user asks about Error…
Provides OpenTelemetry explicit instrumentation methodology and Google Cloud LogEntry formatting rules for Node.js workloads. Use when instrumenting Cloud Run services or Firebase Functions gen2, correlating traces with logs, configuring structured logging, or integrating with Cloud Error Reporting.
Verify whether a GitHub issue is implemented in the current codebase by collecting evidence from the GitHub issue, git history, docs, code, and tests, then producing a structured report with verdict, proof, gaps, confidence, and scope-clarity doubts. Use when the user asks whether an issue was resolved or whether a…
Create and update GitHub pull requests using gh CLI for repositories that use a .github/pullrequesttemplate.md with comment markers. PRs are written in Brazilian Portuguese and staged in .work/ body files. Use when the user asks to create a PR, open a PR, update a PR description, or prepare a PR body.
Rewrite a PR body around what a reviewer actually needs. Use for "distill this PR", "tighten the description", "this body is a thesis", or after a long implementation session where the PR body grew with the investigation.
Use when creating, reviewing, or hardening GitHub Actions CI/CD workflows where deployment topology, promotion safety, release identity, cache discipline, OIDC, environments, or production readiness matter.
Use when authoring or reviewing Go command-line applications, especially when deciding command grammar, output contracts, exit codes, config precedence, thin CLI architecture, testing strategy, automation safety, or agent-friendly behavior.
Go package documentation (doc.go) following official conventions. Use when creating package-level documentation, writing doc.go files, or ensuring compliance with go doc, godoc, and pkg.go.dev standards. Triggers on tasks involving package comments, API documentation, or Go documentation review.
Build and review server-side HTMX applications with Hono using typed HTMX attributes, architecture-first route design, and production-safe server patterns. Use when creating a new Hono + HTMX app, choosing page and fragment boundaries, or implementing HTMX-driven forms, navigation, realtime flows, and partial page…
Write, execute, and assert HTTP requests safely using Hurl text files. Triggers on API testing, HTTP request generation, REST/GraphQL validation, or when .hurl files are mentioned. Do NOT use this skill for UI/browser testing or for internal unit testing.
Type-safe SQL query building in TypeScript using Kysely. Use when writing or reviewing Kysely queries, schema types, migrations, raw SQL snippets, dynamic filters, conditional selects, transactions, or reusable query helpers.
Use when the user wants to audit, tidy, or reality-check a Linear board using MCP-first evidence, especially for project hierarchy, labels, statuses, stale work, and whether Linear reflects the current state of work.
Design and review repository-local agent guidance using root and nested AGENTS.md, .cursor/rules, skills, packs, and optional pack-bundled skills. Use when organizing monorepo AI instructions, deciding where routing knowledge should live, or authoring directory-specific AGENTS.md files for Cursor-first projects.
Scaffold and maintain Nx monorepo structure with hexagonal architecture, project tags, TypeScript project references, and npm workspaces linking. Use when creating new apps/libs/tools, fixing build or linking errors, configuring project tags, or enforcing module boundary rules.
Expert guidance for configuring and deploying the OpenTelemetry Collector. Use when setting up a Collector pipeline, configuring receivers, exporters, or processors, deploying a Collector to Kubernetes or Docker, or forwarding telemetry to Dash0. Triggers on requests involving collector, pipeline, OTLP receiver…
Configures OpenTelemetry trace spans, metrics, and log exporters. Use ONLY when instrumenting applications specifically with OpenTelemetry (OTel). Triggers on requests explicitly mentioning OpenTelemetry, OTel, or OTLP.
OpenTelemetry Transformation Language (OTTL) expert. Use when writing or debugging OTTL expressions for any OpenTelemetry Collector component that supports OTTL (processors, connectors, receivers, exporters). Triggers on tasks involving telemetry transformation, filtering, attribute manipulation, data redaction…
Route Node.js/TypeScript backend security questions to the matching OWASP Top 10 category and the correct library reference (express, mysql2). Use when securing Express endpoints, parameterizing mysql2 queries, hardening sessions/headers/CORS, or classifying a finding as A01–A10. Do NOT use for React/frontend XSS…
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
Verify working-tree changes against an 8-tier test pyramid. Runs the right tests for changed files, collects coverage from instrumentable tiers, and returns a structured verification report. Use when the agent modifies production code, the user asks to run tests or check coverage, or the gh-pr-creator skill needs…
★not rated 2 1mo agoA72 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: