From 37a1b532c862012b31860ac5ae3cb3fe6b88d475 Mon Sep 17 00:00:00 2001 From: Mark Martynenka Date: Thu, 27 Aug 2026 01:54:08 +0200 Subject: [PATCH] fix: stop replying with the dead by-key task link MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The task-creation skill told the agent to answer with /#/issues/, a path the app resolves to nothing — bridgeapp-links and the route map already warn about it. The reply now carries /#/projects//board/, the same shape the app's own Copy-link action produces. --- plugins/bridgeapp/skills/bridgeapp-task-creation/SKILL.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/plugins/bridgeapp/skills/bridgeapp-task-creation/SKILL.md b/plugins/bridgeapp/skills/bridgeapp-task-creation/SKILL.md index fc4ca52..8d20fa0 100644 --- a/plugins/bridgeapp/skills/bridgeapp-task-creation/SKILL.md +++ b/plugins/bridgeapp/skills/bridgeapp-task-creation/SKILL.md @@ -47,12 +47,14 @@ user the task key, its title, and a URL they can open: ``` DEV-1234 — Fix the token exchange returning null -https:///#/issues/DEV-1234 +https:///#/projects//board/ ``` +`` is the project you created the task in and `` comes from +the create result — a task link always carries both; there is no by-key URL. Build `` from a link you were already given rather than assuming one — the workspace may be self-hosted on a domain of its own. The -`bridgeapp-links` skill has the rule. +`bridgeapp-links` skill has the rule and the full route map. That is the whole reply. No summary of the fields you filled, no offer to do more, no closing question. The user asked for a task; the task exists; the link