Security audit
Security checks for vulnerabilities and agentic risk
This Markdown-only skill is coherent for entity and knowledge-graph optimization, with some adjacent GEO/page-content guidance that users should treat as advisory rather than automatic authority.
Before installing, expect this skill to inspect and potentially update an entity registry when you authorize it. Review any recommendations that involve people, About pages, social profiles, or public knowledge-base edits, and use the dedicated GEO/content skills for actual page-copy changes.
The file declares itself part of entity-optimizer while containing instructions that direct GEO-specific work, contradicting the manifest boundary. In an agent skill system, this kind of contradictory association is dangerous because it can misroute tasks, weaken safety boundaries between skills, and make the agent follow the wrong operational playbook.
This section expands the skill from entity-registry maintenance into page-level AI-citation readiness and content optimization, which the manifest explicitly says should be handled by a different skill. That scope drift can cause the agent to perform unintended actions, select the wrong workflow, or apply conflicting guidance, increasing the risk of unsafe or policy-inconsistent changes.
The manifest scopes the skill to optimizing entity presence through the entities registry and maintaining canonical KG facts, while excluding broader brand-canon and page-level readiness work. These lines advise claiming panels, updating About pages and social profiles, and managing cross-platform profile content, which extends beyond registry-focused entity reconciliation into broader profile/content operations.
The manifest explicitly says this skill is for machine-facing entity identity and knowledge graph maintenance, and specifically says it is not for page-level AI-citation readiness, which should use geo-content-optimizer instead. However, these lines recommend About-page wording, SEO for branded queries, topic-content associations, and content freshness tactics that are characteristic of page/content optimization rather than entity registry maintenance.
No suspicious patterns detected.
