content-review
Review CircleCI documentation pages for quality, clarity, and adherence to style guidelines. Use this skill whenever the user asks to review, audit, or assess documentation content, check for style compliance, evaluate page quality, or wants feedback on docs pages. Also trigger when the user mentions content quality, readability issues, or asks "how does this page look" or "is this page good." Even if they just reference a docs file path and ask for a review or feedback, use this skill.
78
—
Does it follow best practices?
Impact
72%
1.04xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Security
2 findings — 2 medium severity. This skill can be installed but you should review these findings before use.
W011: Third-party content exposure detected (indirect prompt injection risk)
What this means
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.
Why it was flagged
Third-party content exposure detected (high risk: 0.85). The required workflow reads CircleCI documentation `.adoc` pages from the user-supplied file path (Step 1: “Read the target documentation page”), and those pages are outsider-authored content that becomes LLM-readable prose via the local file ingestion path.
W021: Hidden or invisible Unicode characters detected (potential obfuscation or prompt injection)
What this means
Detected hidden or invisible Unicode characters (Format/Cf or Control/Cc categories) in the component’s content. These characters are invisible when rendered but are still processed by AI models, and attackers use them to smuggle instructions past human review — for example, zero-width spaces, bidirectional overrides, invisible formatters, or Unicode Tag characters (U+E0000–U+E007F) that encode an entire hidden message. Severity escalates to high when three or more distinct hidden character types are present, or when a hidden tag-encoded message is successfully decoded, as these strongly indicate intentional obfuscation.
Why it was flagged
Hidden Unicode characters detected (1 type(s) found)
- Repository
- circleci/circleci-docs
- Commit
65ff472
- Audited
- Security analysis
Is this your skill?
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.