entity-optimizer

Build entity presence in Knowledge Graph, Wikidata, AI systems for brand recognition and citations. 实体优化/知识图谱

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

85%

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

The body is well-structured with actionable templates, a clear sequenced workflow, validation checklists, and clean progressive disclosure to real reference files. Its main weakness is conciseness — the conceptual opening prose restates knowledge Claude already has.

Suggestions

Trim or remove the "Why entities matter for SEO + GEO" and opening definition paragraphs; assume Claude knows what entities and Knowledge Graphs are and lead directly with the audit procedure.

Collapse the duplicate references to entity-signal-checklist.md in Step 2 (it is linked twice in close succession) to reduce redundancy.

Move the conceptual SEO/GEO rationale into a reference file, keeping SKILL.md as a lean overview pointing to it.

Dimension	Reasoning	Score
Conciseness	Mostly efficient structured content (templates, tables, roadmaps), but the opening prose explains what entities are and why they matter for SEO/GEO — concepts Claude already knows — which is padding that could be tightened.	2 / 3
Actionability	Provides copy-paste-ready markdown templates (Entity Profile, AI resolution test tables, Report structure, roadmap) and concrete audit procedures with specific fields; for an instruction-only skill the guidance is directly actionable.	3 / 3
Workflow Clarity	Clear three-step sequence (Entity Discovery → Signal Audit → Report & Action Plan) reinforced by dedicated Input Validation and Output Validation checklists, giving explicit validation gates for the process.	3 / 3
Progressive Disclosure	Body is an overview that points via clearly signaled one-level-deep links to detailed references; all five referenced files (entity-signal-checklist, entity-type-reference, example-audit-report, knowledge-graph-guide, knowledge-panel-wikidata-guide) exist in references/.	3 / 3
	Total	11 / 12 Passed

Description

72%

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

The description is specific and distinctive with good multilingual natural-term coverage, but it omits an explicit "Use when…" trigger clause, leaving the "when" only implied and capping completeness at 2. Adding a concise trigger clause would lift it to anchor-3 completeness.

Suggestions

Append a "Use when…" clause to the description (e.g., "Use when establishing brand entity presence, claiming a Knowledge Panel, or fixing entity disambiguation") to satisfy the completeness anchor at level 3.

Expand the single "Build" verb into two or three distinct concrete actions (e.g., "Audit, build, and maintain entity presence…") to reach the multi-action specificity anchor.

Add a couple of casual trigger phrasings (e.g., "no knowledge panel", "Google doesn't know my brand") that currently live only in when_to_use into the description for stronger natural-term coverage.

Dimension	Reasoning	Score
Specificity	Names a concrete domain and specific target systems ("Knowledge Graph, Wikidata, AI systems" for "brand recognition and citations"), but relies on a single action verb ("Build") rather than listing multiple distinct concrete actions, so it is not comprehensive.	2 / 3
Completeness	Clearly answers "what" (build entity presence across named systems) but the description field lacks an explicit "Use when…" trigger clause, so per the guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Good coverage of natural terms users say ("Knowledge Graph", "Wikidata", "brand recognition", "citations") with multilingual variants ("实体优化/知识图谱"), matching the anchor for good natural-keyword coverage.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (entity presence/identity) with distinct triggers (Knowledge Graph, Wikidata, entity disambiguation) that are unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: MODSetter/SurfSense
Path: .cursor/skills/entity-optimizer/SKILL.md
Commit: 3b319ce

Reviewed: about 13 hours 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.