--- name: instantly-hello-world-4fd01346f40c description: >- Run one bounded read-only Instantly API v2 request with explicit authentication and response validation. Use when verifying a new API key, workspace, or HTTP client before deeper integration work. Trigger with "test my Instantly API key", "make a first Instantly request", or "list Instantly campaigns safely". argument-hint: "[accounts|campaigns] [limit]" allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit version: 1.13.0 author: Jeremy Longshore license: MIT tags: - saas - instantly - hello-world model: inherit effort: high compatibility: Designed for Claude Code; live verification requires network access and an approved Instantly workspace and API v2 key --- # Instantly Bounded First Request ## Overview Prove a new Instantly integration with the smallest safe request and a redacted evidence handoff. 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 - The API v2 base URL is https://api.instantly.ai/api/v2. - Authorization uses an API v2 key as a Bearer token. - A 401, 403, or 429 must fail the smoke test rather than trigger mutation or broad retries. ## Authentication Use an API v2 key as `Authorization: Bearer ` 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. Confirm the target workspace and create a read-only key with accounts:read or campaigns:read. 2. Store the key in a server-side environment variable and never print it. 3. Send one list request with a limit no greater than five. 4. Validate HTTP status and expected collection/pagination fields. 5. Capture latency, status, route template, and redacted item count. 6. Stop after the proof; do not create, patch, activate, or delete resources. ## 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: ```text resource=accounts; limit=5; workspace=staging ``` Expected handoff: ```text status=200; items=bounded; auth=redacted; mutation=none ``` ## Resources - [Skill-specific official documentation](references/official-docs.md) - [Instantly API v2 documentation](https://developer.instantly.ai/) - [Instantly API v2 OpenAPI document](https://api.instantly.ai/openapi/api_v2.json) --- Source attribution: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/instantly-pack/skills/instantly-hello-world/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2025 Jeremy Longshore Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/instantly-pack/skills/instantly-hello-world/SKILL.md Attribution basis: Source repository record Fields of work: Marketing, Product Management Roles: Growth Marketer, Product Marketer, Technical Product Manager Specialties: API, Design, Frontend, Testing Tools: Instantly Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 04da11845f3da4291092ee6624ad979fa50456dda2b9d696a760e8115b41a044