菜单
Use this skill when cleaning up an Asana task or project description, or when html_notes fails with "XML is invalid".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/cyberuni/cyber-asana --skill improve-description命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | improve-description |
| description | Use this skill when cleaning up an Asana task or project description, or when html_notes fails with "XML is invalid". |
Asana API error: XML is invalid (or Rich text should be wrapped in <body> tag).Plain prose with no formatting needs no HTML — use --notes / notes instead.
cyber-asana task get <gid> --json
Always edit from html_notes. task get and asana_task_get return it unconditionally — an empty description comes back as <body></body>, never absent — so there is no case where you need the plain-text notes projection, which drops every link and list.
The default is a copy-edit, not a rewrite. Preserve the author's message, wording, and structure. The result should read as the same person's text with the noise removed.
Do:
- and others *, a heading that lost its marker.<ul>/<ol>.Do not, unless asked:
If the text is genuinely unclear, keep the author's words and ask rather than guessing at the intent.
Report what you changed before applying it, so the author can see that the meaning survived.
Only when the user asks for them, in the same request or a follow-up. Each is opt-in and composable:
| Ask | Do |
|---|---|
| "add emoji" / "make it scannable" | Prefix each heading with one emoji matching the section. One per heading, never mid-sentence. |
| "use the PRD / bug / research template" | Load the template reference, then restructure into the matching skeleton, mapping existing content into sections and leaving absent sections out. |
| "make it more formal / friendlier / terser" | Rewrite for tone. This is the one case where wording changes are the point. |
| "back up the claims" / "add sources" | Research the assertions, then add <a href="..."> citations. Never cite a source you did not read. Flag any claim you could not support instead of quietly dropping it. |
A template modifier is the only reason to add or reorder sections. When it moves content, move it — do not paraphrase it on the way.
Wrap the whole document in a bare <body> — required, and it must carry no attributes.
cyber-asana task update <gid> --html-notes '<body><h1>Summary</h1>Ship the thing.</body>'
MCP: pass html_notes to asana_task_create / asana_task_update (or asana_project_update). --notes and --html-notes are mutually exclusive; the same holds for notes and html_notes.
Read the task back afterward — Asana normalizes on save (<b>→<strong>, <span> stripped to text, list attributes dropped), so what you sent is not always what is stored.
Verified against the live Asana API (PUT /tasks/{gid}, 2026-08).
Supported
| Tag | Notes |
|---|---|
<body> | Required outermost wrapper, no attributes |
<h1> <h2> <h3> | Headings — <h4>–<h6> are rejected |
<strong> <em> <u> <s> | <b> → <strong>, <i> → <em> on save |
<code> | Inline code |
<pre> | Code block; data-language attribute is kept |
<ul> <ol> <li> | Nesting allowed, including <ol> inside <ul> |
<a href="..."> | href (or data-asana-gid) required; absolute URL only |
<blockquote> | Multi-line allowed |
<table> <tr> <td> | <th> is rejected — use <td> for the header row |
<hr> | Normalized to <hr /> |
<mark> | Highlight; Asana injects its own color attributes |
Rejected — these are what produce XML is invalid
<p> · <br> · <div> · <h4>–<h6> · <img> · <del> · <sub> · <sup> · <th> · <li> outside a list
<span> is accepted but silently stripped to its text.
<pre><code> nested together fails with an opaque "unexpected error occurred" — use <pre> alone.
There is no <p> and no <br>. Separate blocks with real newline characters inside <body>; Asana preserves them. A cleanup pass therefore collapses runs of blank lines rather than deleting them.
<body><h1>Summary</h1>
First paragraph.
Second paragraph.</body>
Passing html_notes via MCP avoids shell quoting entirely and is the safer path for multi-line content. From a POSIX shell, use a quoted heredoc so the newlines survive:
cyber-asana task update <gid> --html-notes "$(cat <<'HTML'
<body><h1>Summary</h1>
Ship the thing.
</body>
HTML
)"
<, > in textA raw < or > outside a tag is rejected with Malformed rich text. Found < or > that was not part of tag. Escape them as < / > everywhere — including inside <code> and <pre>, which do not suppress parsing.
<body><pre><h2>Title</h2></pre></body>
& may be written raw; Asana normalizes it to &, in text and in href alike. Every tag must be closed — an unclosed <strong> is rejected.
| Markdown | Asana |
|---|---|
# H1 / ## H2 / ### H3 | <h1> / <h2> / <h3> |
#### H4 and deeper | Flatten to <h3>, or <strong> on its own line |
| Paragraph break | Blank line (literal newline), never <p> |
**bold** / *italic* | <strong> / <em> |
`code` | <code> |
```ts ... ``` | <pre data-language="typescript">…</pre>, contents escaped |
- item / 1. item | <ul><li>…</li></ul> / <ol><li>…</li></ol> |
[text](url) | <a href="url">text</a> — absolute URL only |
> quote | <blockquote> |
--- | <hr /> |
- [ ] todo | <ul><li>☐ todo</li></ul> — checklist markup is stripped |
A rejected update writes nothing — the stored description is left byte-identical. Fix the HTML and retry; there is nothing to recover.
| Error | Cause |
|---|---|
Rich text should be wrapped in <body> tag. | Missing <body>, or <body> carries an attribute |
XML is invalid | An unsupported tag — check <p>, <br>, <div>, <h4>+, <img> |
XML is invalid: Malformed rich text. Found < or > that was not part of tag. | Unescaped < or > in text |
XML is invalid: Malformed rich text. XML tag was not closed. | Unclosed tag |
One of data-asana-gid or href is required in anchor attributes | <a> with no href |
invalid protocol in HREF field | Relative or non-http(s) href |
Oops! An unexpected error occurred… | <code> nested inside <pre> |
references/templates.md — PRD, research-note, and bug-report skeletons. Load only when the user asks for a named template (step 3).