CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

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

Quality

Content

65%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-organized, token-efficient overview with excellent progressive disclosure to a real one-level reference. Its weaknesses are the absence of any executable snippet or concrete verification method in the body itself, leaving the Check and Fix steps less actionable than they could be.

Suggestions

Add a minimal executable element to the body, e.g. a short JSON-LD Person snippet or a concrete check command like fetching the rendered page and locating the author schema, so the Fix/Check steps are actionable without opening the reference.

Make the Check step's verification method explicit (which URL to fetch, what to grep for in the rendered HTML/HTTP response) instead of delegating it with "describe how to verify the final page output".

Trim the opening rationale sentence about search engines and author authority, and drop the repeated "related to Implement comprehensive author markup" phrase in the Code Review section.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with almost no padding. Minor over-explanation remains: the opening SEO-rationale sentence ("Structured author information helps search engines uniquely identify authors...") and the repeated "related to Implement comprehensive author markup" phrase in Code Review could be trimmed.

4 / 5

Actionability

Some concrete guidance ("Include properties like `name`, `url`, `sameAs`, and `jobTitle`"; "Add a `Person` or `Organization` schema... link it to the `author` property"), but the executable JSON-LD example lives only in references/rule.md and the Check step gives no method for verification. Not a 4 because the body itself contains no copy-paste-ready code or command.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections provide a rough sequence for an audit task, but checkpoints are implicit: "Verify that the page includes structured data identifying the author" and "describe how to verify the final page output" state outcomes, not concrete verification steps. No destructive/batch operations, so no validation cap applies.

3 / 5

Progressive Disclosure

A clear, well-sectioned overview under 50 lines with a well-signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — the file exists and contains the JSON-LD implementation details without further nesting.

5 / 5

Total

15

/

20

Passed

Description

66%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 a valid explicit trigger and good natural SEO-audit keywords, but the capability statement is weakened by the injected rule title and the generic trigger terms create overlap risk with sibling SEO skills. Rewriting as a clean capability-plus-trigger pair with topic-specific terms would lift it.

Suggestions

State the capability directly instead of embedding the rule title, e.g. "Audit author structured data (JSON-LD Person/Organization markup) in rendered pages and verify the HTTP response rather than only source files."

Add topic-distinct trigger terms such as "author markup", "JSON-LD", "byline", or "schema.org Person" so it is distinguishable from sibling SEO-audit skills that share "metadata, crawlability, structured data, indexability".

Lead with the what (audit/verify actions) before the "Use when..." clause so both parts read as distinct, concrete statements.

DimensionReasoningScore

Specificity

Names the SEO-audit domain and two concrete actions ("auditing metadata, crawlability, structured data, or indexability"; "Verify the rendered HTML and HTTP response"), matching the anchor for 1-2 concrete actions without comprehensive coverage. The awkward "related to Implement comprehensive author markup" title-injection further blurs the stated capability.

3 / 5

Completeness

An explicit "Use when auditing..." trigger clause is present, and the what (audit author structured data, verify rendered output) is stated alongside it — both present but not cleanly separated. Not a 5 because the what is entangled in the when-clause rather than stated as concrete capability phrases.

4 / 5

Trigger Term Quality

Good natural-term coverage: "auditing", "metadata", "crawlability", "structured data", "indexability", "rendered HTML", "HTTP response" are phrases users would say when needing this skill. Missing synonyms for the core topic like "author markup", "JSON-LD", "schema", or "rich results", so not a 5.

4 / 5

Distinctiveness Conflict Risk

The author-markup niche is specific, but the generic trigger terms ("metadata, crawlability, structured data, or indexability") would match nearly any sibling SEO-audit skill, and "author markup" appears only late in an awkward construction. Overlap with closely related SEO skills is more than minor.

3 / 5

Total

14

/

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/author-info/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.