Security audit
Security checks for vulnerabilities and agentic risk
This is a coherent SEO and AI-visibility audit template with optional public web/search checks and no executable or persistent behavior.
Use this skill for website SEO/GEO audits. Expect it to inspect public pages and, if you configure SERPAPI_API_KEY, enrich findings with search-result data; do not provide private analytics or Search Console data unless you intend that extra context to be used.
Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.
- `Operator mode`
- `Specialist mode`
## Output Rules
- If the user writes in Chinese, answer in Chinese unless asked otherwise.
- Always begin with a short executive summary.
The description says to use the skill when the user asks for a "full SEO audit" or "wants one prioritized report," which are broad formulations that may overlap with many general website-review requests. It does not provide exclusion conditions or negative examples to distinguish this skill from other audit or analysis skills.
The language rules specify '优先中文' and further constrain terminology style, which creates a locale preference in the skill instructions. Under the policy, forcing or defaulting to a specific language without offering user choice can be a natural-language policy violation unless clearly justified as region-specific.
The prompt example 'Give me an operator-style SEO GEO audit with P0, P1, and P2 actions' is phrased as a general request and does not require a URL, target scope, or explicit invocation boundary. In a manifest or README, this kind of broad example can contribute to ambiguous activation because it is unclear when a generic 'audit' request should invoke this specific skill versus other analysis skills.
The example 'Review this site for AI visibility, EEAT, and entity clarity' is descriptive but still broad enough to resemble ordinary consultation language. The README does not pair these examples with negative examples or explicit boundaries clarifying when this skill should or should not be selected.
The example phrase "Audit this homepage in boss mode" uses informal wording that does not itself identify the SEO/GEO domain and could collide with unrelated audit contexts. Because it is presented as a start phrase without accompanying limits, it weakens trigger specificity.
No suspicious patterns detected.