CtrlK
BlogDocsLog inGet started
Tessl Logo

blog-schema

Generate complete JSON-LD schema markup for blog posts with Article/BlogPosting, Person, Organization, BreadcrumbList, ImageObject, and optional FAQPage. Validates against Google requirements and warns about deprecated types. Use when user says "schema", "blog schema", "json-ld", "structured data", "schema markup", "generate schema".

73

Quality

91%

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

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.

The content is highly actionable, with complete JSON-LD templates and a solid validation checklist across a well-sequenced workflow. Minor gains are available in conciseness (trimming padded explanatory passages) and progressive disclosure (splitting per-type templates into reference files).

Suggestions

Trim the @graph benefits list and AI-citation optimization note in Step 8/9, and consolidate the repeated 'only when visible FAQ content exists' guidance into one place to reduce token usage.

Add an explicit validate->fix->retry loop after the Step 8 checklist (e.g., 'If any check fails, correct the offending entity and re-run all checks before outputting') to reach top-band workflow clarity.

Consider moving the per-type JSON templates (Person, Organization, VideoObject, etc.) into a single one-level-deep reference file (e.g., references/templates.md) linked from SKILL.md, keeping only the BlogPosting and @graph overview inline.

DimensionReasoningScore

Conciseness

Largely lean with concrete JSON templates per step and skill-specific (non-generic) guidance, but minor padding exists (e.g., the @graph benefits list, the AI-citation note, and repeated 'only when visible FAQ exists' phrasing) that could be trimmed. Falls just above the mostly-efficient anchor rather than at fully lean.

4 / 5

Actionability

Each step ships a complete, copy-paste-ready JSON template with explicit @id reference patterns and concrete property structures, covering all common schema types and three output formats (HTML, standalone JSON, MDX).

5 / 5

Workflow Clarity

A clear nine-step sequence with an explicit eight-item validation checklist in Step 8, but the validate->fix->retry feedback loop is only implicit rather than spelled out, so it sits below the top anchor that requires explicit error-recovery loops.

4 / 5

Progressive Disclosure

The body is well-organized into nine clearly headed, sequentially numbered steps and is self-contained; no bundle files exist and no broken external references are present. It scores 4 rather than 5 because, at ~275 lines, some per-type template detail could be split into one-level-deep reference files rather than inlined.

4 / 5

Total

17

/

20

Passed

Description

100%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 is exemplary: it names concrete capabilities, enumerates the schema types handled, and provides an explicit, natural-language trigger clause. Both the 'what' and 'when' are answered with concrete, distinguishable language.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — generating markup for six named schema types (Article/BlogPosting, Person, Organization, BreadcrumbList, ImageObject, FAQPage), validating against Google requirements, and warning about deprecated types — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (generate, validate, warn about deprecated types) and 'when' (concrete trigger phrases via the 'Use when user says' clause), matching the top anchor exactly.

5 / 5

Trigger Term Quality

Provides a concrete 'Use when user says' clause with six natural trigger phrases including synonyms and variations ('schema', 'blog schema', 'json-ld', 'structured data', 'schema markup', 'generate schema').

5 / 5

Distinctiveness Conflict Risk

Targets a specific niche (blog-post JSON-LD schema) with distinct, scenario-specific triggers, giving minimal conflict risk with other skills.

5 / 5

Total

20

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
AgriciDaniel/claude-blog
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.