← FerrisCONTENT HISTORY
WHAT CHANGED
Update to Ferris
Snapshot Nov 3, 2026 · 00:13 UTC · version 1.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Ferris and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Look at what changed for the user in Ferris over the last few days and propose concrete next tasks. Use when the user asks what's new, what changed, what needs their attention, or what to work on next in Ferris.",
"included_files": [],
"name": "whats-next",
"skill_md_contents": "---\nname: whats-next\ndescription: Look at what changed for the user in Ferris over the last few days and propose concrete next tasks. Use when the user asks what's new, what changed, what needs their attention, or what to work on next in Ferris.\n---\n\n# What's next in Ferris\n\nTurn the user's recent Ferris activity into a short, ordered list of next actions.\n\n## Steps\n\n1. Call `list_my_recent_updates` with `days: 7`. If the user names a project, first get its id from `list_projects` and pass it as `project_id`. If the user asks about a shorter or longer period, set `days` from 1 to 14.\n2. If the response has `has_more: true`, call again with a higher `limit` (up to 100). If it has `projects_skipped`, tell the user that some projects were left out, and offer to look at one project at a time.\n3. Read the updates and decide what needs the user. Put them in this order:\n - `client_question`: a client is waiting for an answer.\n - `mention`: someone asked the user something.\n - `unblocked`: work the user can start now.\n - `assigned` and `meeting_action_item`: new work for the user.\n - `comment` and `updated`: changes to the user's tasks to review.\n4. For the most important items, call `get_task` or `list_task_comments` when the reason alone does not say what to do.\n5. Answer with three to five next actions. For each one, give:\n - the action, as one short sentence that starts with a verb (\"Reply to Dana about the go-live date\")\n - the project and task, with the task's link\n - why it matters now, in a few words\n6. End with one line that lists the updates you did not include, grouped by type, so the user knows nothing was hidden.\n\n## Rules\n\n- Do not create, change, or comment on anything unless the user asks. Offer instead: \"Want me to draft the reply to Dana?\"\n- If there are no updates, say so in one line and offer to look further back with a larger `days`.\n- Use the dates in the updates. Say \"yesterday\" or \"on Monday\", not raw timestamps.\n"
}SHA-256 of public snapshot: ba3a33d1137ba466327803f9efe2954ee3b3621afeeef2c4ba4023f3d1917f07