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

/algolia-observability

@820dfc8
Run it yourself

Instrument an Algolia integration for actionable availability, latency, freshness, relevance, and event-health signals. Use when defining dashboards, alerts, traces, or service objectives. Trigger with "monitor Algolia", "Algolia metrics", or "search observability".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈72 tokens for metadata: the name and description. ≈837 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 ≈290 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 Search Observability

Overview

This skill instruments the application-owned search journey rather than substituting generic provider claims. It connects client outcomes, request IDs, index publication, source freshness, and product-level relevance indicators.

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

  • Derive thresholds and objectives from the product SLO and measured baseline; do not use universal latency numbers.
  • Separate application latency from Algolia request latency and rendering time.
  • Track source snapshot to completed indexing task to searchable sentinel for freshness.
  • Treat event delivery and query-ID coverage as their own health surface.

Authentication

Telemetry must exclude API keys, raw personal data, sensitive queries, and unrestricted record payloads. Use approved read-only monitoring access where provider data is needed.

Instructions

  1. Define the user journey, owned SLOs, current baseline, and incident-routing owner.
  2. Instrument operation, outcome, duration, index alias, environment, SDK version, request ID, and bounded retry count.
  3. Add freshness markers linking source snapshot, task completion, and searchable sentinel.
  4. Measure no-result and event coverage using privacy-reviewed aggregation.
  5. Build dashboards and alerts from sustained error-budget or baseline deviation, not a copied threshold.
  6. Test telemetry during success, denial, timeout, stale-index, and event-failure scenarios.

Approval Boundaries

Do not log secrets or raw sensitive queries, create arbitrary alert thresholds, or enable high-cardinality labels without review.

Output

Return the signal catalog, field and redaction schema, SLO mapping, dashboards, alerts, synthetic checks, test evidence, and known blind spots.

Error Handling

Condition Response
Request ID unavailable Preserve local trace correlation and full redacted error metadata.
High cardinality detected Aggregate or hash approved identifiers.
Provider and app latency differ Split the spans and investigate the dominant segment.
No product SLO exists Report measurements and request an owner decision.

Examples

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

Input:

journey=product-search; slo=company-owned; fields=operation,outcome,duration,index

Expected handoff:

secret-fields=blocked; freshness-sentinel=pass; alert-threshold=baseline-derived

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

    The skill provides guidelines and resources for instrumenting Algolia observability. It includes explicit security instructions to avoid logging secrets or sensitive data and uses official documentation from a well-known service. No malicious patterns were detected.

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

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-observability