Repository navigation
docs(skill): Tell agents to read any page as Markdown with the Accept header - #124
Conversation
|
|
@deanzaka Impact of this PR. It adds one line to the source of the agent skill, the same line that taskade/taskcade#33591 adds to the served copy.
|
There was a problem hiding this comment.
🟢 Approval recommended
The review identified no active issues in the sole changed file, which clearly documents requesting normal Taskade pages as Markdown with the appropriate header.
No open issues 🎉
What changed in this PR
Updates the Taskade agent skill to explain how agents can request normal Taskade pages as Markdown using the Accept: text/markdown header.
Changes:
- Added an “Any page as Markdown” instruction under “Learn more.”
- Included a
curlexample usingAccept: text/markdown. - Clarified that agents should use normal page URLs instead of guessing
.mdpaths.
| File | Description |
|---|---|
skills/taskade/SKILL.md |
Documents how agents can request normal Taskade page URLs as Markdown. |
Review effort: Lite
Why
This file is the source of the agent skill that taskcade serves at
https://www.taskade.com/SKILL.md(src/backend/concerns/mcp/agentSkillText.ts, which copies this file exactly). taskade/taskcade#33591 adds one line to the served copy. This PR adds the same line here, so the next copy keeps it.Cloudflare Markdown for Agents is on for the
taskade.comzone (settingcontent_converter). Any page answers anAccept: text/markdownrequest withContent-Type: text/markdown, for example/pricing,/appsand/learn/account/free-plan./llms.txtstaystext/plain.Change
One bullet under "Learn more", after the
llms.txtline. The text is the same as in taskade/taskcade#33591:Before / after (agent flow)
Note: #120 (open) also edits
skills/taskade/SKILL.md. Its hunks are in other sections, so the two PRs do not conflict.