entity-optimizer

Use when the user asks to "optimize entity presence", "build knowledge graph", "improve knowledge panel", "entity audit", "establish brand entity", "Google does not know my brand", "no knowledge panel", or "establish my brand as an entity". Works standalone with public search and AI query testing; supercharged when you connect ~~knowledge graph + ~~SEO tool + ~~AI monitor for automated entity analysis. For structured data implementation, see schema-markup-generator. For content-level AI optimization, see geo-content-optimizer.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/entity-optimizer/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, well-structured audit skill with concrete templates, specific property references, and a worked example. It is held back by verbosity (conceptual padding and a promotional skill browser) and by reference-grade tables that belong in the bundled reference files rather than the main body.

Suggestions

Trim conceptual padding Claude already knows — the "Why entities matter for SEO + GEO" section and the Extract→Resolve→Retrieve→Generate AI pipeline — to lift conciseness.

Move the Wikidata property table and Knowledge Panel issue/fix table into references/knowledge-graph-guide.md, leaving a one-line pointer, so SKILL.md stays an overview.

Remove or collapse the promotional "Browse all 20 skills" details block; it is library navigation, not entity-optimization instruction.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational tables and templates, but padded with conceptual explanation Claude already knows ("Why entities matter for SEO + GEO", the Extract→Resolve→Retrieve→Generate AI pipeline) and a promotional browsable 20-skills list that earns no analytical value.	3 / 5
Actionability	Concrete fill-in templates, specific Wikidata property codes (P31, P856, P571, P17), and a fully worked CloudMetrics example make the guidance executable; some strategic items ("build notability through press coverage") remain high-level, keeping it just below 5.	4 / 5
Workflow Clarity	A clear 3-step sequence (Entity Discovery → Signal Audit → Report & Action Plan) is paired with Input/Output Validation checklists; it is a read-only audit so the destructive-cap does not apply, but there are no true error-recovery feedback loops.	4 / 5
Progressive Disclosure	Two real one-level-deep references (entity-signal-checklist.md, knowledge-graph-guide.md) are well-signaled, but heavy reference material (Wikidata property tables, Knowledge Panel issue/fix tables) is inlined in SKILL.md rather than split into the knowledge-graph guide.	4 / 5
	Total	15 / 20 Passed

Description

81%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, trigger-rich description with excellent natural keyword coverage and clear boundary-setting against sibling skills. Its main weakness is that the capability ("what") is implied via triggers and a tool note rather than stated as a crisp action list.

Dimension	Reasoning	Score
Specificity	Names the domain (entity presence / knowledge graph) and a couple concrete actions ("public search and AI query testing", "automated entity analysis"), but leans on trigger phrases rather than a comprehensive enumeration of what the skill does.	3 / 5
Completeness	The "when" is explicit via the "Use when the user asks to..." clause, but the "what" is only implied through triggers and a tool-integration note rather than crisply stated; not a 5 because the what is not clearly and explicitly declared.	4 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users would actually say — "optimize entity presence", "build knowledge graph", "improve knowledge panel", "Google does not know my brand", "no knowledge panel" — with synonyms and variations covered.	5 / 5
Distinctiveness Conflict Risk	Clear entity-optimization niche with distinct triggers, and explicit cross-references to sibling skills (schema-markup-generator for structured data, geo-content-optimizer for content-level AI optimization) minimize overlap and conflict.	5 / 5
	Total	17 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (522 lines); consider splitting into references/ and linking	Warning
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 30 suspicious	Warning

	Total	13 / 16 Passed

Repository: teeclaw/phorm-nft
Path: .agents/skills/entity-optimizer/SKILL.md
Commit: 02adecb

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.