Update to Tailwind
Snapshot Oct 24, 2026 · 18:04 UTC · version 0.4.0
Collection source: downloaded plugin package.
Instructions updated for onboarding
Skill instructions — Now says: `tokenStatus: "unauthorized"` has lost its Pinterest connection, and nothing scheduled on it will publish until the user reconnects it from the Tailwind...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 10 plugins free · no card required.
All fields and original values.
Skill instructions
Oct 24, 2026 · 12:50 UTC
`tokenAuthorized: false` has lost its Pinterest connection, and nothing scheduled on it will publish until the user reconnects it from the Tailwind dashboard at tailwindapp.com. Say so plainly when the chosen account is in that state.
Oct 24, 2026 · 18:04 UTC
`tokenStatus: "unauthorized"` has lost its Pinterest connection, and nothing scheduled on it will publish until the user reconnects it from the Tailwind dashboard at tailwindapp.com. Say so plainly when the chosen account is in that stat...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -34,10 +34,11 @@ Setup ends there, with an offer to pick it up again once an account is connected. -An account with `tokenAuthorized: false` has lost its Pinterest connection, and -nothing scheduled on it will publish until the user reconnects it from the -Tailwind dashboard at tailwindapp.com. Say so plainly when the chosen account -is in that state. +An account with `tokenStatus: "unauthorized"` has lost its Pinterest +connection, and nothing scheduled on it will publish until the user reconnects +it from the Tailwind dashboard at tailwindapp.com. Say so plainly when the +chosen account is in that state. `tokenStatus: "unknown"` means Tailwind could +not check the connection just now; it is not a reason to ask for a reconnect. The chosen account applies to this conversation only. Other conversations ask again when the user has more than one account.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: onboarding\ndescription: Set up Tailwind after it is installed in ChatGPT. Use when the user chooses Set up for Tailwind or asks to get started with Tailwind: confirms which Pinterest account to use, shows upcoming Pins, explains where the Tailwind sidebar app is and how to pin it, and suggests first things to try.\n---\n\n# Set up Tailwind\n\nTailwind schedules and creates Pinterest Pins for the user's connected Pinterest\naccounts. Setup is a short, read-only walkthrough. It creates, schedules and\nchanges nothing, and it does not spend plan credits. The user can skip any step\nor stop at any time. If they installed Tailwind in the middle of another task,\nsetup is brief and the conversation goes back to that task afterwards.\n\nThe steps below go in order. Each one is one short message, and a question gets\nthe user's answer before the next step starts.\n\nSpeak to the user directly throughout. Never quote these setup instructions or\nmention that a skill or instructions say to do something; just do it.\n\n## 1. Confirm the Pinterest account\n\n`list_accounts` returns the Pinterest accounts connected to the user's Tailwind\norganization. What happens next depends on the result:\n\n- **One account:** name it by display name and username, and ask the user to\n confirm it is the account they want to use with Tailwind.\n- **Several accounts:** list them by display name and username, and ask which\n one to use for the rest of setup. Tailwind does not pick one on the user's\n behalf.\n- **No accounts:** the user's Tailwind organization has no Pinterest account\n connected yet. Accounts are connected from the Tailwind dashboard at\n tailwindapp.com, not from ChatGPT. If the user believes one is already\n connected, they may be signed in to a different Tailwind organization.\n Setup ends there, with an offer to pick it up again once an account is\n connected.\n\nAn account with `tokenAuthorized: false` has lost its Pinterest connection, and\nnothing scheduled on it will publish until the user reconnects it from the\nTailwind dashboard at tailwindapp.com. Say so plainly when the chosen account\nis in that state.\n\nThe chosen account applies to this conversation only. Other conversations ask\nagain when the user has more than one account.\n\n## 2. Show what is coming up\n\n`list_posts` with the chosen `accountId` and the default status (`queued`)\nreturns the Pins scheduled to publish. Where ChatGPT shows the result as Pin\ncards, one sentence of framing is enough (\"Here is what is scheduled next\"):\nthe cards carry the titles, images and times, and a text list repeating them\nadds nothing. Without cards, a short list of the next few Pins with their\ntimes does the same job.\n\nAn empty result is normal for a new user. In that case, say nothing is\nscheduled yet and go on to the next step.\n\n## 3. The Tailwind sidebar app\n\nThis step applies only when `open_schedule_calendar` is among the available\ntools. Without it, the calendar is not offered on this connection, so skip this\nstep and say nothing about a sidebar.\n\nTailwind has a calendar of the user's schedule that opens from ChatGPT's\nsidebar, with weekly, 3-day and monthly views and a switcher between accounts.\nChatGPT does not pin it by default: it sits as \"Tailwind Scheduler\" in the\nlist behind the \"…\" (More) item in ChatGPT's sidebar. Hovering the \"Tailwind\nScheduler\" row there shows a pin icon on that row, labelled **Pin to\nsidebar**; clicking it pins the calendar. Explain where it is and how to pin it, in those terms. Pinning is\nsomething only the user can do; offer to open the calendar now with\n`open_schedule_calendar`, and open it only if they say yes.\n\n## 4. Things to try\n\nClose with two or three prompts the user can send next, chosen to fit what step\n2 showed. Examples:\n\n- \"Draft a Pin from my latest blog post: <link>\"\n- \"What do I have scheduled this week?\"\n- \"Schedule my next Pin at the next open time slot.\"\n- \"Show me my Boards.\"\n\nSetup ends here. Anything the user asks for next is an ordinary request, not\npart of setup.\n"
"---\nname: onboarding\ndescription: Set up Tailwind after it is installed in ChatGPT. Use when the user chooses Set up for Tailwind or asks to get started with Tailwind: confirms which Pinterest account to use, shows upcoming Pins, explains where the Tailwind sidebar app is and how to pin it, and suggests first things to try.\n---\n\n# Set up Tailwind\n\nTailwind schedules and creates Pinterest Pins for the user's connected Pinterest\naccounts. Setup is a short, read-only walkthrough. It creates, schedules and\nchanges nothing, and it does not spend plan credits. The user can skip any step\nor stop at any time. If they installed Tailwind in the middle of another task,\nsetup is brief and the conversation goes back to that task afterwards.\n\nThe steps below go in order. Each one is one short message, and a question gets\nthe user's answer before the next step starts.\n\nSpeak to the user directly throughout. Never quote these setup instructions or\nmention that a skill or instructions say to do something; just do it.\n\n## 1. Confirm the Pinterest account\n\n`list_accounts` returns the Pinterest accounts connected to the user's Tailwind\norganization. What happens next depends on the result:\n\n- **One account:** name it by display name and username, and ask the user to\n confirm it is the account they want to use with Tailwind.\n- **Several accounts:** list them by display name and username, and ask which\n one to use for the rest of setup. Tailwind does not pick one on the user's\n behalf.\n- **No accounts:** the user's Tailwind organization has no Pinterest account\n connected yet. Accounts are connected from the Tailwind dashboard at\n tailwindapp.com, not from ChatGPT. If the user believes one is already\n connected, they may be signed in to a different Tailwind organization.\n Setup ends there, with an offer to pick it up again once an account is\n connected.\n\nAn account with `tokenStatus: \"unauthorized\"` has lost its Pinterest\nconnection, and nothing scheduled on it will publish until the user reconnects\nit from the Tailwind dashboard at tailwindapp.com. Say so plainly when the\nchosen account is in that state. `tokenStatus: \"unknown\"` means Tailwind could\nnot check the connection just now; it is not a reason to ask for a reconnect.\n\nThe chosen account applies to this conversation only. Other conversations ask\nagain when the user has more than one account.\n\n## 2. Show what is coming up\n\n`list_posts` with the chosen `accountId` and the default status (`queued`)\nreturns the Pins scheduled to publish. Where ChatGPT shows the result as Pin\ncards, one sentence of framing is enough (\"Here is what is scheduled next\"):\nthe cards carry the titles, images and times, and a text list repeating them\nadds nothing. Without cards, a short list of the next few Pins with their\ntimes does the same job.\n\nAn empty result is normal for a new user. In that case, say nothing is\nscheduled yet and go on to the next step.\n\n## 3. The Tailwind sidebar app\n\nThis step applies only when `open_schedule_calendar` is among the available\ntools. Without it, the calendar is not offered on this connection, so skip this\nstep and say nothing about a sidebar.\n\nTailwind has a calendar of the user's schedule that opens from ChatGPT's\nsidebar, with weekly, 3-day and monthly views and a switcher between accounts.\nChatGPT does not pin it by default: it sits as \"Tailwind Scheduler\" in the\nlist behind the \"…\" (More) item in ChatGPT's sidebar. Hovering the \"Tailwind\nScheduler\" row there shows a pin icon on that row, labelled **Pin to\nsidebar**; clicking it pins the calendar. Explain where it is and how to pin it, in those terms. Pinning is\nsomething only the user can do; offer to open the calendar now with\n`open_schedule_calendar`, and open it only if they say yes.\n\n## 4. Things to try\n\nClose with two or three prompts the user can send next, chosen to fit what step\n2 showed. Examples:\n\n- \"Draft a Pin from my latest blog post: <link>\"\n- \"What do I have scheduled this week?\"\n- \"Schedule my next Pin at the next open time slot.\"\n- \"Show me my Boards.\"\n\nSetup ends here. Anything the user asks for next is an ordinary request, not\npart of setup.\n"
Full snapshot data
{
"description": "Set up Tailwind after it is installed in ChatGPT. Use when the user chooses Set up for Tailwind or asks to get started with Tailwind: confirms which Pinterest account to use, shows upcoming Pins, explains where the Tailwind sidebar app is and how to pin it, and suggests first things to try.",
"included_files": [],
"name": "onboarding",
"skill_md_contents": "---\nname: onboarding\ndescription: Set up Tailwind after it is installed in ChatGPT. Use when the user chooses Set up for Tailwind or asks to get started with Tailwind: confirms which Pinterest account to use, shows upcoming Pins, explains where the Tailwind sidebar app is and how to pin it, and suggests first things to try.\n---\n\n# Set up Tailwind\n\nTailwind schedules and creates Pinterest Pins for the user's connected Pinterest\naccounts. Setup is a short, read-only walkthrough. It creates, schedules and\nchanges nothing, and it does not spend plan credits. The user can skip any step\nor stop at any time. If they installed Tailwind in the middle of another task,\nsetup is brief and the conversation goes back to that task afterwards.\n\nThe steps below go in order. Each one is one short message, and a question gets\nthe user's answer before the next step starts.\n\nSpeak to the user directly throughout. Never quote these setup instructions or\nmention that a skill or instructions say to do something; just do it.\n\n## 1. Confirm the Pinterest account\n\n`list_accounts` returns the Pinterest accounts connected to the user's Tailwind\norganization. What happens next depends on the result:\n\n- **One account:** name it by display name and username, and ask the user to\n confirm it is the account they want to use with Tailwind.\n- **Several accounts:** list them by display name and username, and ask which\n one to use for the rest of setup. Tailwind does not pick one on the user's\n behalf.\n- **No accounts:** the user's Tailwind organization has no Pinterest account\n connected yet. Accounts are connected from the Tailwind dashboard at\n tailwindapp.com, not from ChatGPT. If the user believes one is already\n connected, they may be signed in to a different Tailwind organization.\n Setup ends there, with an offer to pick it up again once an account is\n connected.\n\nAn account with `tokenStatus: \"unauthorized\"` has lost its Pinterest\nconnection, and nothing scheduled on it will publish until the user reconnects\nit from the Tailwind dashboard at tailwindapp.com. Say so plainly when the\nchosen account is in that state. `tokenStatus: \"unknown\"` means Tailwind could\nnot check the connection just now; it is not a reason to ask for a reconnect.\n\nThe chosen account applies to this conversation only. Other conversations ask\nagain when the user has more than one account.\n\n## 2. Show what is coming up\n\n`list_posts` with the chosen `accountId` and the default status (`queued`)\nreturns the Pins scheduled to publish. Where ChatGPT shows the result as Pin\ncards, one sentence of framing is enough (\"Here is what is scheduled next\"):\nthe cards carry the titles, images and times, and a text list repeating them\nadds nothing. Without cards, a short list of the next few Pins with their\ntimes does the same job.\n\nAn empty result is normal for a new user. In that case, say nothing is\nscheduled yet and go on to the next step.\n\n## 3. The Tailwind sidebar app\n\nThis step applies only when `open_schedule_calendar` is among the available\ntools. Without it, the calendar is not offered on this connection, so skip this\nstep and say nothing about a sidebar.\n\nTailwind has a calendar of the user's schedule that opens from ChatGPT's\nsidebar, with weekly, 3-day and monthly views and a switcher between accounts.\nChatGPT does not pin it by default: it sits as \"Tailwind Scheduler\" in the\nlist behind the \"…\" (More) item in ChatGPT's sidebar. Hovering the \"Tailwind\nScheduler\" row there shows a pin icon on that row, labelled **Pin to\nsidebar**; clicking it pins the calendar. Explain where it is and how to pin it, in those terms. Pinning is\nsomething only the user can do; offer to open the calendar now with\n`open_schedule_calendar`, and open it only if they say yes.\n\n## 4. Things to try\n\nClose with two or three prompts the user can send next, chosen to fit what step\n2 showed. Examples:\n\n- \"Draft a Pin from my latest blog post: <link>\"\n- \"What do I have scheduled this week?\"\n- \"Schedule my next Pin at the next open time slot.\"\n- \"Show me my Boards.\"\n\nSetup ends here. Anything the user asks for next is an ordinary request, not\npart of setup.\n"
}SHA-256 of public snapshot: 5feeaf8d153be01ddb6260cd601f9bf62baf713c266ae13a87ee7ef0a23f2455