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

/algolia-data-handling

@820dfc8
Run it yourself

Design and audit the data lifecycle for records and user events sent to Algolia. Use when minimizing indexed fields, handling deletion requests, or documenting retention and privacy boundaries. Trigger with "Algolia privacy", "delete Algolia user data", or "index data review".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈75 tokens for metadata: the name and description. ≈879 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 ≈301 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 Data Handling Review

Overview

This skill maps which data leaves the source system, how it becomes searchable records or events, and how correction and deletion propagate. It does not claim legal compliance; it produces technical evidence for the responsible privacy owner.

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

  • Index only fields required for retrieval, ranking, filtering, display, or approved analytics.
  • Treat attributesToRetrieve as response shaping, not as a substitute for excluding sensitive data from records.
  • Keep source-system identity mappings so corrections and deletions are reproducible.
  • Handle record deletion and Insights user-token deletion as separate surfaces with separate evidence.

Authentication

Use a restricted backend write key for record changes and the documented authorization for user-data deletion. Never include raw secrets or direct personal identifiers in logs or example events.

Instructions

  1. Inventory record fields, derived attributes, event fields, user tokens, environments, and downstream exports.
  2. Classify each field by purpose, sensitivity, source authority, and deletion requirement.
  3. Remove unnecessary fields before indexing and test that UI and ranking behavior still work.
  4. Implement idempotent correction and deletion paths with request IDs and target indices.
  5. Verify absence using bounded lookups and preserve evidence without retaining the deleted value.
  6. Document retention ownership, incident escalation, and gaps for privacy or legal review.

Approval Boundaries

Do not make legal conclusions, bulk-delete records, change retention policy, or expose protected values while verifying a request.

Output

Return the data-flow map, field inventory, minimization changes, deletion/correction procedure, verification evidence, unresolved provider retention questions, and named policy owner.

Error Handling

Condition Response
Identity mapping missing Stop and reconcile the source identity before deletion.
Deletion task incomplete Retain the task ID and verify state before closing.
Event token contains PII Stop sending it and escalate remediation.
Policy answer unavailable Record the question for the privacy owner or provider.

Examples

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

Input:

request=privacy-123; surfaces=records,events; indices=customer_search

Expected handoff:

records=removed-and-verified; events=requested; legal-determination=not-made

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 structured workflow for auditing Algolia data privacy and handling record deletions. It adheres to security best practices by explicitly instructing against hardcoding secrets and restricting tool usage to official documentation. The low-risk finding relates to the inherent surface for indirect prompt injection when processing external data.

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

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-data-handling