organization

Use when auditing structured data on a business or brand website homepage. Applies to organisations, companies, non-profits, and publishers that want accurate Knowledge Panel information in Google Search.

Quality

66%

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 ./skills/organization/SKILL.md

Quality

Content

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

The body is well-structured with a clean check/fix/review workflow, concrete property-level requirements, and exemplary progressive disclosure through a single clearly signaled reference file. Main weakness is redundancy: 'Explain' and 'Code Review' add little that 'Check' and 'Fix' don't already cover, which wastes tokens without harming correctness.

Dimension	Reasoning	Score
Conciseness	Mostly lean, but the 'Explain' section ('Organization structured data tells Google who you are as a brand... Google uses it to populate the Knowledge Panel...') re-explains background Claude already knows, and the 'Code Review' section largely duplicates the 'Check' section (both describe inspecting the homepage JSON-LD and running the Rich Results Test). Fits 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	Concrete, specific guidance throughout: exact required properties (name, url, logo as ImageObject with url/width/height, contactPoint, sameAs), a named validation tool (Google's Rich Results Test), an absolute HTTPS logo URL requirement, and 'at least 2 verified social profiles'. Falls short of fully copy-paste ready only because the JSON-LD example lives in the reference file rather than the body — acceptable for an instruction skill but leaves minor gaps.	4 / 5
Workflow Clarity	A clear Check → Fix → Code Review sequence with explicit validation checkpoints (Rich Results Test in both Check and Code Review, verified social profiles, confirming no duplication on interior pages). Not a 5 because there is no error-recovery guidance for what to do when validation fails.	4 / 5
Progressive Disclosure	A short (~45 line), well-sectioned overview with a clearly signaled, verified one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — the file exists at 153 lines and is not further nested). Content is appropriately split: essentials inline, implementation detail in the reference.	5 / 5
	Total	16 / 20 Passed

Description

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

The description has an explicit, well-formed trigger clause and a clear target audience, but undersells the skill: it never mentions Organization schema, JSON-LD, or schema markup — the terms a user would most naturally say — and frames the skill purely as auditing rather than also adding/fixing markup. Distinctiveness is good thanks to the Knowledge Panel and brand framing.

Suggestions

Include the primary trigger terms in the description — e.g., 'Organization schema', 'schema markup', 'JSON-LD' — so it matches what users actually say when they need this skill.

State the skill's full action set, not just auditing: e.g., 'audit, add, and validate Organization (JSON-LD) schema markup on a business homepage'.

Tighten the second sentence ('Applies to organisations, companies, non-profits, and publishers...') which restates the audience rather than adding capabilities or triggers.

Dimension	Reasoning	Score
Specificity	Names the domain ('auditing structured data on a business or brand website homepage') with one concrete action, but omits the skill's other actions such as adding or fixing Organization JSON-LD markup. Matches the 'domain and 1-2 concrete actions, but not comprehensive' anchor; not a 4 because there are not several specific actions listed.	3 / 5
Completeness	Both what ('auditing structured data on a business or brand website homepage') and when (explicit 'Use when...' clause) are present. Not a 5 because the 'what' is thin — it never states the skill adds or fixes Organization schema markup, only that it audits.	4 / 5
Trigger Term Quality	Includes relevant keywords like 'structured data', 'brand website homepage', 'Knowledge Panel', and 'Google Search', but misses the most natural user triggers for this skill: 'Organization schema', 'schema markup', and 'JSON-LD'. Fits 'some relevant keywords but missing common variations or synonyms'; not a 4 because the core vocabulary of the task is absent.	3 / 5
Distinctiveness Conflict Risk	Scoped to brand presence and Knowledge Panel information, making it mostly distinct. Minor overlap risk remains because 'structured data' generically could trigger this skill for non-Organization schema types (e.g., Product or Article markup) that the skill does not cover.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/organization/SKILL.md
Commit: 7bfd868

Reviewed: 1 day 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.