tracker
/tracker
Read, create and update tickets in whichever tracker the project uses (Linear, Jira, ClickUp, GitHub Issues, markdown files, or a custom one). Use whenever a task involves a ticket: reading its scope, creating one, moving its status, commenting. Never call tracker tools directly.
- Author
- lemramimel ↗
- Repository
- agent-team ↗
- Licence
- MIT
- Last repository change
- 06.11.2026
Assessment and security
- Files in this package
- 7
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Read, create and update tickets in whichever tracker the project uses (Linear, Jira, ClickUp, GitHub Issues, markdown files, or a custom one). Use whenever a task involves a ticket: reading its scope, creating one, moving its status, commenting. Never call tracker tools directly.
Original author description
Read, create and update tickets in whichever tracker the project uses (Linear, Jira, ClickUp, GitHub Issues, markdown files, or a custom one). Use whenever a task involves a ticket: reading its scope, creating one, moving its status, commenting. Never call tracker tools directly.
How it works
- Procedure
- Rules
SKILL.md preview
--- name: tracker description: Read, create and update tickets in whichever tracker the project uses (Linear, Jira, ClickUp, GitHub Issues, markdown files, or a custom one). Use whenever a task involves a ticket: reading its scope, creating one, moving its status, commenting. Never call tracker tools directly. --- # Tracker Single entry point to the project's ticket tracker. The contract and the rules are in `docs/TRACKERS.md` of the agent-team plugin; this file is the procedure. ## Procedure 1. Read `team/tracker.json` in the project. If it does not exist, use the `markdown` adapter (tickets as files in `team/state/tickets/`) and tell the user once that no tracker is configured. 2. Load the adapter file `adapters/<adapter>.md` from this skill's folder. For `custom`, use the `operations` mapping of the config. 3. Do the requested operation (`search`, `get`, `create`, `update`, `setStatus`, `comment`, `link`, `list`) with the adapter's instructions. Translate statuses, types and labels through the config maps. 4. Return the canonical result: `id`, `title`, `status`, `url`, plus what was changed. Never echo the full description or the raw tool response back into the conversation: they cost tokens on every later turn. ## Rules - `search` before `create`, to avoid duplicates. If a close match exists, show it and ask. - Create or edit a ticket only when the user asked for it or approved its text. - Write the description with the project's sections and language. Default sections: Context, To do, Out of scope, Acceptance criteria. Acceptance criteria must be verifiable. - Never put the ticket id in a branch name. It goes in the PR title. - If `autoDone` is true, do not set `done`: the tracker does it on merge. - If an operation is not available in this tracker, say so and use the fallback in the adapter file. Do not invent one silently. - If the tracker is unreachable: retry once, then stop and tell the user which operation failed. Never guess a ticket's state, never create a duplicate, never invent an id, never mark `done`. Offer the `markdown` fallback only with the user's approval. See `docs/TRACKERS.md`. - Never print tokens or secrets. Credentials come from the tool's own connection or environment variables. - Tool names differ between installations. If a tool named in an adapter is not available, search for the equivalent tool in the connected tools, and tell the user which one you used.
Files in this package (7)
- SKILL.md 2 KB
- adapters/clickup.md 1 KB
- adapters/custom.md 2 KB
- adapters/github-issues.md 1 KB
- adapters/jira.md 1 KB
- adapters/linear.md 1 KB
- adapters/markdown.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · lemramimel/agent-team | 90 | MIT |
| andriiklymiuk/corgi | 100 | MIT |
| zagware/tracker-plugins | 100 | MIT |
| zagware/tracker-plugins | 100 | MIT |
Database snapshot: 13.11.2026 · package version 1847cc538fe3 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90using-tracker
Use when the user mentions issues, tickets, tasks, epics, current work, sprint or cycle, backlog, creating or updating issues, or anything about task tracking and planning in any tracker (Linear, Jira, GitHub Issues, local files). Invoke BEFORE asking the user any question about… - 90dev10x:linear
Linear issue tracker operations via MCP tools. Get, create, update issues and list comments. Documentation-only skill — no scripts. TRIGGER when: performing CRUD operations on Linear issues, comments, or statuses. DO NOT TRIGGER when: using GitHub Issues or JIRA (use… - 90gsdt-tracker
Read and write the repo's tickets (ClickUp tasks, or whatever tracker the repo uses) from the shell with gsdt-tracker: read a ticket, comment, set status, create a ticket, edit its title/description/assignees/priority, or find tickets. Use whenever the user asks to look at,… - 100writing-tickets
Write or rewrite an issue tracker ticket (Linear, GitHub Issues, Jira, or similar) that a person or coding agent will pick up. States the objective, evidence, decisions already made, hard rules, and done criteria, and leaves the how to the implementer. Use when the user says… - 90dev10x:project-scope
Scope a multi-ticket project with milestones, blocking relationships, and tracker integration. Accepts a parent ticket URL/ID or free-text description and creates the full project structure in Linear, JIRA, or GitHub Issues. TRIGGER when: scoping a multi-ticket project with… - 100flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.