slideshot: Skill for Claude Code

.agents/skills/schema-markup/SKILL.md

schema-markup is a skill for Claude Code, Codex from 06ketan/slideshot. It costs 122 tokens per session (1,187 once invoked), scanned A, a copy of schema, MIT.

Instructions for adding schema markup, structured information on a webpage that helps search engines understand its content.

In plain words
What is it for?
For adding or fixing structured data for products, FAQs, reviews, breadcrumbs, and other page types.
Why use it?
They guide accurate JSON-LD implementation and help identify which search features, such as rich results, the page may qualify for.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is 06ketan/slideshot's own configuration. It tells Claude Code and Codex how to work on slideshot itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything slideshot configures →

Reuse

Borrowing it

Nothing to install: this file belongs to 06ketan/slideshot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/06ketan/slideshot/main/.agents/skills/schema-markup/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/06ketan/slideshot

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for schema-markup

README.md
[![agentmods](https://agentmods.dev/badge/skills/06ketan/slideshot/schema-markup/github.svg)](https://agentmods.dev/skills/06ketan/slideshot/schema-markup)
Your own site
<a href="https://agentmods.dev/skills/06ketan/slideshot/schema-markup"><img src="https://agentmods.dev/badge/skills/06ketan/slideshot/schema-markup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for schema-markup

Your own site · 80×15
<a href="https://agentmods.dev/skills/06ketan/slideshot/schema-markup"><img src="https://agentmods.dev/badge/skills/06ketan/slideshot/schema-markup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,187 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00122 $0.01187
Opus 5 $0.00061 $0.00593
Sonnet 5 $0.00024 $0.00237
Haiku 4.5 $0.00012 $0.00119

Measured 8d ago against content hash 728f221b25d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

schema-markup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

97% identical to schema — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/schema-markup/SKILL.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Schema Markup

You are an expert in structured data and schema markup. Your goal is to implement schema.org markup that helps search engines understand content and enables rich results in search.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before implementing schema, understand:

  1. Page Type - What kind of page? What's the primary content? What rich results are possible?

  2. Current State - Any existing schema? Errors in implementation? Which rich results already appearing?

  3. Goals - Which rich results are you targeting? What's the business value?


Core Principles

1. Accuracy First

  • Schema must accurately represent page content
  • Don't markup content that doesn't exist
  • Keep updated when content changes

2. Use JSON-LD

  • Google recommends JSON-LD format
  • Easier to implement and maintain
  • Place in <head> or end of <body>

3. Follow Google's Guidelines

  • Only use markup Google supports
  • Avoid spam tactics
  • Review eligibility requirements

4. Validate Everything

  • Test before deploying
  • Monitor Search Console
  • Fix errors promptly

Common Schema Types

Type Use For Required Properties
Organization Company homepage/about name, url
WebSite Homepage (search box) name, url
Article Blog posts, news headline, image, datePublished, author
Product Product pages name, image, offers
SoftwareApplication SaaS/app pages name, offers
FAQPage FAQ content mainEntity (Q&A array)
HowTo Tutorials name, step
BreadcrumbList Any page with breadcrumbs itemListElement
LocalBusiness Local business pages name, address
Event Events, webinars name, startDate, location

Read the full file on GitHub · 180 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 180 lines · 122 tokens per session scan A 728f221b25d0

Subscribe to this mod's changes

schema-markup is a skill published in the GitHub repository 06ketan/slideshot (2 stars, last pushed 4mo ago), licensed MIT. It adds 122 tokens to every session and 1,187 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to schema, differing in 6 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens