Affected Skill
devtools/android-cli, performance/r8-analyzer
Description
Several code examples in these two skills are broken in the raw markdown, which is what an agent reads. Some of them no longer work when copied.
android-cli, since the 2026-09-15 update:
- SKILL.md#L33-L36: the install commands contain
\| and \&\&, and the Windows paths became %TEMP%\\i.cmd. Run as written, curl -fsSL .../install.sh \| bash passes | and bash to curl as extra URLs, and nothing gets installed:
curl: (6) Could not resolve host: |
curl: (6) Could not resolve host: bash
- interact.md#L77-L83, journeys.md#L3-L16 and journeys.md#L49-L50: fenced blocks became single-backtick spans (
`json, `xml), so they render inline, and the journey XML lost its indentation.
r8-analyzer, references/REFLECTION-GUIDE.md, throughout the file:
- The fences are either backslash-escaped (
\`\`\`proguard or \`\`\`kotlin at L18, L35, L54, L68, L93, L129) or reduced to single backticks (L13, L29, L50, L75, L88, L109, L117), so none of the examples render as code blocks.
- L20-L21 and L39-L40:
<init> is missing from the keep rules, which read -keep class \* implements com.example.library.StartupTask { (); } instead of { <init>(); }.
- L54: the rule is on the same line as its comment,
# Keep the annotation itself -keep @interface com.example.library.ReflectiveExecutor, so the -keep becomes part of the comment when copied. L68 puts the start of the Kotlin example on the label line the same way, and L136-L139 runs # No manual rule needed into the note text.
- Wildcards and comment markers are backslash-escaped (
class \*, /\* skip feature \*/), so copied rules keep the backslashes.
Separately, section 3 describes the rules incorrectly. The comment at L56 says "Keep members of any class annotated with this specific annotation", but the rule at L57-L59 keeps the annotated members of any class. The rules also leave out -keepattributes RuntimeVisibleAnnotations, which the keep rule examples include for the same pattern so the annotation can be read at runtime.
Expected Behavior
Install commands and keep rules keep valid syntax when copied, and code examples render as code blocks.
Actual Behavior
The install commands and keep rules fail or change meaning when copied, and the code examples render as inline text.
Steps to Reproduce
Open the raw files at the linked lines.
Suggested Fix
Restore the fences, the plain |, && and *, the single \ in the Windows paths, and <init>(); in the keep rules. In section 3, fix the comment and add -keepattributes RuntimeVisibleAnnotations.
Affected Skill
devtools/android-cli,performance/r8-analyzerDescription
Several code examples in these two skills are broken in the raw markdown, which is what an agent reads. Some of them no longer work when copied.
android-cli, since the 2026-09-15 update:\|and\&\&, and the Windows paths became%TEMP%\\i.cmd. Run as written,curl -fsSL .../install.sh \| bashpasses|andbashto curl as extra URLs, and nothing gets installed:`json,`xml), so they render inline, and the journey XML lost its indentation.r8-analyzer, references/REFLECTION-GUIDE.md, throughout the file:\`\`\`proguardor\`\`\`kotlinat L18, L35, L54, L68, L93, L129) or reduced to single backticks (L13, L29, L50, L75, L88, L109, L117), so none of the examples render as code blocks.<init>is missing from the keep rules, which read-keep class \* implements com.example.library.StartupTask { (); }instead of{ <init>(); }.# Keep the annotation itself -keep @interface com.example.library.ReflectiveExecutor, so the-keepbecomes part of the comment when copied. L68 puts the start of the Kotlin example on the label line the same way, and L136-L139 runs# No manual rule neededinto the note text.class \*,/\* skip feature \*/), so copied rules keep the backslashes.Separately, section 3 describes the rules incorrectly. The comment at L56 says "Keep members of any class annotated with this specific annotation", but the rule at L57-L59 keeps the annotated members of any class. The rules also leave out
-keepattributes RuntimeVisibleAnnotations, which the keep rule examples include for the same pattern so the annotation can be read at runtime.Expected Behavior
Install commands and keep rules keep valid syntax when copied, and code examples render as code blocks.
Actual Behavior
The install commands and keep rules fail or change meaning when copied, and the code examples render as inline text.
Steps to Reproduce
Open the raw files at the linked lines.
Suggested Fix
Restore the fences, the plain
|,&&and*, the single\in the Windows paths, and<init>();in the keep rules. In section 3, fix the comment and add-keepattributes RuntimeVisibleAnnotations.