CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

72%

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

70%

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

A well-structured instruction-only skill with a clean audit-to-fix-to-verify workflow and an appropriately delegated single reference. The main weaknesses are duplicated Check/Code Review sections and the absence of any inline executable code example in the body.

Suggestions

Merge the near-duplicate 'Check' and 'Code Review' sections to remove redundancy and recover token budget.

Add one minimal inline JSON-LD snippet so the core action is copy-paste ready without forcing a reference hop.

Trim the 'Explain' section's Knowledge Panel definition, which restates a concept Claude already knows.

DimensionReasoningScore

Conciseness

The body is largely lean, but the 'Check' and 'Code Review' sections duplicate the same homepage-JSON-LD verification instructions, and 'Explain' restates the Knowledge Panel concept, so it could be tightened.

2 / 3

Actionability

The Fix section gives specific property lists (name, url, logo ImageObject with width/height, contactPoint, sameAs), but the body carries no inline executable code example, delegating that to the reference, leaving guidance concrete but incomplete.

2 / 3

Workflow Clarity

A clear Check → Fix → Code Review sequence is present with explicit validation checkpoints ('Validate with Google's Rich Results Test', 'Confirm Organization schema is NOT duplicated on interior pages').

3 / 3

Progressive Disclosure

The SKILL.md is a concise overview that signals a single one-level-deep reference ('see references/rule.md') which exists as a real file, matching the clear-overview-with-well-signaled-reference anchor.

3 / 3

Total

10

/

12

Passed

Description

75%

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 clear, well-triggered description for a specific SEO auditing niche, with an explicit 'Use when' clause and good distinctiveness. It loses points on specificity and trigger coverage for relying on a single action verb and omitting the common 'Organization schema'/'JSON-LD' phrasings.

Suggestions

Add concrete action verbs beyond 'auditing' (e.g., 'add, validate, and audit Organization schema markup') to lift specificity.

Include common trigger terms users actually say, such as 'Organization schema', 'JSON-LD', or 'schema markup'.

DimensionReasoningScore

Specificity

It names the domain ('business or brand website homepage', 'structured data') and a single action ('auditing'), but does not list multiple concrete actions, matching the 'names domain and some actions' anchor rather than the multi-action anchor above.

2 / 3

Completeness

An explicit 'Use when auditing structured data...' trigger answers when, and 'auditing structured data... Knowledge Panel information' answers what, satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Natural terms like 'structured data', 'Knowledge Panel', and 'Google Search' appear, but common variations a user would say ('Organization schema', 'JSON-LD', 'schema markup') are missing, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The brand/Knowledge-Panel SEO niche with terms like 'business or brand website homepage' and 'Knowledge Panel information' is distinct and unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.