Apply pending @slide-comment markers written by the open-slide inspector tool. Use when the user asks to "apply comments", "process slide comments", "apply the inspector comments", or references markers left inside `slides/<id>/index.tsx`.
80
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Security
1 high severity finding. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill requires decoding base64url marker contents and using them to make edits and a reported summary (plus suggests running node to inspect payloads), which can force the LLM to include decoded marker text verbatim in edits or output and thus risk exposing any secrets embedded in those markers.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The workflow requires scanning `slides/<slideId>/index.tsx` for `/* @slide-comment ... text="...""" markers` and then base64url-decoding that `text` and `JSON.parse`-ing it into `{ note, hint }`, so outsider-authored free text can flow into the LLM via the slide files’ embedded comments at runtime.
35dc46c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.