Draft and apply TRS ticket resolutions after user approval.
npx skills add https://github.com/leomleao/tct-cowork-plugin --skill resolve-leomleao
Please help me install this Agent Skill. Skill: resolve Source: https://github.com/leomleao/tct-cowork-plugin/tree/main/plugins/assistant/skills/resolve Command: npx skills add https://github.com/leomleao/tct-cowork-plugin --skill resolve-leomleao
Acting on behalf of a TCT consultant, this skill writes and applies well-structured resolutions to TRS tickets by inferring the most appropriate category from context and drafting concise, professional text for final submission. It ensures consistency with ticket history and prior discussions, and automates application via the TRS MCP tooling after user confirmation.
Fetch the ticket context for the provided TICKET_ID, infer the resolution category, draft the resolution text, and apply it after user confirmation.
High-intent search queries and answers about installing and using this skill.
To automate TRS ticket resolution, the skill fetches ticket context, infers the correct category, and drafts a 2–4 sentence professional resolution. It applies this text via the edit_resolution tool only after receiving explicit user approval.
Applying a formal TRS ticket resolution requires fetching ticket data, selecting a predefined category, and drafting a 2–4 sentence description of the issue and actions taken. The resolution is applied via the edit_resolution tool only after explicit user confirmation.
No, the TRS ticket resolution system never applies changes without explicit user approval. It drafts the text and category inference for review, requiring explicit confirmation before executing the edit_resolution tool to modify the ticket.
Yes, you can use existing session notes when drafting a TRS ticket resolution. The system optionally uses existing context and prior session notes alongside fetched ticket data to infer the category and draft the description.
A TRS ticket resolution description should be a concise 2–4 sentence text covering the issue, actions taken, and expected outcome. It must be consistent with ticket history and prior discussions to ensure professional final submission.
kvnxiaoCreate per-ticket git worktrees and generate GitHub PRs for Linear tickets.
endlessblinkSave in-progress work and push updates to a remote repository.
cshyangCoordinates a structured stakeholder discussion to align scope and decisions.
lucasfthQuantize machine learning models to GGUF format using llama.cpp.
