By name: clanky-work-tracker description: Provider-neutral work tracker protocol for using configured tracker MCP servers, CLIs, or skills and binding tracker refs to Clanky sessions. when_to_use: Use when SELF.md, the project's AGENTS.md, or the user designates a work tracker (Linear, GitHub Issues, Jira) and the task involves durable work, implementation, debugging, review, status, issues, tickets, notifications, or follow-up. allowed_tools: - mcp_list_tools - mcp_call - work_tracker_link deps: []
Clanky Work Tracker
Treat the configured work tracker as part of the working context. Do not wait for the user to remind you to use it when the task is durable work.
Operating Model
- Use provider-specific MCP servers, CLIs, or skills for tracker actions such as creating issues, reading inboxes or notifications, commenting, assigning, and changing status.
- Use
work_tracker_linkonly after an external tracker issue exists, so Clanky can remember which session maps to that provider issue. - Prefer the tracker provider and workspace/team already configured for this project when that context is available.
- If no tracker MCP/tool/skill is available, say
tracker_update_skippedwith the concrete reason. Do not pretend a tracker update happened.
Native Behavior
- At the start of substantial implementation, debugging, review, or planning work, look for a relevant existing tracker issue before creating a new one.
- If the configured provider exposes inbox, notification, assigned-issue, or update-feed tools, check them at natural boundaries: when beginning work, before claiming status, and before finalizing. Do not busy-poll.
- Keep tracker comments short and useful: what changed, what was verified, and what risk remains.
- Preserve
providerKind,providerId, external issue id, identifier, URL, session id, and relevant file scope when linking.
MCP Pattern
Use mcp_list_tools first when exact server or tool names are unknown. Then call the provider tool through mcp_call, and finally call work_tracker_link with the issue returned by the provider, setting providerKind to match the configured provider (e.g. linear, github, jira).