Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/algolia-prod-checklist

@820dfc8
Run it yourself

Run a fail-closed production readiness review for an Algolia-backed search release. Use when promoting new indices, settings, credentials, UI behavior, or event tracking. Trigger with "Algolia production checklist", "search go-live", or "Algolia launch review".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-prod-checklist

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈71 tokens for metadata: the name and description. ≈811 when used: this file. ≈333 more on demand in 1 file.

Description uses 3.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈286 characters, or 3.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Algolia Production Readiness Review

Overview

This skill consolidates the release evidence needed to decide whether an Algolia search surface is ready. It uses organization-owned SLOs and policies rather than hard-coded latency or response targets.

Prerequisites

  • A named repository, environment, and Algolia application or index in scope
  • The local lockfile and installed client types as implementation authority
  • A safe read-only query or explicitly disposable test target
  • Current first-party documentation for any provider behavior that affects the change

Tool Discipline

Use Read, Glob, and Grep to inspect local code, configuration names, tests, and dependency versions. Use WebFetch only for current official Algolia documentation. Use Write or Edit only after identifying the target files, constraints, and verification plan.

Current Contract

  • Bind all evidence to a release SHA, target application, index state, and source snapshot.
  • Verify least-privilege browser, server, indexing, monitoring, and event credentials separately.
  • Exercise representative relevance, filter, facet, empty-state, error, and accessibility paths.
  • Require tested rollback for both application code and index or settings state.

Authentication

Confirm secret-store ownership, key ACLs, index restrictions, rotation, and exposure scans. Never include credential values in the readiness packet.

Instructions

  1. Freeze the candidate SHA and inventory code, records, settings, synonyms, rules, keys, and event surfaces.
  2. Run schema, unit, integration, security, accessibility, and representative query gates.
  3. Verify indexing tasks, counts, sentinel records, environment mapping, and rollback target.
  4. Review observability against owned SLOs and exercise alert or incident routing.
  5. Validate event consent, stable user tokens, query IDs, and provider event validation where applicable.
  6. Record pass, fail, waiver owner, evidence link, expiration, and final go/no-go decision.

Approval Boundaries

Do not waive a failed security, rollback, data-integrity, or required branch-protection gate without the named authority and durable evidence.

Output

Return a release-bound checklist, evidence links, failed and waived gates, credential matrix, rollback rehearsal, approvers, and explicit go/no-go outcome.

Error Handling

Condition Response
Evidence belongs to another SHA Rerun or reject it.
Rollback not rehearsed Hold production promotion.
Threshold has no owner Treat it as observation, not a gate.
Required gate pending Outcome remains no-go.

Examples

Use this compact input and expected handoff to calibrate scope and evidence quality.

Input:

release=abc123; app=production; index=products_20260910; source=snap-184

Expected handoff:

required=31/31-pass; waivers=0; rollback=rehearsed; decision=go

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a production readiness checklist for Algolia-backed search releases. It focuses on auditing configuration, credentials, and indexing state while emphasizing security best practices, such as excluding credential values from reports and restricting network access to official documentation.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[repository-path] [release-sha]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "algolia",
  "production"
]
model
inherit
effort
medium
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-prod-checklist