CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

entity-registry

Use when the user asks to "optimize entity presence", reconcile an entity identity, or update canonical Knowledge Graph facts; audits and maintains machine-facing identity, sameAs, schema, disambiguation, and AI-recognition evidence through the entities registry. Not for page-level AI-citation readiness - use geo-content-optimizer; not for human-facing brand canon - use narrative-registry. 实体注册/知识图谱

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

This is a dense, protocol-style skill body that is exceptionally actionable — concrete commands, explicit authorization rules, and clear stop conditions — with well-organized one-level-deep references that check out against the actual bundle. Remaining gaps are minor: a missing error-recovery loop after 'verify entities', some duplicated reference listings, and two bundle files not surfaced in the overview.

Suggestions

Add an explicit feedback loop after step 9: instruct what to do when 'verify entities' fails (e.g., re-check event schema conformance, fix the offending event, re-run verification before reporting).

Consolidate the Runtime Reads and Reference Materials lists into a single section to remove the duplicated ../../references/ entries.

Surface the two unreferenced bundle files (entity-type-reference.md, example-audit-report.md) in the Reference Materials section so their content is discoverable from the overview.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no space is spent explaining what Knowledge Graphs or sameAs are, and dense lines like 'Pageviews and mention counts are recognition proxies, not authority scores' each carry operational rules. It is not 5 because the Skill Contract paragraph is a long run-on packing unit/reads/writes/done-when into one block, and the Runtime Reads list duplicates the Reference Materials entries, both of which could be trimmed.

4 / 5

Actionability

Guidance is fully concrete and copy-paste ready: full script invocations with placeholders ('python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/kg.py" reconcile "<entity>"', 'python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" get entities <aggregate-id>'), precise revision/offset semantics for owner-append, and a nine-step procedure covering the audit, reconcile, and update cases. This matches the top anchor for an instruction-only skill.

5 / 5

Workflow Clarity

The numbered Procedure is clearly sequenced with a dedicated Decision Gates section providing explicit stop/continue checkpoints and a terminal 'Run verify entities' validation step. It is not 5 because there is no feedback loop after verification — nothing instructs what to do if 'verify entities' fails — leaving a minor validation gap.

4 / 5

Progressive Disclosure

Structure is good: a concise overview body with a labeled Reference Materials section pointing one level deep to real files (entity-signal-checklist.md, knowledge-graph-guide.md, and knowledge-panel-wikidata-guide.md all exist in references/ and carry substantive content). It is not 5 because two bundle files (entity-type-reference.md, example-audit-report.md) are never referenced from SKILL.md, and the same ../../references/ files are listed twice (Runtime Reads and Reference Materials), which slightly muddies navigation.

4 / 5

Total

17

/

20

Passed

Description

87%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 description: explicit 'Use when' triggers with quoted user phrasings, a clear statement of what the skill does, and unusually good negative boundary guidance that separates it from sibling skills. Trigger term coverage could add a few natural synonyms (Wikidata, knowledge panel) to reach the top tier on every dimension.

DimensionReasoningScore

Specificity

The description names two concrete actions — 'audits and maintains' — against a specific list of objects ('machine-facing identity, sameAs, schema, disambiguation, and AI-recognition evidence'), which matches the 'several specific actions; minor gaps' anchor. It falls short of 5 because the action verbs are limited to audit/maintain/reconcile/update without fuller coverage of the skill's operations (e.g., merging duplicates, verifying QIDs).

4 / 5

Completeness

It explicitly answers both questions: 'Use when the user asks to...reconcile...or update canonical Knowledge Graph facts' (when, with concrete trigger phrases) and 'audits and maintains machine-facing identity, sameAs, schema, disambiguation, and AI-recognition evidence through the entities registry' (what). This matches the top anchor exactly.

5 / 5

Trigger Term Quality

Quoted natural trigger phrases like '"optimize entity presence"', 'reconcile an entity identity', and 'update canonical Knowledge Graph facts' give good keyword coverage, plus negative triggers steering to sibling skills. It is not 5 because common synonyms a user might say — 'Wikidata', 'knowledge panel', 'schema markup' — appear only in other frontmatter fields, not in the description itself.

4 / 5

Distinctiveness Conflict Risk

The explicit negative boundary clauses — 'Not for page-level AI-citation readiness - use geo-content-optimizer; not for human-facing brand canon - use narrative-registry' — carve out a clear niche with minimal conflict risk, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

relative_links

Relative link issues: 14 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

protocol/entity-registry/SKILL.md

Reviewed

Table of Contents

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.