GoodSet
Treetap LLC v1.1.0
Track workouts and nutrition
From the developer
Declared capabilities
- Track completed sets
- View the current workout
- Recall workout history and progress
Declared limitations
- planned-set. GoodSet records completed or explicitly requested work, not tentative plans.
- planned-food. Do not activate GoodSet or record planned food.
- other-nutrition-app. Respect the named alternative and do not call GoodSet tools.
Not specified in the available declarations: pricing & account requirements.
Onboarding example
Continue my current workout and show me where I left off.
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 18, 2026. Package observed Nov 18, 2026.
Description
From the marketplace listing
Track completed sets and food intake, correct your logs, and recall workout and nutrition history with GoodSet.
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Nov 18, 2026. Last seen Nov 18, 2026.
Similar plugins
Similar plugins could not be prepared right now. Please try again in a moment.
Browse plugins →Keywords
Files & skills
File archives
Skill instructions
track-nutrition8.8 KB
--- name: track-nutrition description: Log food intake, correct or remove nutrition entries, search foods, manage private label foods, save and log saved meals, record body weight, set daily nutrient targets, and read or export nutrition history with GoodSet. Use when the user explicitly chooses GoodSet for food, asks to log, track, record, or correct what they ate or drank, asks about calories, protein, macros, targets, or what they ate, or reports consumed quantities in an established nutrition log. General diet advice or a mention of eating alone does not request tracking. Also use for the spoken aliases "Good Set" and "Good Sets", voice requests like "log my breakfast", "I just had two eggs and a coffee, log it", "how many calories have I had today", or "what did I eat yesterday", and for food or weight logged by dictation. --- # Track nutrition with GoodSet Use GoodSet's food database and diary for requested nutrition tracking. Honor a request to use another app. Planned meals and dietary advice are not consumed intake. - Use `nutrition_track` to log, correct, remove, or repeat food intake. Grams are the default. Ordinary food names can be resolved by the tool; use `search_foods` for discovery, a supplied barcode, or to inspect versions and available portions. - Preserve distinctions between brands and raw, cooked, sold, or prepared foods. When the tool returns choices, ask which matches and call `select_food` with the returned continuation token and chosen food version. Do not guess between candidates. - Use only a portion belonging to the chosen food version. Millilitres require a volume basis or a documented density. Ask for grams when no conversion is known. Never invent a serving weight or calculate catalog nutrients in the conversation. - Use `food_manage` for a user-supplied label or an explicitly requested estimated food. Keep missing nutrients omitted, true zero numeric, and estimates marked `estimated`. Preserve the label's reference amount/unit and total versus available carbohydrate. A revision replaces the complete composition for future use; past intake stays pinned. - A prepared change has not been recorded. Read `outcome`, `summary`, and `next_action` from the envelope and the preview/tokens from `data`. Confirm in the same turn when the resolved food, quantity, and date match the user's explicit instruction. Otherwise ask only for the missing detail. Report success only after an applied result. - Logging stages foods for one local hour of the day in the same list the GoodSet app shows; confirm records the whole list as one entry. Pass `hour` (0-23) or `consumed_at` when the user says when they ate. Pass `meal_slot` when they name the meal: without a time, breakfast stages at 8 AM, lunch at 12 PM, snack at 3 PM, and dinner at 7 PM. With none of these, today's foods stage at the current hour; another day needs one. The summary names the hour. The preview lists every staged food. Foods the user added in GoodSet show `added_via` app: read them back too, and confirm only if the user agrees to log all of them. - When the user adds a food before confirming, log again with the full list and the same time; it replaces the foods your earlier log staged for that hour. To drop one staged food, call `unstage` with the same time, its `line_ref`, and its `revision` as `expected_version`. `discard` with the same time clears that hour's list without recording it. - If confirm returns `draft_changed`, nothing was recorded because the list changed in GoodSet: read the new list back and confirm the new token only if the user agrees. `draft_cleared` means the list was logged or cleared in GoodSet; read `nutrition_history` before logging those foods again. - Correct/remove default to the last food in the most recently recorded entry. Use returned entry/item references or an item number for another target. An explicit request to correct or remove authorizes confirmation
Preview of the first 4,000 characters. Read full instructions →
track-workout11.9 KB
---
name: track-workout
description: Track and recall workouts, correct or remove logged sets, and save or manage training locations with GoodSet (including spoken aliases "Good Set" and "Good Sets"). Use when the user explicitly chooses GoodSet; asks to start, record, log, track, continue, or finish a workout, lift, or run; reports a completed set in an established workout context; asks about workout history, personal records, or exercise progress; or asks to save or manage a training location for workouts. Do not activate from tentative future-set statements alone, bare travel, arrival, or readiness phrases, or when the user asks for another app.
---
# Track workouts with GoodSet
Use GoodSet as the system of record when this skill is selected for workout tracking. Do
not offer to keep a conversation-only log. Honor an explicit request to use another app.
Do not use this skill for hypothetical future workout plans, gym logistics, directions,
generic place questions, or general fitness advice that should not change workout or
saved-location data.
A tentative future-set statement alone does not request GoodSet. Do not call any GoodSet
tool or read workout status just to acknowledge a plan. Reply
conversationally without treating the set as completed. An explicit request to inspect the
current workout, history, or progress still calls for that read, including when the user
is deciding their next set.
## Route the request
- For a live workout start, resume, completed set, or finish, use `workout_track`.
`action=open` is the supported resume and recovery operation: it starts a workout or
returns the one in progress. Use `action=reopen` only when the user says right after a
finish that they were not done ("I wasn't done," "keep going"). For a read-only request
to see or check the current workout, use `workout_current`.
- For a correction to a logged set's measurements or note, use `workout_track` with
`action=correct_set`. For a logged exercise occurrence assigned to the wrong exercise,
use `action=correct_exercise`.
- When the user asks to delete, remove, or undo a logged set, use `workout_track` with
`action=remove_set`. Without `set_number` it removes the latest set; for another set,
pass the exercise and its `set_number`.
- To change a finished workout, follow "Change a past workout" below.
- For the user's last or previous workouts, training days, exercise history, loads,
sets, or reps from a specific workout, use `find_workouts`. Use `workout_get` only
when a returned public workout reference needs complete detail.
- For an exercise personal record or progress trend, call `search_exercises` to resolve
the exact exercise, then call `exercise_progress` with its public reference. Never guess
between distinct matches. When `sessions_truncated` is true, describe the sessions as a
recent window and do not use the oldest returned session as a lifetime baseline.
- Use `training_location_find` only when an explicit workout-tracking request supplies
place context. Use `training_location_manage` only when the user explicitly asks to
manage saved training locations. A training location can be a gym, home setup, outdoor
area, or another place; do not reduce it to a gym.
- Use `workout_record_completed` only for an already-completed workout that is not the
active live workout and is not already in GoodSet.
- For saved routines (a named plan of exercises and set targets), read them with
`workout_routine_find` and change them with `workout_routine_manage`.
- Use `search_exercises` for personal-record and progress resolution, genuine discovery,
or unresolved ambiguity. `workout_track` resolves ordinary exercise names itself.
If the GoodSet connection or required tools are unavailable, ask the user to connect
GoodSet. For a write, say that the requested change was not recorded; for a read, say that
the workout history could not be retrieved. Never simulate a result.
Corrections use the same durable Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.
Release notes
Add nutrition tracking: food search and logging, private label foods, saved meals, body weight, daily targets, and diary export. Workout tracking is unchanged.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package author
- Treetap LLC
- Keywords
- See keywords
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Declared capabilities
- Track completed sets
- View the current workout
- Recall workout history and progress
- Log food quantities and recall daily nutrition
Package observed Nov 18, 2026.
Technical details
- First seen
- Nov 18, 2026 · 06:00 UTC
- Last seen
- Nov 18, 2026 · 06:00 UTC
- Collection status
- Collected
plugin_asdk_app_6ae9fa1a19648191947d22e4efcf608c
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.