← PlanableCONTENT HISTORY
WHAT CHANGED
Update to Planable
Snapshot Nov 13, 2026 · 12:08 UTC · version 2.1.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Planable and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "List every Planable post waiting for approval across workspaces, with the ones going live soon first. Use when the user asks what needs their approval, what is stuck in review, or what is holding up the calendar.",
"included_files": [],
"name": "pending-approvals-roundup",
"skill_md_contents": "---\nname: pending-approvals-roundup\ndescription: 'List every Planable post waiting for approval across workspaces, with the ones going live soon first. Use when the user asks what needs their approval, what is stuck in review, or what is holding up the calendar.'\n---\n\n# Approvals roundup\n\nOne overview of the posts that wait for approval across workspaces, most urgent first.\n\n## 1. Scope\n\n- Workspaces: one, a few, or all. Default: all of the user's workspaces. With more than 10, say how many you will check and ask whether to narrow it down first.\n- Whose approval: the user's own (approvalStatus PENDING_MY_APPROVAL, the default) or every post that is not fully approved (NOT_APPROVED and PARTIAL_APPROVED). REQUESTED_BY_ME shows the posts the user sent to others for approval.\n\n## 2. Fetch\n\nFor each workspace in scope, call list_posts with the approvalStatus filter and page through until nextOffset is empty. Also call list_posts with postStatus WITH_ERRORS for the same workspaces, since failed posts often block the plan too.\n\n## 3. Present\n\nGroup by workspace. For each post show the page, a short text preview, its date and its approval state.\n\n- First the posts dated within the next 48 hours, marked as urgent.\n- Then the other dated posts by date, then the posts with no date.\n- Publishing errors in a separate block.\n\nIf nothing waits for approval, say so in one line.\n\n## 4. Act on request\n\nOffer to open a post in full (get_post), approve it (approve_post), or send it back with a reason (disapprove_post, then create_comment with the reason). Approve or reject only the posts the user names, after they confirm, and never by default. Approving needs an approval workflow in the workspace (approvalWorkflow from get_workspace_details is not \"none\") and the user's approval permission.\n"
}SHA-256 of public snapshot: 255b8bd81cc4941da72ee6ef4e817f7de1d74a521426210bed0704acd52a41ae