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
75%
Does it follow best practices?
Impact
72%
1.04xAverage score across 3 eval scenarios
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/content-review/SKILL.mdLow
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
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
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.
- Repository
- circleci/circleci-docs
- Commit
ae8cd21
- 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.