[devin-ai-integration]

Summary

New record-link-jam skill. An agent that has a browser and the Jam MCP, with no Jam CLI installed, can record a Jam itself:

listRecordingUrls → createRecordingLink({name, jamTitle, reference, expiresAt, recordingUrlId})
→ open returned url in the browser → Start Recording → Chrome share picker: Entire Screen → Share
→ do the work → Stop → "Anything to add?" → Submit
→ listRecordingLinkJams({publicId}) → getDetails({jamId}) → deleteRecordingLink({publicId})

• Fallback A, no browser or no access to the native picker: send the link to a human and poll listRecordingLinkJams with bounded backoff (at most 10 minutes).
• Fallback B, CLI: the equivalent jam recording-links … commands live in references/cli.md.
• Added to the ChatGPT package SKILLS list (MCP-only), the README card, the jam router and the CHANGELOG.

Behavior verified on production:

• A Jam's origin is recording_link and its author is the link owner.
• The "Anything to add?" text becomes the first comment, and the description stays empty.
• A connected-domain URL looks like https://<domain>/?jam-recording=<publicId>. Without a connected domain it is https://recorder.jam.dev/<publicId>.
• Deleting the link keeps its Jams.

Caveat: Chrome's share picker is browser UI, so Playwright/CDP page control can't click it. The skill calls for a desktop click, or describes --auto-select-desktop-capture-source as an untested option.

Proof of work

• MCP-only run (no CLI): the agent created the link over MCP, recorded it in its own browser, then read it back over MCP: https://jam.dev/c/1f061df4-949f-48c4-b6c7-6d7370b99554
• CLI-created links recorded in the browser: https://jam.dev/c/c7ba2b68-0a4f-486e-826d-ed1c37f1be93 (plain) and https://jam.dev/c/db10f43d-94a1-4b7d-95fc-f7cc75718ab0 (connected domain)
• All test links were deleted afterwards. Console and network capture is still unconfirmed, because the test page logged nothing.

npm ci && node scripts/check.mjs && npm test: 14 skills, 36/36 tests pass. npx skills add . --list lists record-link-jam.

Link to Devin session: https://app.devin.ai/sessions/2eedee53ca274174b560ed4a9db08151
Open in Devin Desktop: https://app.devin.ai/desktop/session/2eedee53ca274174b560ed4a9db08151?variant=devin
Requested by: @baransu

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

---

Original prompt from Tomasz

SYSTEM:
<latest_message>
Tomasz Cichociński (U01BES75X1S) [ts=1793665194.657229]: @Devin let’s experiment with creating jams from cli via recording links created by agents, try to cook a skills for jamdotdev/skills and verify it’s working e2e, draft PR
</latest_message>

=== BEGIN THREAD HISTORY ===
Tomasz Cichociński (U01BES75X1S) [ts=1793665194.657229]: @Devin let’s experiment with creating jams from cli via recording links created by agents, try to cook a skills for jamdotdev/skills and verify it’s working e2e, draft PR
=== END THREAD HISTORY ===
Channel ID: D0BSMNRED43
Thread URL: https://bwf4521.slack.com/archives/D0BSMNRED43/p1793665194657229?thread_ts=1793665194.657229&amp;cid=D0BSMNRED43

The <latest_message> is the message that you should use to guide your goals + task for this session, and you should use the rest of the slack thread as context.
A [ts=...] marker on a Slack message is that message's timestamp. To act on a specific message with the slack tool (e.g. adding an emoji reaction via the reaction command), pass that value as timestamp along with the Channel ID — no extra lookup call is needed.