Skip to content
Contact
Marketing

Schema Markup

coreyhaines31

Add structured data only for information visibly supported by the page and relevant schema definitions.

SKILL.md

---
name: knoveya-schema-markup
description: "Add structured data only for information visibly supported by the page and relevant schema definitions. Use for matching marketing work."
---

# Schema Markup

## Scope

Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.

## Workflow

Add structured data only for information visibly supported by the page and relevant schema definitions.

Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.

## Acceptance check

JSON-LD parses and makes no unsupported rating or availability claim.

## Example task

Describe an editorial article without marking it as a purchasable product.

## Report

State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.
View all

How to use

Copy the full block, including its frontmatter, into a new folder named knoveya-schema-markup as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-schema-markup/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.

This is an independent Knoveya skill. No files are installed by this website.

Example

Describe an editorial article without marking it as a purchasable product.

Verify

JSON-LD parses and makes no unsupported rating or availability claim.

Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.

Limits

The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.