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

82%

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

75%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 well-built protocol skill body: concrete commands, a sequenced procedure with decision gates and a terminal verify step, and disciplined avoidance of concept explanations. The main weaknesses are structural — triple-listed references, an undescribed-in-command-form write path, no verify-failure recovery loop, and two orphaned bundle files.

Suggestions

Deduplicate the reference listings: 'Runtime Reads', Procedure step 1, and 'Reference Materials' each re-list the same files — collapse to one canonical list (e.g., step 1 can say 'read the three runtime references below').

Show the owner-append invocation as a concrete command example (upsert and accept/reject), matching the level of specificity already given for `get entities` and the connectors.

Add a short error-recovery loop after step 9: what to inspect and retry when `verify entities` fails (e.g., expected_revision mismatch, schema validation error), and link entity-type-reference.md and example-audit-report.md from the Reference Materials section so they are discoverable.

DimensionReasoningScore

Conciseness

Lean, dense operational prose with zero explanation of concepts Claude already knows (no primer on Knowledge Graphs, schema.org, or sameAs). Not a 5 because the same reference files are listed three times — "Runtime Reads", Procedure step 1, and "Reference Materials" — which is trimmable token spend.

4 / 5

Actionability

Concrete, executable commands are given (`registry-events.py get entities <aggregate-id>`, the connector invocations, the full `AARON_SKILLS_ROOT` shell resolution) alongside precise protocol details ("the decision request omits `expected_revision` and acceptance inherits the proposal revision"). Not a 5 because the core write path — the `owner-append` invocation for upserts and accept/reject — is described but never shown as a runnable command, leaving a minor gap.

4 / 5

Workflow Clarity

A clear 9-step sequence with most checkpoints present: Decision Gates define stop conditions, the Skill Contract defines done-when, and step 9 runs `verify entities` as an explicit validation step (so the destructive/batch cap is not triggered). Not a 5 because there is no error-recovery feedback loop for what to do when `verify entities` fails, and per-step intermediate checkpoints are implicit.

4 / 5

Progressive Disclosure

Good structure: an overview body with clearly labeled one-level-deep reference sections ("Runtime Reads", "Reference Materials"), and the three referenced bundle files (entity-signal-checklist.md, knowledge-graph-guide.md, knowledge-panel-wikidata-guide.md) all exist. Not a 5 because two bundle files (entity-type-reference.md, example-audit-report.md) are never linked from SKILL.md, making them undiscoverable, and several referenced paths (../../references/*) point outside the bundle where their existence cannot be confirmed.

4 / 5

Total

16

/

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: third-person voice, explicit trigger phrases, a clear capability statement, and unusual negative-skill disambiguation that sharply reduces conflict risk. The only gap is a handful of missing natural trigger synonyms (Wikidata, knowledge panel) that keep trigger coverage just short of comprehensive.

DimensionReasoningScore

Specificity

Lists several concrete actions — "audits and maintains machine-facing identity, sameAs, schema, disambiguation, and AI-recognition evidence" plus "reconcile an entity identity" and "update canonical Knowledge Graph facts" — with only minor gaps (e.g., proposal review is not named). Not a 5 because the actions stop short of the fully concrete operation level (upsert events, QID reconciliation, proposal accept/reject) that the skill actually performs.

4 / 5

Completeness

Explicitly answers both: "Use when the user asks to..." with three concrete trigger phrases, and a clear what ("audits and maintains machine-facing identity... through the entities registry"). Matches the anchor for clear and explicit what AND when with concrete trigger phrases; also adds explicit negative boundaries, exceeding the 4 anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage — "optimize entity presence", "reconcile an entity identity", "Knowledge Graph", "sameAs", "schema", "disambiguation" — phrased the way a user in this domain would speak. Not a 5 because common variations users would actually say ("Wikidata", "knowledge panel", "entity SEO") are absent, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (machine-facing entity identity) with explicit conflict resolution — "Not for page-level AI-citation readiness - use geo-content-optimizer; not for human-facing brand canon - use narrative-registry" — giving minimal overlap risk with closely related skills.

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.