Skip to content
cccskills
FreePublished on GitHub

alchemy-core-workflow-b

Build NFT collection browsers and ownership checks with Alchemy NFT API v3. Handle paginated results, missing metadata, and media fallbacks, with optional viem reads to compare indexed results against contract state recorded on the blockchain.

OriginalShow the original description

Build an NFT discovery workflow with Alchemy NFT API v3 and isolate typed on-chain reads through viem. Use when creating collection explorers or ownership checks. Trigger with "Alchemy NFT API", "NFT collection explorer", or "read an NFT contract".

Run score Not tested

See how to install

Good for

  • Building an NFT collection browser
  • Retrieving an owner's NFTs across multiple result pages
  • Handling missing metadata and media
  • Comparing NFT ownership results with contract state

Files included (2)

  • SKILL.md4.8 KB
  • references/official-docs.md3.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Alchemy NFT Discovery and Contract Read Workflow

Overview

Build an NFT discovery workflow with Alchemy NFT API v3 and isolate typed on-chain reads through viem. This workflow produces a reviewable artifact and negative-path evidence before any live side effect.

Prerequisites

  • Current first-party Alchemy documentation for the selected product, chain, feature, client, authentication method, limit, and lifecycle.
  • Named product, application, security, data/privacy, budget, release, and operations owners appropriate to the requested scope.
  • Synthetic or approved non-production fixtures, a credential canary, explicit success criteria, and a tested rollback boundary.

Current Contract

NFT API responses, metadata availability, spam classification, pagination, and supported networks are endpoint-specific. NFT indexing is not chain finality, and cached media is not proof of ownership. Contract state reads use the declared viem chain and ABI; ownership-sensitive decisions require an explicit block/finality policy.

Authentication

Use a scoped application API key in the server boundary. Validate owner and contract addresses before lookup. Treat queried owner addresses, collections, and behavioral analytics under the product's privacy and retention policy.

Instructions

  1. Choose owner discovery, collection enumeration, metadata lookup, or contract-state verification and confirm the endpoint's current chain support.
  2. Define the response schema, spam/filter policy, metadata and media fallbacks, page-key handling, maximum pages, and freshness label.
  3. Fetch through a narrow NFT API v3 adapter, validate every page, and retain provenance for cached versus original media without executing remote media content.
  4. For on-chain verification, create a viem public client on the same declared chain, use a reviewed minimal ABI, and record the block context.
  5. Reconcile indexer output with contract reads only where the product requires it; represent disagreement and reorganization risk explicitly.
  6. Test empty, paginated, malformed metadata, spam-filtered, unsupported-chain, and indexer-versus-chain disagreement before release.

Tool Discipline

Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Skill invocation alone does not authorize network access, credentials, wallet addresses, customer data, plan changes, spend, key creation or rotation, webhook changes, deployment, replay, transaction construction, signing, broadcast, or deletion.

Approval Boundaries

Product/privacy owners approve address use and analytics. Security approves remote-media handling and ABI/source provenance. Transactions, approvals, mints, or marketplace writes are outside this read-only workflow.

Error Handling

  • Do not infer ownership from an image URL or stale cached metadata.
  • Do not silently exclude assets without recording the configured spam/filter policy.
  • If the NFT index and contract read disagree, show an indeterminate state and reconcile at an approved block/finality point.

Output

Return the query purpose, chain/endpoint proof, schema and pagination contract, filter policy, media safety rules, optional viem read evidence, disagreement behavior, tests, and rollback. Mark assumptions, observations, source dates, environment-specific behavior, owners, and unresolved gaps explicitly.

Examples

  • Page through a public test collection and retain the next-page token until exhaustion while labeling cached media provenance.
  • Verify an ownership-sensitive result with a typed ownerOf read at a recorded block and surface disagreement instead of choosing one source silently.

Validation

Exercise and record expected and observed results for:

  • empty collection
  • multi-page owner
  • missing metadata
  • unsafe media URL
  • unsupported network
  • indexer/contract disagreement

Resources

  • Current first-party evidence map — recheck dated Alchemy sources before execution.
  • Treat observed account, application, network, indexer, chain, or provider behavior as environment-specific evidence, never a universal guarantee.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.

  • Adding regression checks to an Abridge integration repository
  • Testing consent and note-release handling
  • Checking logs for sensitive data exposure
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.

  • Separate recording problems from upload failures
  • Investigate note creation delays and editor issues
  • Identify the responsible team for Epic handoff failures
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.

  • Map a clinical note workflow for a care setting
  • Check where consent and patient identity are verified
  • Review draft notes against linked evidence before sign-off
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.

  • Checking Abridge note section mappings to Epic templates
  • Auditing a department’s approved documentation handoff
  • Preparing test evidence and a go or no-go decision
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.

  • Reviewing adoption after an Abridge rollout
  • Preparing evidence for a renewal decision
  • Comparing workflow outcomes across care settings
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.

  • Preparing reviewed evidence for an Abridge support case
  • Documenting redactions and excluded data
  • Collecting approved operational details for an incident
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 25, 2026

See all skills by jeremylongshore

Report a problem with this skill