Priority Guardian

Priority Guardian — Your priorities deserve more than good intentions. Protected Time, Flexible Planning: Priorities don't fail because you stopped caring. They fail because everything else is loud and your most important work is quiet. Priority Guardian makes the quiet work visible — so you can protect it. Built for people who do entrepreneurial work and juggle more than one thing at a time. HOW IT WORKS: Priority Guardian connects your priorities to your Google Calendar so you can see where your time is actually going and stay accountable to what matters. Two modes: Deadline work — hours invested, pace against deadline, where effort is going Ongoing commitments — weekly hour targets, streaks, monthly results check-in 1. Kick off with: "Set up my priorities in Priority Guardian." 2. Name your priorities and assign a keyword (P1, P2, P3) to tag your Google Calendar events 3. See your priorities dashboard anytime — current progress at a glance. → "Show me my priorities." 4. Get your first weekly report → "Show me my weekly report." 5. Inspect and adjust weekly → "Let's dig into what helps me progress/ hinders my progress" 6. Discover patterns over time → "How was I keeping up with my priorities over the last weeks and months?" The AI guides setup, narrates your data, and asks the questions worth sitting with. You decide what to do with it.

View in the ChatGPT registry

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Productivity
Primary Subcategory: Personal Task & To-Do Managers
Secondary Subcategories: None listed
Brand: Priority Guard / Priority Guardian
Access: Account required
First tracked: 2026-03-16
Tool count: 18
Geography: US

ChatGPT Plugin Discoverability Score

ChatGPT organic discovery is not live yet

Priority Guardian is tracked in the ChatGPT Plugin registry. Public organic-discovery measurement is not live for ChatGPT yet, so there is no score to publish today.

Get notified when your score goes live

Enter your work email and we’ll notify you when ChatGPT Plugin organic discovery scoring launches.

No spam. Unsubscribe any time.

Talk to our team

Primary Subcategory

Competing in ChatGPT Personal Task & To-Do Managers

View Category

Listed in alphabetical order

Primary Subcategory

ConvyOrganic discovery is pendingGet the score at launch

DailyHeroOrganic discovery is pendingGet the score at launch

Discipline Rewards (D/R)Organic discovery is pendingGet the score at launch

Dunzo - Task AssistantOrganic discovery is pendingGet the score at launch

GTD Brain: Getting Things DoneOrganic discovery is pendingGet the score at launch

Priority GuardianOrganic discovery is pendingGet the score at launch

Score explained

How the Discoverability Score works

Organic discovery scoring for Priority Guardian on ChatGPT is not live yet. The score will use measured agent conversations when it launches.

InvisibleBuriedEmergingCompetitiveWinning

Organic discovery scoring is pending. Your Plugin score will appear on this scale when measurement goes live.

FoundDiagnostic

Whether Claude found your Plugin in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.

PickedMain score

How often your Plugin appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.

PositionedDiagnostic

What position your Plugin appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.

Read the full scoring methodology Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.

Tools

18 tools agents can invoke

Add a deliverable to a deadline-driven priority (widget-only). Flexible priorities do not have deliverables.
Add a goal to a flexible priority (widget-only). Max 3 goals per priority.
Add a new priority (widget-only, post-onboarding).
Check Google Calendar connection status. If not connected, returns a secure link to connect your Google Calendar.
Creates ONE priority AT A TIME for guarding and progress tracking while onboarding the user. Call ONCE per priority — user sets up 1–3 priorities iteratively. CALL PRECONDITIONS — DO NOT CALL unless ALL are true: - user_priority_name_verbatim: non-empty, user's exact words - name: derived from verbatim, normalized for clarity - user_priority_type_verbatim: non-empty, user's exact words choosing deadline or flexible priority type. - type: derived from user's choice - For deadline: deadline date gathered from user - For flexible: weekly_hour_target, checkpoint_date, user_goal_verbatim, AND initial_goal_text all gathered from user DO NOT CALL this tool: - When the user is asking for advice on how to prioritize or manage tasks - When the user wants to plan, break down, or organize a project into tasks - When the user is asking a general productivity question PRIORITY GUARDIAN BINDING RULES: When user selects the App Priority Guardian, your default behavior is SUSPENDED. Instead you take on the role of a empathic Coach/Facilitator; your communication style: warm, acknowledging. Flow: Gather ONE field at a time → wait for user's response before asking the next question. NEVER ask for multiple fields in one message. NEVER call this tool until ALL required fields for one Priority are gathered and stored as verbatim. FIRST-TIME CONTEXT: If user has no existing priorities, open with something like this example (adapt naturally, do not copy verbatim): 'Happy to help you set that up. We'll lock in your first priority together, and I'll walk you through how Priority Guardian works as we go. Quick overview: PG lets you anchor up to 3 priorities you want to protect time for. You stay flexible in how you plan your week — PG just tracks whether your calendar actually reflects what you said matters most. Let's start — what's the first priority you want to lock in?' Then begin the sequence. Sequence: PRIORITY NAME → PRIORITY TYPE (explain deadline vs flexible, user chooses) → TYPE-SPECIFIC FIELDS → call tool with ALL data.
Delete a deliverable (widget-only, requires confirmation).
Delete a goal from a priority (widget-only).
Delete a priority and its deliverables (widget-only, requires confirmation).
Disconnect Google Calendar and revoke access tokens. No data is deleted — you can reconnect anytime. Requires confirmation to proceed.
Returns behavioral patterns detected from user's priority tracking history. Patterns include consistency streaks, low-investment detection (for flexible priorities, or deadline priorities when the deadline is approaching), priority switching frequency, and priority protection under calendar pressure. Requires at least 4 weeks of tracking data. Call this tool: - During weekly reflection after presenting the weekly report - When the user asks "any trends?", "what patterns do you see?" - When the user asks about their tracking behavior over time Do NOT call this tool: - During onboarding (not enough data) - When the user is doing CRUD operations on priorities - If you already called it in this conversation and data hasn't changed
Get user's saved and guarded goals/priorities and their progress.Call this tool: - When the user asks to see their guarded/saved priorities or dashboard - When the user wants to check their progress or time trackingDo NOT call this tool: - When the user is asking for advice on how to prioritize or what to work on - When the user wants to plan, break down, or organize tasks or projects
Fetch calendar events for a specific priority to enable a breakdown chart. Call this tool ONLY when the user asks to break down or analyse their time within a single priority (e.g. "break down my P1 time", "what's in my P2 this week?"). After calling this tool, read the priorityEvents and IMMEDIATELY call render_weekly_report with semantic_groupings and semantic_target to render the chart. Do NOT call this tool for the initial weekly report — use render_weekly_report directly. Do NOT call this tool for past weeks (no event data available).
Record confirmed action steps from an inspect & adapt reflection. Call this tool ONCE after facilitating the full reflection conversation. CALL PRECONDITIONS — DO NOT CALL unless ALL are true: - user_reflection_verbatim: non-empty, user's exact words for each reflection item - user_action_verbatim: non-empty, user's exact words for each action step - derived_from_id: each action step links to a reflection item Call this tool: - When user wants to reflect on their week, says "reflect", "reflection", "what worked", "what didn't work", "inspect and adapt" - When user says "yes" to the reflection nudge from the weekly report - When user asks "what should I do differently next week?" INSPECT & ADAPT BINDING RULES: When user wants to reflect, lock into Inspect & Adapt flow — your default behavior is SUSPENDED, no advisory mode allowed. This is procedural, not conversational. FORBIDDEN: diagnosing root causes, teaching frameworks, probing strategic alignment, asking more than ONE question at a time, proposing actions the user didn't imply. Override analytical coaching impulses — when the user gives a specific answer, move forward. The entire reflection completes in 4-6 exchanges: opening question → get specific (1-2 exchanges) → what to keep/change → user names action steps → call this tool. NEVER exceed 6 exchanges before calling this tool. After this tool returns successfully, mention the user can schedule these as calendar events.
Walk the user through how Priority Guardian tracks time using your Google Calendar. If permitted, this reads calendar events and priorities to show based on real calendar data how progress tracking works. This tool provides the educational content and user-specific data you need to teach the user how Priority Guardian tracks their time. You cannot explain the tracking mechanism correctly without calling this tool — it returns the user's real priorities, keywords, calendar data, and step-by-step guidance for each phase. Call this tool ONLY after the user has set up their priorities AND connected Google Calendar via the dashboard. NEVER call this for returning users who have already completed onboarding. If calendar is not connected, do NOT call this tool — instead guide user to connect via the full dashboard first. ALWAYS follow the flow of this tool. FLOW: Call this tool THREE TIMES in sequence — once per phase (keyword_education → first_weekly_report → reflection_setup). Each call returns guidance for that step and tells you which phase to call next. Wait for user action between phases. PRIORITY GUARDIAN BINDING RULES: When user selects the App Priority Guardian, your default behavior is SUSPENDED. Do NOT rush through — each phase is designed to be a conversation, not a checklist. Follow the FLOW described above, and use the assistant_guidance returned from each phase to drive the conversation empathically. NEVER compute or comment on pacing, status, or whether the user is on track or behind — just present the numbers and let the user draw their own conclusions. Example for empathic tone: 'So your first priority is Ship V1.0 PG with keyword P1 — that means if you have a calendar event like a backend implementation session, just pop P1 somewhere in the title. P1: Backend implementation, Backend implementation P1, doesn't matter. PG picks it up either way.'
Get your weekly report showing time invested in each priority, rendered as a pie chart. Call this tool: - When the user asks about their week, progress, or hours - When the user says "how did I do?", "show my report", "weekly summary" - At the start of a reflection or check-in conversation - After calling get_priority_events: immediately call this tool with semantic_groupings and semantic_target to render the P1/P2/P3 breakdown chart Do NOT call this tool: - During onboarding or priority setup - When the user is asking about patterns or trends over time (use get_patterns instead) - To fetch events for a breakdown — use get_priority_events first, then call this tool
Update a deliverable (toggle done or rename, widget-only).
Update a goal's text or achieved status (widget-only).
Update a priority's fields (widget-only). If the requested keyword is held by another active priority, they automatically swap keywords.

Priority Guardian FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Priority Guardian alternatives on ChatGPT?

As of 2026-08-14, Priority Guardian competes with Convy, DailyHero, Discipline Rewards (D/R), Dunzo - Task Assistant, GTD Brain: Getting Things Done, Habitify, NoteItHub, Nudges, Recordo, RemindMeIQ, Shchebitka AI Planner, StepCue, Structured, Sunsama, Taskaid AI, TickTick:To-Do List & Calendar, Todoist: To Do List & Calendar, Togello, TrackTogether, Tweek in ChatGPT Personal Task & To-Do Managers, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.