CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agent-ready-website-converter

Convert websites into agent-consumable formats with JSON-LD, product feeds, and .well-known discovery files. Use when: Generate valid JSON-LD for Organization and Product schemas; Create a .well-known/agent.json file for AI agent discovery; Audit a website's readiness for AI shopping and browsing agents.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/agent-ready-website-converter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

17%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 reads as a product landing page rather than an operational skill: it promotes a Python pipeline it does not ship, provides zero executable instructions, and pads token budget with FAQ and marketing copy. Claude loading this skill would learn what the tool supposedly does but have no idea how to do any of it.

Suggestions

Ship the pipeline scripts (or inline their commands) and replace the 'What it does' descriptions with concrete invocations, e.g. 'python scripts/extract.py ./dist' followed by generation and scoring commands.

Delete the marketing prose ('Why use this skill?', 'Turn Your Website into an Agent-Ready Storefront') and the FAQ section; retain only requirements, deliverable file formats, and the worked example.

Add an explicit step sequence with validation checkpoints (e.g. validate generated JSON-LD against schema.org before writing the agent-ready/ directory) and move schema templates and readiness-scoring criteria into referenced files under references/.

DimensionReasoningScore

Conciseness

Marketing framing ("As AI agents like Claude, ChatGPT, and shopping bots begin to navigate the web autonomously, traditional HTML isn't enough") and a six-question FAQ re-explaining how agents read websites pad the body with concepts Claude already knows. Not 1 because a few genuinely useful facts survive (Python 3.11+ requirement, deliverables, known limitations).

2 / 5

Actionability

The body only describes the pipeline ("The skill executes a multi-stage pipeline using Python-based extraction and generation scripts") with no commands, code, script paths, or API usage, and it explicitly states the scripts "are not in this folder". There is nothing executable for Claude to act on, so it cannot reach 2's 'high-level hints with specific steps missing'.

1 / 5

Workflow Clarity

The stages (Extraction, Generation, Formatting, Readiness Scoring) appear only as capability descriptions, not as an executable sequence, and no validation or verification steps exist for what is a batch web-scraping operation. Not 3 because there is no actionable step sequence at all, only a rough conceptual order with validation absent.

2 / 5

Progressive Disclosure

No bundle files exist and the body references none, while FAQ and promotional content that belongs outside SKILL.md is inlined. Not 3 because the section structure present is navigational marketing rather than skill organization, and the detailed material the skill needs (pipeline scripts, schema templates) exists nowhere to be disclosed.

2 / 5

Total

7

/

20

Passed

Description

87%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.

A strong description: third-person voice, concrete capability statement, and an explicit 'Use when:' clause with specific triggers. Its only weaknesses are minor coverage gaps (llms.txt, readiness scoring) and a few missing natural synonyms like 'structured data' or 'schema markup'.

DimensionReasoningScore

Specificity

"Convert websites into agent-consumable formats with JSON-LD, product feeds, and .well-known discovery files" plus "Generate valid JSON-LD", "Create a .well-known/agent.json", and "Audit a website's readiness" name several concrete actions. Not 5 because capabilities documented in the body (llms.txt generation, readiness scoring/report) are omitted from the description.

4 / 5

Completeness

Both are explicitly answered: a clear what ("Convert websites into agent-consumable formats with JSON-LD, product feeds, and .well-known discovery files") and an explicit "Use when:" clause listing three concrete triggers. Not 4 because the when-guidance is explicit with concrete trigger phrases rather than merely present.

5 / 5

Trigger Term Quality

Natural terms like "JSON-LD", ".well-known/agent.json", "AI agent discovery", and "AI shopping and browsing agents" are present. Not 5 because common user synonyms such as "structured data", "schema markup", or "llms.txt" are missing.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (agent-ready website conversion) with distinct triggers (JSON-LD schemas, agent.json discovery, AI readiness audits) that are unlikely to fire for unrelated skills. Not 4 because no meaningful overlap with neighboring web/SEO skills is evident from the triggers given.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

skills/agent-ready-website-converter/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.