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

/instantly-data-handling

@820dfc8
Run it yourself

Govern Instantly lead, email, suppression, export, and deletion data with explicit privacy controls. Use when mapping personal-data flows or reviewing an export, suppression, retention, or erasure request. Trigger with "map Instantly data flows", "export Instantly leads safely", or "handle an Instantly deletion request".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/instantly-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

≈87 tokens for metadata: the name and description. ≈978 when used: this file. ≈688 more on demand in 1 file.

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

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.

Instantly Lead Data Governance

Overview

Map and constrain personal-data movement across lead ingestion, campaigns, webhooks, exports, logs, and deletion. Record assumptions, evidence, approval state, and rollback ownership so another operator can reproduce the result.

Prerequisites

  • The target repository, Instantly workspace, environment, and accountable owner
  • Current security, privacy, compliance, capacity, and change-control requirements
  • An approved API v2 key only when a bounded live verification is necessary

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Instantly documentation and package metadata. Use Write or Edit only when implementation was requested and exact target files are known; never write credentials, lead data, email content, or unrestricted environment output.

Current Contract

  • Lead payload values may be scalar values; nested arrays are not a safe assumed contract.
  • Webhook payloads can contain lead and full reply/email content.
  • Deletion and export behavior must be tied to customer policy and signed terms, not generic assumptions.

Authentication

Use an API v2 key as Authorization: Bearer <key> against https://api.instantly.ai/api/v2. Grant only the endpoint-specific scopes needed, inject the key from an approved server-side secret manager, and never print, persist, commit, or place it in a URL. Treat key creation, rotation, revocation, member changes, workspace delegation, and production access as owner-approved actions.

Instructions

  1. Classify every input field, purpose, legal basis, retention owner, and downstream destination.
  2. Map create, list, patch, export, webhook, and delete paths with exact scopes.
  3. Minimize payloads and apply blocklist, consent, suppression, and deduplication controls before import.
  4. Redact email bodies, reply text, API keys, and personal identifiers from logs and evidence.
  5. Test access, correction, suppression, export, and deletion with synthetic records.
  6. Require privacy and data-owner approval before production retention or deletion changes.

Approval Boundaries

Do not create, rotate, reveal, or revoke keys; invite or remove members; delegate across workspaces; connect sending accounts; create or activate campaigns; import or delete leads; change suppression or retention; register, patch, resume, or delete webhooks; alter plans or paid capacity; transmit diagnostics; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested.

Output

Return the workspace-safe scope, files and contracts inspected, exact API v2 routes and required scopes, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action.

Error Handling

Condition Response
401 Stop and verify that the bearer key exists, is current, and was not revoked.
403 Stop and compare the operation with its exact required scope; do not broaden to all:all by default.
429 Coordinate the workspace-wide budget, honor endpoint overrides, and bound retries.
Schema or tenant mismatch Fail closed, preserve redacted evidence, and do not retry a mutation.

Examples

Use a compact handoff that makes scope, mutation authority, and evidence reviewable.

Input:

dataset=synthetic-leads; fields=email,first_name; retention=policy-bound

Expected handoff:

flow=mapped; minimization=pass; production-change=awaiting-owner

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 is designed for managing lead data within the Instantly platform and includes strong guidelines for privacy, redaction, and credential management. The main security consideration is the potential for indirect prompt injection resulting from the processing of external data such as email content and lead payloads.

  • 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
[data-flow-path] [workspace]
version
1.13.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "instantly",
  "data-handling"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live verification requires network access and an approved Instantly workspace and API v2 key

README badge

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