# Read Pinterest platform resources for context

> Tier: recipe. Operating recipe: real tool sequence, core rules, known traps.

Platform resources read for the lookups other skills lean on.

**Intent.** The platform-level reference data behind the account reads.

## When to use

- Resolving enums and reference values during other work.

## When not to use

- No specific contraindication beyond the preconditions below.

## Sources

Required: Pinterest Ads

## Preconditions

- The account is ticked in the dashboard, confirmed via list_accounts.

## Inputs

- `window`: Analysis window. Default: last 30 days.

## Procedure

1. Pull the needed platform resources. — tools: `pinterest_get_platform_resources`
2. Cache the mapping in the working notes for the session.

## Decision rules

- **When** A code appears that the mapping does not cover → **conclude** Quote it raw and flag it: guessed labels corrupt reports downstream.

## Evidence requirements

- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.

## Human approval boundary

- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

## Failure modes

- Reference data versions drift with the API: date the lookup.

## Output

- **Readout**: The figures, with windows and accounts named.
- **Flags**: What deserves a deeper skill or a human decision.