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

/algolia-deploy-integration

@820dfc8
Run it yourself

Plan and verify deployment of an Algolia-backed application with separated browser and server credentials. Use when releasing search code, index configuration, or event instrumentation. Trigger with "deploy Algolia", "Algolia production rollout", or "search release checklist".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

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

Description uses 3.8% 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 ≈306 characters, or 3.8%.

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 Deployment Integration

Overview

This skill coordinates application deployment with the Algolia assets it depends on. It treats code, records, settings, keys, and events as separate release surfaces with explicit ordering and rollback.

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

  • The browser receives only a search-only or secured key; write-capable keys stay in trusted server or job environments.
  • Pin application and index names per environment rather than deriving production targets from branch names.
  • Complete indexing tasks and representative queries before routing production traffic.
  • Deploy event instrumentation only after user-token, consent, query ID, and validation behavior are reviewed.

Authentication

Provision custom least-privilege keys through the approved secret store. Never place Admin keys in static build variables, client bundles, deployment logs, or preview environments.

Instructions

  1. Map the deploy platform, runtime boundaries, environment variables, index targets, and current rollback mechanism.
  2. Verify client packages and API usage against the pinned lockfile and current first-party docs.
  3. Prepare or verify target records, settings, synonyms, and rules before the application cutover.
  4. Deploy server and browser configuration with credential separation and redacted logging.
  5. Run a read-only health check plus representative search tests against the intended target.
  6. Record release SHA, index state, task receipts, smoke results, and rollback trigger.

Approval Boundaries

Do not overwrite production indices, rotate keys, promote settings, or enable events as an implicit side effect of application deployment.

Output

Return the release topology, environment map, credential classification, ordered deployment plan, smoke evidence, rollback steps, and unresolved approvals.

Error Handling

Condition Response
Browser bundle contains write key Stop deployment and rotate the exposed credential.
Target index is stale Hold traffic and complete or rollback indexing.
Health check passes but relevance fails Use representative query gates, not connectivity alone.
Rollback target unknown Do not cut over.

Examples

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

Input:

release=abc123; environment=production; browser-key=search-only; server-key=custom-write

Expected handoff:

index-task=complete; smoke=pass; representative-queries=pass; rollback=previous-release

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.

1 warning2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill coordinates Algolia deployments with a clear focus on security best practices, such as credential separation, least-privilege access, and explicit verification steps. No malicious patterns or high-risk behaviors were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 1 issue

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] [environment]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "algolia",
  "deployment"
]
model
inherit
effort
medium
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-deploy-integration