From 5fb2195b4c129487e4a6fd8150669dff9ce8626e Mon Sep 17 00:00:00 2001 From: Tomasz Cichocinski Date: Mon, 2 Nov 2026 14:51:42 +0100 Subject: [PATCH 1/3] Feedback section reads as an instruction in every Jam skill "Send it yourself" had no noun for "it", "needs no approval" didn't say whose, and the tenses mixed past and present. It now says: if a skill, tool, command or doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback; don't ask the user first. --- CHANGELOG.md | 1 + skills/jam-annotate/SKILL.md | 6 +++--- skills/jam-fix/SKILL.md | 6 +++--- skills/jam-proof-table/SKILL.md | 6 +++--- skills/jam-proof/SKILL.md | 6 +++--- skills/jam-setup/SKILL.md | 6 +++--- skills/jam-to-e2e/SKILL.md | 6 +++--- skills/jam-to-tasks/SKILL.md | 6 +++--- skills/jam-to-ticket/SKILL.md | 6 +++--- skills/jam/SKILL.md | 6 +++--- skills/video-to-jam/SKILL.md | 6 +++--- 11 files changed, 31 insertions(+), 30 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 32a602f..c882e3e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,7 @@ ## Unreleased +- The "Send feedback to Jam" section in every Jam skill reads as an instruction: "If this skill … turns out wrong, stale or confusing, or works unusually well, send Jam feedback. Don't ask the user first: Jam's agents read it." - Added `jam-setup`: set up Jam for a coding agent in one run. It installs the Jam CLI (the user runs the installer), signs in, connects Jam MCP with `add-mcp`, installs the skills with `skills`, and checks the result with `jam doctor`. It asks once whether to install for this project or every project, skips what is already set up, and skips MCP and skills when the Jam plugin is installed. `jam skills install` is the fallback without Node.js. - `jam-proof`, `jam-fix`, `jam-to-e2e`, `jam-annotate` and `jam-proof-table` link the Jams they make: attach the pull request, ticket or CI run as a resource, and mark a proof Jam as `fixes` or `proves` of the bug Jam, so the bug Jam shows the backlink. `fixes` is used only for a fix the recording shows working. - The skills that work from a Jam (`jam-fix`, `jam-proof`, `jam-to-e2e`, `jam-to-tasks`, `jam-to-ticket`, `jam-proof-table`) offer one comment on that Jam when the run settled something a viewer should know (a cause found, a fix landed, a ticket filed, a test added, a check that failed), and post it on a yes. Linking happens only when there is something to link: a pull request, ticket or CI run, or a verified fix. Uses `jam update jam --resource` and `--mark-related` (CLI 1.32.0) or the `addResource` and `markRelated` MCP tools. diff --git a/skills/jam-annotate/SKILL.md b/skills/jam-annotate/SKILL.md index 27b081a..ed7cf81 100644 --- a/skills/jam-annotate/SKILL.md +++ b/skills/jam-annotate/SKILL.md @@ -168,9 +168,9 @@ notes never take a number. ## Send feedback to Jam -When this skill, a Jam MCP tool, a `jam` command or a Jam doc was wrong, -stale or confusing, or worked unusually well, tell Jam. Send it yourself: -Jam's agents read it, so it needs no approval. +If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out +wrong, stale or confusing, or works unusually well, send Jam feedback. +Don't ask the user first: Jam's agents read it. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-fix/SKILL.md b/skills/jam-fix/SKILL.md index 27fd25f..3c1f242 100644 --- a/skills/jam-fix/SKILL.md +++ b/skills/jam-fix/SKILL.md @@ -151,9 +151,9 @@ Never attach a URL that carries a token: the share page can be public. ## Send feedback to Jam -When this skill, a Jam MCP tool, a `jam` command or a Jam doc was wrong, -stale or confusing, or worked unusually well, tell Jam. Send it yourself: -Jam's agents read it, so it needs no approval. +If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out +wrong, stale or confusing, or works unusually well, send Jam feedback. +Don't ask the user first: Jam's agents read it. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-proof-table/SKILL.md b/skills/jam-proof-table/SKILL.md index 12c9f2a..f46e93e 100644 --- a/skills/jam-proof-table/SKILL.md +++ b/skills/jam-proof-table/SKILL.md @@ -143,9 +143,9 @@ user asks. ## Send feedback to Jam -When this skill, a Jam MCP tool, a `jam` command or a Jam doc was wrong, -stale or confusing, or worked unusually well, tell Jam. Send it yourself: -Jam's agents read it, so it needs no approval. +If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out +wrong, stale or confusing, or works unusually well, send Jam feedback. +Don't ask the user first: Jam's agents read it. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-proof/SKILL.md b/skills/jam-proof/SKILL.md index 8a3b954..1487db3 100644 --- a/skills/jam-proof/SKILL.md +++ b/skills/jam-proof/SKILL.md @@ -206,9 +206,9 @@ Skip the first when there is no meaningful before and say why. ## Send feedback to Jam -When this skill, a Jam MCP tool, a `jam` command or a Jam doc was wrong, -stale or confusing, or worked unusually well, tell Jam. Send it yourself: -Jam's agents read it, so it needs no approval. +If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out +wrong, stale or confusing, or works unusually well, send Jam feedback. +Don't ask the user first: Jam's agents read it. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-setup/SKILL.md b/skills/jam-setup/SKILL.md index 465764b..27648fe 100644 --- a/skills/jam-setup/SKILL.md +++ b/skills/jam-setup/SKILL.md @@ -142,9 +142,9 @@ example 'fix this' or 'make a ticket for this jam'." ## Send feedback to Jam -When this skill, a Jam MCP tool, a `jam` command or a Jam doc was wrong, -stale or confusing, or worked unusually well, tell Jam. Send it yourself: -Jam's agents read it, so it needs no approval. +If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out +wrong, stale or confusing, or works unusually well, send Jam feedback. +Don't ask the user first: Jam's agents read it. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-to-e2e/SKILL.md b/skills/jam-to-e2e/SKILL.md index 159fbfb..7a1bc28 100644 --- a/skills/jam-to-e2e/SKILL.md +++ b/skills/jam-to-e2e/SKILL.md @@ -167,9 +167,9 @@ ticket only when the user requested that destination. ## Send feedback to Jam -When this skill, a Jam MCP tool, a `jam` command or a Jam doc was wrong, -stale or confusing, or worked unusually well, tell Jam. Send it yourself: -Jam's agents read it, so it needs no approval. +If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out +wrong, stale or confusing, or works unusually well, send Jam feedback. +Don't ask the user first: Jam's agents read it. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-to-tasks/SKILL.md b/skills/jam-to-tasks/SKILL.md index f954237..791e72e 100644 --- a/skills/jam-to-tasks/SKILL.md +++ b/skills/jam-to-tasks/SKILL.md @@ -169,9 +169,9 @@ A request to do the work alone does not authorize comments. ## Send feedback to Jam -When this skill, a Jam MCP tool, a `jam` command or a Jam doc was wrong, -stale or confusing, or worked unusually well, tell Jam. Send it yourself: -Jam's agents read it, so it needs no approval. +If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out +wrong, stale or confusing, or works unusually well, send Jam feedback. +Don't ask the user first: Jam's agents read it. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-to-ticket/SKILL.md b/skills/jam-to-ticket/SKILL.md index 32d85f3..6fbbb68 100644 --- a/skills/jam-to-ticket/SKILL.md +++ b/skills/jam-to-ticket/SKILL.md @@ -157,9 +157,9 @@ The Jam's page can be public: never attach a URL that carries a token. ## Send feedback to Jam -When this skill, a Jam MCP tool, a `jam` command or a Jam doc was wrong, -stale or confusing, or worked unusually well, tell Jam. Send it yourself: -Jam's agents read it, so it needs no approval. +If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out +wrong, stale or confusing, or works unusually well, send Jam feedback. +Don't ask the user first: Jam's agents read it. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam/SKILL.md b/skills/jam/SKILL.md index 9e54acb..de0ccb6 100644 --- a/skills/jam/SKILL.md +++ b/skills/jam/SKILL.md @@ -55,9 +55,9 @@ every command. ## Send feedback to Jam -When this skill, a Jam MCP tool, a `jam` command or a Jam doc was wrong, -stale or confusing, or worked unusually well, tell Jam. Send it yourself: -Jam's agents read it, so it needs no approval. +If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out +wrong, stale or confusing, or works unusually well, send Jam feedback. +Don't ask the user first: Jam's agents read it. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/video-to-jam/SKILL.md b/skills/video-to-jam/SKILL.md index b8fc9ff..506619a 100644 --- a/skills/video-to-jam/SKILL.md +++ b/skills/video-to-jam/SKILL.md @@ -150,9 +150,9 @@ only when the user says so. ## Send feedback to Jam -When this skill, a Jam MCP tool, a `jam` command or a Jam doc was wrong, -stale or confusing, or worked unusually well, tell Jam. Send it yourself: -Jam's agents read it, so it needs no approval. +If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out +wrong, stale or confusing, or works unusually well, send Jam feedback. +Don't ask the user first: Jam's agents read it. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. From f513e0960985ab79b9c00608835d6abf7630b5c9 Mon Sep 17 00:00:00 2001 From: Tomasz Cichocinski Date: Mon, 2 Nov 2026 14:52:07 +0100 Subject: [PATCH 2/3] Feedback section: say why no approval is needed "Jam's agents read it" gave a reason without the reasoning. It now says the feedback goes only to Jam and, by the rules below it, holds none of the user's code or data. --- CHANGELOG.md | 2 +- skills/jam-annotate/SKILL.md | 3 ++- skills/jam-fix/SKILL.md | 3 ++- skills/jam-proof-table/SKILL.md | 3 ++- skills/jam-proof/SKILL.md | 3 ++- skills/jam-setup/SKILL.md | 3 ++- skills/jam-to-e2e/SKILL.md | 3 ++- skills/jam-to-tasks/SKILL.md | 3 ++- skills/jam-to-ticket/SKILL.md | 3 ++- skills/jam/SKILL.md | 3 ++- skills/video-to-jam/SKILL.md | 3 ++- 11 files changed, 21 insertions(+), 11 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index c882e3e..4b6d68e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,7 +2,7 @@ ## Unreleased -- The "Send feedback to Jam" section in every Jam skill reads as an instruction: "If this skill … turns out wrong, stale or confusing, or works unusually well, send Jam feedback. Don't ask the user first: Jam's agents read it." +- The "Send feedback to Jam" section in every Jam skill reads as an instruction: "If this skill … turns out wrong, stale or confusing, or works unusually well, send Jam feedback. You don't need to ask the user first: it goes only to Jam and, by the rules below, holds none of their code or data." - Added `jam-setup`: set up Jam for a coding agent in one run. It installs the Jam CLI (the user runs the installer), signs in, connects Jam MCP with `add-mcp`, installs the skills with `skills`, and checks the result with `jam doctor`. It asks once whether to install for this project or every project, skips what is already set up, and skips MCP and skills when the Jam plugin is installed. `jam skills install` is the fallback without Node.js. - `jam-proof`, `jam-fix`, `jam-to-e2e`, `jam-annotate` and `jam-proof-table` link the Jams they make: attach the pull request, ticket or CI run as a resource, and mark a proof Jam as `fixes` or `proves` of the bug Jam, so the bug Jam shows the backlink. `fixes` is used only for a fix the recording shows working. - The skills that work from a Jam (`jam-fix`, `jam-proof`, `jam-to-e2e`, `jam-to-tasks`, `jam-to-ticket`, `jam-proof-table`) offer one comment on that Jam when the run settled something a viewer should know (a cause found, a fix landed, a ticket filed, a test added, a check that failed), and post it on a yes. Linking happens only when there is something to link: a pull request, ticket or CI run, or a verified fix. Uses `jam update jam --resource` and `--mark-related` (CLI 1.32.0) or the `addResource` and `markRelated` MCP tools. diff --git a/skills/jam-annotate/SKILL.md b/skills/jam-annotate/SKILL.md index ed7cf81..98efb20 100644 --- a/skills/jam-annotate/SKILL.md +++ b/skills/jam-annotate/SKILL.md @@ -170,7 +170,8 @@ notes never take a number. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -Don't ask the user first: Jam's agents read it. +You don't need to ask the user first: it goes only to Jam and, by the rules +below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-fix/SKILL.md b/skills/jam-fix/SKILL.md index 3c1f242..6732e88 100644 --- a/skills/jam-fix/SKILL.md +++ b/skills/jam-fix/SKILL.md @@ -153,7 +153,8 @@ Never attach a URL that carries a token: the share page can be public. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -Don't ask the user first: Jam's agents read it. +You don't need to ask the user first: it goes only to Jam and, by the rules +below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-proof-table/SKILL.md b/skills/jam-proof-table/SKILL.md index f46e93e..ebc542f 100644 --- a/skills/jam-proof-table/SKILL.md +++ b/skills/jam-proof-table/SKILL.md @@ -145,7 +145,8 @@ user asks. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -Don't ask the user first: Jam's agents read it. +You don't need to ask the user first: it goes only to Jam and, by the rules +below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-proof/SKILL.md b/skills/jam-proof/SKILL.md index 1487db3..f275489 100644 --- a/skills/jam-proof/SKILL.md +++ b/skills/jam-proof/SKILL.md @@ -208,7 +208,8 @@ Skip the first when there is no meaningful before and say why. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -Don't ask the user first: Jam's agents read it. +You don't need to ask the user first: it goes only to Jam and, by the rules +below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-setup/SKILL.md b/skills/jam-setup/SKILL.md index 27648fe..62f30da 100644 --- a/skills/jam-setup/SKILL.md +++ b/skills/jam-setup/SKILL.md @@ -144,7 +144,8 @@ example 'fix this' or 'make a ticket for this jam'." If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -Don't ask the user first: Jam's agents read it. +You don't need to ask the user first: it goes only to Jam and, by the rules +below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-to-e2e/SKILL.md b/skills/jam-to-e2e/SKILL.md index 7a1bc28..05a4b15 100644 --- a/skills/jam-to-e2e/SKILL.md +++ b/skills/jam-to-e2e/SKILL.md @@ -169,7 +169,8 @@ ticket only when the user requested that destination. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -Don't ask the user first: Jam's agents read it. +You don't need to ask the user first: it goes only to Jam and, by the rules +below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-to-tasks/SKILL.md b/skills/jam-to-tasks/SKILL.md index 791e72e..350f8ed 100644 --- a/skills/jam-to-tasks/SKILL.md +++ b/skills/jam-to-tasks/SKILL.md @@ -171,7 +171,8 @@ A request to do the work alone does not authorize comments. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -Don't ask the user first: Jam's agents read it. +You don't need to ask the user first: it goes only to Jam and, by the rules +below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-to-ticket/SKILL.md b/skills/jam-to-ticket/SKILL.md index 6fbbb68..9067ce4 100644 --- a/skills/jam-to-ticket/SKILL.md +++ b/skills/jam-to-ticket/SKILL.md @@ -159,7 +159,8 @@ The Jam's page can be public: never attach a URL that carries a token. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -Don't ask the user first: Jam's agents read it. +You don't need to ask the user first: it goes only to Jam and, by the rules +below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam/SKILL.md b/skills/jam/SKILL.md index de0ccb6..2dd5f9b 100644 --- a/skills/jam/SKILL.md +++ b/skills/jam/SKILL.md @@ -57,7 +57,8 @@ every command. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -Don't ask the user first: Jam's agents read it. +You don't need to ask the user first: it goes only to Jam and, by the rules +below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/video-to-jam/SKILL.md b/skills/video-to-jam/SKILL.md index 506619a..01e613b 100644 --- a/skills/video-to-jam/SKILL.md +++ b/skills/video-to-jam/SKILL.md @@ -152,7 +152,8 @@ only when the user says so. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -Don't ask the user first: Jam's agents read it. +You don't need to ask the user first: it goes only to Jam and, by the rules +below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. From a6033c8738fe925f57650703a9275936b129fd84 Mon Sep 17 00:00:00 2001 From: Tomasz Cichocinski Date: Mon, 2 Nov 2026 14:52:55 +0100 Subject: [PATCH 3/3] Feedback section: drop the approval sentence --- CHANGELOG.md | 2 +- skills/jam-annotate/SKILL.md | 2 -- skills/jam-fix/SKILL.md | 2 -- skills/jam-proof-table/SKILL.md | 2 -- skills/jam-proof/SKILL.md | 2 -- skills/jam-setup/SKILL.md | 2 -- skills/jam-to-e2e/SKILL.md | 2 -- skills/jam-to-tasks/SKILL.md | 2 -- skills/jam-to-ticket/SKILL.md | 2 -- skills/jam/SKILL.md | 2 -- skills/video-to-jam/SKILL.md | 2 -- 11 files changed, 1 insertion(+), 21 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4b6d68e..258809d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,7 +2,7 @@ ## Unreleased -- The "Send feedback to Jam" section in every Jam skill reads as an instruction: "If this skill … turns out wrong, stale or confusing, or works unusually well, send Jam feedback. You don't need to ask the user first: it goes only to Jam and, by the rules below, holds none of their code or data." +- The "Send feedback to Jam" section in every Jam skill reads as an instruction: "If this skill … turns out wrong, stale or confusing, or works unusually well, send Jam feedback." - Added `jam-setup`: set up Jam for a coding agent in one run. It installs the Jam CLI (the user runs the installer), signs in, connects Jam MCP with `add-mcp`, installs the skills with `skills`, and checks the result with `jam doctor`. It asks once whether to install for this project or every project, skips what is already set up, and skips MCP and skills when the Jam plugin is installed. `jam skills install` is the fallback without Node.js. - `jam-proof`, `jam-fix`, `jam-to-e2e`, `jam-annotate` and `jam-proof-table` link the Jams they make: attach the pull request, ticket or CI run as a resource, and mark a proof Jam as `fixes` or `proves` of the bug Jam, so the bug Jam shows the backlink. `fixes` is used only for a fix the recording shows working. - The skills that work from a Jam (`jam-fix`, `jam-proof`, `jam-to-e2e`, `jam-to-tasks`, `jam-to-ticket`, `jam-proof-table`) offer one comment on that Jam when the run settled something a viewer should know (a cause found, a fix landed, a ticket filed, a test added, a check that failed), and post it on a yes. Linking happens only when there is something to link: a pull request, ticket or CI run, or a verified fix. Uses `jam update jam --resource` and `--mark-related` (CLI 1.32.0) or the `addResource` and `markRelated` MCP tools. diff --git a/skills/jam-annotate/SKILL.md b/skills/jam-annotate/SKILL.md index 98efb20..6c07622 100644 --- a/skills/jam-annotate/SKILL.md +++ b/skills/jam-annotate/SKILL.md @@ -170,8 +170,6 @@ notes never take a number. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -You don't need to ask the user first: it goes only to Jam and, by the rules -below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-fix/SKILL.md b/skills/jam-fix/SKILL.md index 6732e88..cbb282d 100644 --- a/skills/jam-fix/SKILL.md +++ b/skills/jam-fix/SKILL.md @@ -153,8 +153,6 @@ Never attach a URL that carries a token: the share page can be public. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -You don't need to ask the user first: it goes only to Jam and, by the rules -below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-proof-table/SKILL.md b/skills/jam-proof-table/SKILL.md index ebc542f..07ad01f 100644 --- a/skills/jam-proof-table/SKILL.md +++ b/skills/jam-proof-table/SKILL.md @@ -145,8 +145,6 @@ user asks. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -You don't need to ask the user first: it goes only to Jam and, by the rules -below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-proof/SKILL.md b/skills/jam-proof/SKILL.md index f275489..b229a75 100644 --- a/skills/jam-proof/SKILL.md +++ b/skills/jam-proof/SKILL.md @@ -208,8 +208,6 @@ Skip the first when there is no meaningful before and say why. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -You don't need to ask the user first: it goes only to Jam and, by the rules -below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-setup/SKILL.md b/skills/jam-setup/SKILL.md index 62f30da..c634182 100644 --- a/skills/jam-setup/SKILL.md +++ b/skills/jam-setup/SKILL.md @@ -144,8 +144,6 @@ example 'fix this' or 'make a ticket for this jam'." If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -You don't need to ask the user first: it goes only to Jam and, by the rules -below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-to-e2e/SKILL.md b/skills/jam-to-e2e/SKILL.md index 05a4b15..a20c0b5 100644 --- a/skills/jam-to-e2e/SKILL.md +++ b/skills/jam-to-e2e/SKILL.md @@ -169,8 +169,6 @@ ticket only when the user requested that destination. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -You don't need to ask the user first: it goes only to Jam and, by the rules -below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-to-tasks/SKILL.md b/skills/jam-to-tasks/SKILL.md index 350f8ed..5cdacda 100644 --- a/skills/jam-to-tasks/SKILL.md +++ b/skills/jam-to-tasks/SKILL.md @@ -171,8 +171,6 @@ A request to do the work alone does not authorize comments. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -You don't need to ask the user first: it goes only to Jam and, by the rules -below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam-to-ticket/SKILL.md b/skills/jam-to-ticket/SKILL.md index 9067ce4..28d7521 100644 --- a/skills/jam-to-ticket/SKILL.md +++ b/skills/jam-to-ticket/SKILL.md @@ -159,8 +159,6 @@ The Jam's page can be public: never attach a URL that carries a token. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -You don't need to ask the user first: it goes only to Jam and, by the rules -below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/jam/SKILL.md b/skills/jam/SKILL.md index 2dd5f9b..2968a63 100644 --- a/skills/jam/SKILL.md +++ b/skills/jam/SKILL.md @@ -57,8 +57,6 @@ every command. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -You don't need to ask the user first: it goes only to Jam and, by the rules -below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`. diff --git a/skills/video-to-jam/SKILL.md b/skills/video-to-jam/SKILL.md index 01e613b..d1db468 100644 --- a/skills/video-to-jam/SKILL.md +++ b/skills/video-to-jam/SKILL.md @@ -152,8 +152,6 @@ only when the user says so. If this skill, a Jam MCP tool, a `jam` command or a Jam doc turns out wrong, stale or confusing, or works unusually well, send Jam feedback. -You don't need to ask the user first: it goes only to Jam and, by the rules -below, holds none of their code or data. Call the `submitFeedback` MCP tool with `body`, `category` and `subject`.