Update to Tailwind

{
  "name": "tailwind-pinterest-profile-audit",
  "description": "Audit the health of a connected Pinterest account's profile through Tailwind — authorization, domain verification, and profile completeness. Use when the user asks for a profile audit, an account checkup, or why their account may not be publishing.",
  "included_files": [],
  "skill_md_contents": "---\nname: tailwind-pinterest-profile-audit\ndescription: Audit the health of a connected Pinterest account's profile through Tailwind — authorization, domain verification, and profile completeness. Use when the user asks for a profile audit, an account checkup, or why their account may not be publishing.\n---\n\n# Pinterest profile health audit\n\nThis audit reports on the profile fields Tailwind can verify directly for a\nconnected Pinterest account. It is read-only: it consumes no credits, creates\nnothing, and changes nothing.\n\nIt is also narrow, and the narrowness is the point. Users asking for an\n\"account audit\" usually want to know why their impressions are low. That\nquestion cannot be answered from this data, and guessing at it from the fields\nbelow produces confident advice built on nothing. Report what the checks show,\nthen say plainly what this audit cannot see.\n\n## Run the checks\n\nCall `list_accounts`. Every field this audit reports comes from that one call.\n\nIf the user has more than one connected account and hasn't said which, ask\nrather than auditing all of them — a report about the wrong profile reads as\nauthoritative and wastes the user's time acting on it.\n\nCheck each field below. A field that is present and non-empty is a healthy\ncheck; a field that is missing or false is a finding.\n\n| Field | Healthy | Finding means | User action |\n| --- | --- | --- | --- |\n| `tokenAuthorized` | `true` | Tailwind cannot publish to this account at all. Nothing else in this report matters until it is fixed. | Reconnect the Pinterest account from the Tailwind dashboard. |\n| `isDomainVerified` | `true` | Tailwind has no verified website domain for this account. | Claim the website on Pinterest, then reconnect in Tailwind so the status refreshes. |\n| `avatarUrl` | non-null | No profile image. | Add a profile photo on Pinterest. |\n| `username` | non-null | No Pinterest username on record — usually a legacy connection. | Reconnect the account so Tailwind picks up the username. |\n\n`createdAt` is context, not a check. A recently connected account has little\nhistory behind it, which is worth saying when the user is asking why they see\nno results yet. Never report it as a problem.\n\n`displayName` is not checkable and must never be reported as a finding. The\nAPI falls back to the Pinterest username when an account has no name set, so\nthe field is non-empty for an account with no display name just as it is for\none with a display name — the two are indistinguishable from this response.\nClaiming a display name is present would be as wrong as claiming it is\nmissing, so say nothing about it either way.\n\nOrder findings by consequence, not by the order above: an unauthorized token\nstops publishing outright, a missing profile image does not.\n\n## The domain verification trap\n\n`isDomainVerified` is Tailwind's own record, and users regularly report that\nPinterest shows their site as verified while Tailwind shows it missing. When\nyou report this finding, say that it reflects what Tailwind has recorded, and\nthat a reconnect is what refreshes it. Do not tell the user their site is\nunverified on Pinterest — you cannot see Pinterest's side of it.\n\n`tokenAuthorized` is resolved live from Pinterest at request time, so it is\ntrustworthy in a way the stored fields are not. One consequence worth knowing:\nduring a Tailwind service degradation every account can report `false` at once.\nIf every account in a multi-account org looks unauthorized simultaneously,\ntreat that as suspect and say so rather than telling the user to reconnect all\nof them.\n\n## Report structure\n\nUse these sections, in this order:\n\n1. **Audit scope and data sources** — name the account audited, and state that\n   every finding comes from Tailwind account data.\n2. **Healthy checks** — the fields that passed. Say them; a report that lists\n   only problems reads as a broken account.\n3. **Findings and recommended actions** — one entry per finding, each with the\n   user action from the table.\n4. **Not available in this audit** — the section below.\n\nLabel every finding as **Tailwind account data**. This audit has no other\nsource. That labelling matters because the board audit does mix sources, and a\nuser reading both should be able to tell where each claim came from.\n\n## Not available in this audit\n\nState these explicitly rather than leaving them unmentioned — an unmentioned\ngap reads as a clean bill of health:\n\n- **Performance of any kind.** Impressions, saves, outbound clicks, follower\n  counts, and profile visits are not exposed here. If the user asked why their\n  numbers are low, this audit cannot answer that.\n- **Profile content quality.** Bio text, board cover imagery, and whether the\n  profile reads well for a niche are not visible.\n- **Pinterest-side account standing.** Whether the account is in good standing,\n  rate-limited, or has had content flagged is not visible.\n- **Whether Pins are being distributed.** Nothing here reports how Pinterest is\n  treating the account's content.\n\nDo not substitute a proxy for any of these. \"You have no profile image, which\nis probably why your impressions are low\" is exactly the kind of invented\ncausation this audit exists to avoid.\n"
}