Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation style guide skill with no executable code, persistence, credential access, or hidden runtime behavior.
This skill is reasonable to install if you want general documentation style guidance. Be aware that it may influence many documentation-writing or review tasks because its trigger is broad, so use more specific documentation skills when you need tutorial, how-to, reference, or explanation guidance.
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
Address the reader directly as "you" rather than "the user" or "developers."
<!-- Good -->
You can configure the API by setting environment variables.
<!-- Avoid -->
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
<!-- Good: Table for structured data -->
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| api_key | string | Yes | Your API key |
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
Orient documentation around user goals, not product features.
<!-- Good: User-goal oriented -->
# Send Emails
Send transactional emails to your users with delivery tracking.
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
Don't document self-explanatory UI actions.
<!-- Good: Meaningful instruction -->
Enter your webhook URL. The URL must use HTTPS and be publicly accessible.
<!-- Avoid: Obvious instruction -->
Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
Enter your webhook URL. The URL must use HTTPS and be publicly accessible.
Click in the text field. Type your webhook URL. Click the Save button.
The description says to use the skill when writing or reviewing "any documentation," which is very broad and lacks clear boundaries or exclusion conditions. For a markdown skill description, this can create ambiguity about when the skill should activate versus when more specific documentation skills should apply.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import requests
API_KEY = "your-api-key"
BASE_URL = "https://api.example.com/v1"
response = requests.get(
f"{BASE_URL}/users",