Relay
PricingFor agents
Sign inStart a task →
Relay

Do the work you love.
Hand off the rest.

Start a task →

Product

  • Use cases
  • Library
  • Solutions
  • Pricing
  • For agents
  • API documentation

Library

  • Agents
  • Workflows
  • Skills
  • Tasks
  • Browse everything

Help & company

  • Help center
  • Security
  • About Relay
  • Contact

Teams

  • Marketing
  • Sales
  • Customer success
  • Operations
  • Leadership

Industries

  • Agencies & consulting
  • B2B SaaS
  • Professional services
  • Financial services
  • Healthcare
  • Retail & ecommerce
  • Manufacturing
  • Nonprofits

Goals

  • Retain customers
  • Grow revenue
  • Serve more clients
  • Report to the board
  • Cut rework

Who it’s for

  • Agencies
  • Operators
  • Founders
  • Builders
  • Independents
  • Teams at work
  • Workers
  • Everyone

Use cases

  • Monthly client performance report
  • Competitive landscape brief
  • Client content calendar
  • SEO audit
  • Proposal and SOW draft
  • Quarterly business review deck
  • Market research brief
  • Campaign plan
  • All use cases

Compare

  • Relay vs Dust
  • Relay vs Gumloop
  • Relay vs Sana Agents
  • Relay vs Relevance AI
  • Relay vs Glean
  • Relay vs Credal
  • Relay vs StackAI
  • Relay vs Lindy
  • Relay vs n8n
  • Relay vs Zapier
  • Relay vs Make
  • All comparisons

© 2026 Relay

PrivacyTermsCreator termsWorker terms
Home›Library

Ready-made AI for the work you hand off.

Browse the library

AllAgentsWorkflowsSkillsTasks

Find it here. Run it on your own work.

Browsing is free. Create a free account to run anything with your own files. Paid work uses credits, and the cost is shown first.

Create a free account →Connecting an AI agent? Read For Agents
FeaturedSearchBrowse

Product and engineering

24 shown, more on the next page

Skill · Product and engineering

Accessibility Qa

Plan and report accessibility QA for a web or app experience against WCAG 2.2 level AA. Defines scope and a page and flow sample, combines automated scans with manual keyboard, screen reader, zoom and reflow, contrast, semantics, and form-error testing, computes contrast ratios, logs each issue with the success criterion, affected users, severity, and a fix direction, and ends with retest criteria. Use when someone asks for accessibility testing, an accessibility audit plan or report, keyboard or screen reader checks, contrast checks, or WCAG review of a page or flow. Do not use for the overall test plan (use test-plan), the release verdict (use release-regression-report), visual design critique (use design-audit), or posting issue text (use jira-evidence-uploader).Free
Skill · Product and engineering

Codebase Audit

Audit an existing codebase or system and produce an evidence-backed findings register and prioritized remediation roadmap. Covers scoping the audit questions, a read-only orientation, eight dimensions (architecture, maintainability, reliability, security, performance, test coverage, operability, delivery), change-frequency by complexity hotspots, test-gap mapping to critical paths, findings with evidence and confidence, severity times likelihood times exposure scoring, and now/next/later sequencing. Use when someone asks to audit a codebase, assess technical debt, review the health of an inherited or acquired system, find reliability or security gaps, judge whether to rewrite or refactor, or prepare due diligence on a code base. Do not use for dependency version and licence health alone (use dependency-health), for planning a data or platform move (use migration-plan), for designing the target system (use technical-architecture), or for reviewing a single change (use gitnexus-review).Free
Skill · Product and engineering

GitNexus Impact Analysis

Assess the likely consequences of a proposed or local code change with GitNexus graph evidence, then verify the result against the exact repository. Use for dependency tracing, blast-radius analysis, regression planning, and deciding whether a shared symbol is safe to change.Free
Skill · Product and engineering

Iac Setup

Plan an infrastructure-as-code setup, or the adoption of one for existing manual infrastructure. Inventories resources by layer and stateful versus stateless, picks a tool by criteria, designs environments, repository, module, and remote state layout, deployer identity, handling of sensitive values, a reviewed plan-then-apply flow with policy checks and a production approval gate, drift detection, change-safety rules for replacements and deletions, and rollback classified per resource. Use when someone asks to set up or codify infrastructure, manage staging and production from code, structure modules and state, design an infrastructure deploy pipeline, or decide how to roll back infrastructure changes. Do not use for application design (use technical-architecture), auditing existing cloud resources (use audit-cloud-infrastructure), data or platform moves (use migration-plan), or monitoring design (use observability-plan).Free
Workflow · Product and engineering

Implementation Plan

Implementation Plan workflow that groups context collection, production, review, and packaging tasks into one deliverable.Free
Skill · Product and engineering

Jira Evidence Uploader

Package QA findings into Jira-ready drafts without posting anything. Normalizes each finding to one defect, decides new issue versus comment versus link, writes the summary, preconditions, numbered reproduction steps, expected and actual results, severity proposal, and environment block, selects and names screenshots, recordings, and log excerpts, runs a redaction check for personal data, builds an attachment manifest with hashes, and drafts new-issue, evidence, and retest comments. Use when someone asks to write up a bug for Jira, turn QA findings into tickets, package screenshots and reproduction steps, or draft evidence comments. Do not use for writing epics or stories (use jira-epic-writer), the release verdict (use release-regression-report), test planning (use test-plan), or running the tests (use playwright-browser-runner).Free
Skill · Product and engineering

Migration Plan

Plan a safe technical migration (schema, data store, hosting platform, service or API version, framework, or vendor) as a staged parallel-change plan. Covers an inventory of what moves and who depends on it, a compatibility matrix for old and new code against old and new data, a data preservation plan with reconciliation checks, backfill duration math, phases with entry and exit gates, a cutover and point-of-no-return decision, a rollback per phase, and a cleanup step. Use when someone asks how to migrate a database, move to a new platform or provider, change a schema without downtime, version or retire an API, plan a cutover, or write a rollback plan. Do not use for an audit of existing code health (use codebase-audit), for the target design itself (use technical-architecture), for infrastructure definitions (use iac-setup), or for live incident handling (use coordinate-production-incident).Free
Skill · Product and engineering

Mobile Web Implementation Plan

Turn product requirements into a buildable implementation plan for a web or mobile app. Converts requirements into testable acceptance criteria, decides the delivery platform (responsive web, installable web app, native, or cross-platform) from capability needs, breaks work into vertical slices with the files to create or change, the interface contract, the screen states, accessibility and analytics needs, a test plan traced to each criterion, milestones with three-point estimates, and a staged rollout with a kill switch and a support policy for old app versions. Use when someone asks how to implement a feature or app, to plan a build from a spec, to break a front-end project into milestones, to decide web versus native, or to plan a mobile release. Do not use for the system-level design (use technical-architecture), for splitting a spec into engineering tickets only (use technical-requirements-splitter), for a data or platform move (use migration-plan), or for the visual design itself (use wireframe-spec).Free
Skill · Product and engineering

Observability Plan

Plan the logs, metrics, traces, alerts, dashboards, service level objectives, and incident response hooks for a system so its operators can tell within minutes whether users are hurting and why. Starts from user journeys, defines good-event service level indicators and SLO targets with error budget and multi-window burn-rate alert math, maps instrumentation per component, sets log field and metric cardinality rules, designs tiered dashboards and symptom-based paging, adds runbook and escalation hooks, and budgets telemetry volume, retention, and privacy. Use when someone asks how to monitor a system, what to log or alert on, how to set SLOs, why alerts are noisy, how to add tracing, or how to prepare a service for on-call. Do not use for triaging a specific metric anomaly (use anomaly-triage), running a live incident (use coordinate-production-incident), auditing existing code (use codebase-audit), or defining infrastructure resources (use iac-setup).Free
Skill · Product and engineering

Playwright Browser Runner

Guide browser test execution with Playwright or a similar runner as a run plan the user carries out. Covers pre-flight checks, run modes (smoke, targeted, full, cross-browser, repeat for flake detection), command templates, evidence settings (trace, screenshot, video), a failure triage decision tree that separates product bugs from locator, data, environment, and flaky causes, repeat sizing, quarantine rules, and a stable run record for reporting. Use when someone asks how to run browser tests, capture evidence, triage Playwright failures, find flaky tests, or report a browser test run reliably. Do not use for the overall test strategy (use test-plan), the release verdict (use release-regression-report), accessibility checks (use accessibility-qa), or writing issue text (use jira-evidence-uploader).Free
Skill · Product and engineering

Release Regression Report

Produce a release regression report from the user's test results and defect list for one release candidate. Separates executed from planned work, computes execution, pass, and effective pass rates by priority and area, classifies every failure (regression, known issue, flaky, environment, test defect), maps failures and unexecuted tests to changed areas, rates residual risk, and ends with a go, conditional go, or no-go recommendation tied to stated gates and named waivers. Use when someone asks for a regression summary, release readiness report, go or no-go recommendation, or whether a build is safe to ship. Do not use for writing the test plan or its exit criteria (use test-plan), accessibility findings (use accessibility-qa), or turning findings into issue text (use jira-evidence-uploader).Free
Skill · Product and engineering

Responsive Layout Check

Check a web app's responsive layout across breakpoints and devices before launch. Use when you need Playwright screenshots of key pages at phone, tablet, laptop and wide desktop widths, a findings list of layout breaks (horizontal overflow, clipped text, overlapping elements, unreachable navigation, undersized tap targets), fixes mapped to CSS or component code, and a re-check that proves each fix.Free
Skill · Product and engineering

Security Questionnaire Response

Answer a customer's vendor security questionnaire (SIG, CAIQ, or a custom spreadsheet) from the company's own evidence. Builds and maintains an answer library keyed to control areas, maps each question to policies, SOC 2 report sections, penetration test summaries, and architecture documents, answers Yes, No, Partial, or N/A with a short factual explanation, handles compensating controls honestly, routes answers that need security or legal sign-off, and hands back a gap list for the security owner. Use when a prospect or customer sends a security questionnaire, vendor risk assessment, third-party risk review, or due-diligence form, or needs consistent SIG or CAIQ answers. Do not use for drafting a full RFP response (rfp-response-drafter), writing security policies from scratch, running a security audit or threat model, or negotiating contract terms.Free
Skill · Product and engineering

Technical Architecture

Create a technical architecture plan for a new or evolving system from its requirements. Ranks quality attributes with measurable targets, sizes load and storage with back-of-envelope capacity math, sets system boundaries and data ownership, maps the context, containers, and data flows for key scenarios, designs APIs and data storage by access pattern, covers infrastructure, security trust boundaries, and failure modes, and records each major choice as a decision with options, criteria, reversibility, and a build sequence that proves the riskiest assumptions first. Use when someone asks to design a system architecture, choose between a monolith and services, plan data flow and APIs, size infrastructure, or document architecture decisions and tradeoffs. Do not use for splitting a finished design into tickets (use technical-requirements-splitter), assessing an existing codebase (use codebase-audit), planning a move between systems (use migration-plan), or writing infrastructure definitions (use iac-setup).Free
Skill · Product and engineering

Test Plan

Create a risk-based test plan for a feature, release, or system from the user's requirements, designs, and change list. Scores each requirement by likelihood and impact, derives scenarios with named techniques (equivalence classes, boundary values, decision tables, state transitions, pairwise), places each at the cheapest effective test level, builds a requirement-to-test coverage matrix, defines environments, fixtures, owners, schedule, and numeric entry and exit criteria, and lists what is out of scope. Use when someone asks for a test plan, test strategy for a feature, coverage matrix, exit criteria, or what to test before launch. Do not use for the final release verdict (use release-regression-report), the roles and seeded data detail (use test-user-data-matrix), accessibility checks (use accessibility-qa), or proving one fix with a test (use prove-regression-tests).Free
Skill · Product and engineering

Test User Data Matrix

Define the synthetic test users, roles, permissions, seeded data, edge cases, and reset requirements a test effort needs. Builds a persona list across role, tenant, account state, and plan; a role-by-resource-by-action permission matrix with allow, deny, own-record, and conditional expectations; negative and cross-tenant cases; a seed catalogue with volume, boundary, date, money, and text edge data; and a reset and isolation plan covering parallel runs and side effects, with case counts computed. Use when someone asks which test users and roles to create, how to test permissions, what seed data and edge cases to prepare, or how to reset data between test runs. Do not use for the overall test strategy (use test-plan), running browser tests (use playwright-browser-runner), accessibility checks (use accessibility-qa), or the release verdict (use release-regression-report).Free
Skill · Product and engineering

Web Accessibility Audit

Audit a web app against WCAG 2.2 level AA before launch and hand back fixes developers can ship. Use when you need automated axe-core scans of key pages and states, a manual keyboard, focus, screen reader, zoom and reflow review, colour contrast checks, accessible forms and error messages, each failure mapped to its WCAG success criterion with a code fix, and a re-test that proves the fix.Free
Skill · Product and engineering

Coordinate Production Incident

Coordinate an active production incident or prepare an incident runbook using runtime evidence, explicit roles, bounded mitigations, stakeholder updates, verification, rollback, and a blameless follow-up. Use for outage command, degraded service, security or provider incidents, incident timelines, status updates, and post-incident action plans. Do not use to execute destructive remediation or claim recovery without authoritative readback.FreeHigh risk
Skill · Product and engineering

GitNexus Review

Review a pull request, commit range, branch, or local diff with GitNexus-assisted dependency evidence and exact-source verification. Use for regression review, merge-risk assessment, missing-test analysis, and source-supported review findings.Free
Skill · Product and engineering

Launch Readiness Check

Run a go/no-go launch readiness check for a web app before it goes live. Use when you need one evidence-backed checklist covering domain, DNS, HTTPS and redirects, email deliverability (SPF, DKIM, DMARC), analytics and conversion tracking, error tracking, uptime and health checks, backups and a tested restore, rollback and the launch-day runbook, privacy policy, terms and cookie consent, broken links, 404 and error pages, transactional email, and owners on call, ending in a signed go/no-go decision.Free
Skill · Product and engineering

Relay Quality Evidence

Review QA Manager evidence with requirement-to-test traceability, fast and full gate plans, comparable performance baselines, security evidence records, workflow maps, and UI edge-case gaps.Free
Skill · Product and engineering

Visual Evidence Analyzer

Classify screenshots, locate visible QA errors, annotate evidence, select walkthrough or marketing frames, inspect UI defects, tag design references, locate document regions, or find browser fallback targets using Relay's real metered Jev image tool.Free
Workflow · Product and engineering

Web App Go-Live Review

Checks a web app before launch across launch readiness, performance, technical SEO, AI search visibility, responsive layout and accessibility, then delivers an evidence-backed go or no-go recommendation with owned fixes.Free
Skill · Product and engineering

Web Performance Audit

Audit and improve a web app's page speed before launch with Lighthouse and PageSpeed Insights. Use when you need mobile and desktop Lighthouse runs on key URLs, Core Web Vitals (LCP, INP, CLS) read from both lab and field data, every failing audit mapped to a concrete code or config fix, a prioritized fix plan, and a re-measurement that proves the gain.Free

Page 1