CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/organization/SKILL.md
SKILL.md
Quality
Evals
Security

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 a well-structured, actionable overview with an excellent progressive-disclosure split to references/rule.md and a real validation loop through Google's Rich Results Test. Its only real weakness is redundancy — the Explain section and the Check/Code Review overlap could be merged or cut to tighten token efficiency without losing any guidance.

DimensionReasoningScore

Conciseness

The body is short but contains genuine redundancy: the 'Explain' section teaches Claude what Organization schema and the Knowledge Panel are (concepts it already knows), and 'Code Review' largely repeats 'Check' (same @type check, same properties, same Rich Results Test validation).

3 / 5

Actionability

Concrete, executable instruction: 'Add an Organization schema JSON-LD block to the homepage <head>. Include name, url, logo (ImageObject with url, width, height), contactPoint, and sameAs array...', with verifiable criteria ('logo.url is an absolute HTTPS URL', 'sameAs array contains at least 2 verified social profiles') and a named validation tool; full code examples are appropriately deferred to the reference.

4 / 5

Workflow Clarity

A coherent Check → Fix → Code Review sequence with an explicit validation checkpoint ('Validate with Google's Rich Results Test') and a post-fix review that catches a real gotcha ('Confirm Organization schema is NOT duplicated on interior pages'). It falls short of 5 only because there is no explicit fix-then-revalidate loop and the 'Explain' section sits awkwardly mid-flow.

4 / 5

Progressive Disclosure

A lean ~35-line overview with clear section headers and a well-signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — pointing to a real file that contains exactly those code examples; the split is appropriate for a simple skill.

5 / 5

Total

16

/

20

Passed

Description

58%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 'Use when' trigger and a clear, niche domain focus, but it is capped by a missing action vocabulary (only 'auditing') and the absence of the skill's most natural trigger terms — 'organization schema', 'schema markup', 'JSON-LD'. Adding those terms and the word 'Organization' would lift specificity, trigger quality, and distinctiveness simultaneously.

Suggestions

Add the skill's core trigger terms to the description: 'organization schema', 'schema markup', 'JSON-LD', and 'SEO' — currently none of these words appear, so users asking to 'add organization schema' or 'check schema markup' won't naturally match.

Broaden the action beyond 'auditing' to cover the skill's full scope (check, add, and fix Organization schema), since the body's Fix section is half the skill but the description only promises auditing.

Name 'Organization' schema explicitly (e.g., 'auditing Organization schema markup on a business homepage') to distinguish it from sibling structured-data skills covering Article, Product, or LocalBusiness schema.

DimensionReasoningScore

Specificity

Names the domain ('auditing structured data on a business or brand website homepage', 'Knowledge Panel information in Google Search') with one concrete action (auditing), but lists no further actions and the second sentence describes audiences rather than capabilities.

3 / 5

Completeness

Both what ('auditing structured data on a business or brand website homepage') and when (explicit 'Use when auditing...' plus audience scoping) are present, but the when-clause restates the what rather than naming distinct user situations, so it falls short of the fully explicit anchor 5.

4 / 5

Trigger Term Quality

Relevant keywords are present ('structured data', 'brand website homepage', 'Knowledge Panel', 'Google Search') but common synonyms users would actually say are missing — 'schema', 'schema markup', 'organization schema', 'JSON-LD', 'SEO' never appear, and 'auditing' won't match users asking to add or fix schema.

3 / 5

Distinctiveness Conflict Risk

Homepage/brand/Knowledge Panel scoping helps, but the description never says 'Organization' and 'structured data' generically spans many schema types (Article, Product, LocalBusiness), leaving real overlap risk with sibling schema-audit skills rather than only minor overlap.

3 / 5

Total

13

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

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