CtrlK
BlogDocsLog inGet started
Tessl Logo

author-info

Use when auditing metadata, crawlability, structured data, or indexability related to Implement comprehensive author markup. Verify the rendered HTML and HTTP response rather than relying only on source files.

60

Quality

70%

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/author-info/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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 and lean with excellent progressive disclosure to a single real reference file, but it keeps all executable code in that reference and lacks explicit validation checkpoints in the inline workflow. Inlining a minimal JSON-LD example and an explicit verify step would raise actionability and workflow clarity.

Suggestions

Inline a minimal, copy-paste Person/Organization JSON-LD snippet and the author-property wiring so the body is actionable without opening the reference.

Add an explicit validation checkpoint, e.g. "After editing, fetch the rendered HTML (not the source) and confirm the JSON-LD block contains the author Person/Organization and its sameAs links before treating the rule as satisfied."

Drop the duplicated rule title inside the Code Review section ("related to Implement comprehensive author markup") to tighten the already-lean body.

DimensionReasoningScore

Conciseness

The body is lean with terse Check/Fix/Explain/Code Review sections and no concept padding; the single benefit sentence is acceptable framing and every section earns its place.

3 / 3

Actionability

Concrete guidance is present (specific schema types Person/Organization, properties name/url/sameAs/jobTitle, and a verification approach), but no executable code example is inlined in the body — the actionable code is deferred to references/rule.md.

2 / 3

Workflow Clarity

An ordered audit/fix sequence exists (Check, Fix, Explain, Code Review) and verification is mentioned, but validation checkpoints are only implicit with no explicit validate-then-proceed feedback loop in the body.

2 / 3

Progressive Disclosure

The body is a concise overview with a single clearly-signaled one-level-deep reference to the real file references/rule.md, which holds the detailed code, rationale, and verification steps.

3 / 3

Total

10

/

12

Passed

Description

67%

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 includes an explicit Use-when trigger and names a specific SEO-author-markup audit domain, but it reads as templated checklist prose with embedded title text and only moderately natural trigger terms. Trigger phrasing and distinctiveness among sibling skills are the main weaknesses.

Suggestions

Rewrite the trigger in natural user voice, e.g. "Use when the user mentions author schema, JSON-LD Person/Organization markup, rich results for authors, or wants to verify author structured data is rendering in the page HTML."

Replace the embedded skill title ("related to Implement comprehensive author markup") with a concrete capability statement and drop the generic rendered-HTML clause that overlaps with sibling SEO-audit skills.

Add concrete, granular actions (e.g. "inject a Person/Organization JSON-LD block, wire it to the Article/WebPage author property, and confirm sameAs links resolve") to lift specificity.

DimensionReasoningScore

Specificity

Names the SEO-author-markup domain and several audit actions ("auditing metadata, crawlability, structured data, or indexability", "Verify the rendered HTML and HTTP response"), but the actions are broad audit categories rather than a tight list of concrete actions, and the skill's own title is awkwardly embedded.

2 / 3

Completeness

Explicitly answers both what (audit author-markup signals and verify rendered HTML/HTTP responses vs source files) and when via an explicit "Use when..." trigger clause.

3 / 3

Trigger Term Quality

Contains relevant natural terms ("structured data", "crawlability", "author markup", "indexability") but the templated phrasing and missing common variations (e.g. "schema markup", "JSON-LD", "rich results", "person schema") keep it from full coverage.

2 / 3

Distinctiveness Conflict Risk

The author-markup SEO niche is fairly distinct, but the generic "Verify the rendered HTML and HTTP response rather than relying only on source files" clause overlaps with sibling SEO-audit skills in the same checklist family.

2 / 3

Total

9

/

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.