Agent skill · greedychipmunk
standard-site
Convert data into Standard.site AT Protocol lexicon records and validate them against official schemas. Use when creating or verifying site.standard.publication, site.standard.document, site.standard.graph.subscription, site.standard.graph.recommend, or site.standard.theme.basic records — even if the user doesn't name Standard.site directly. Also use when working with AT Protocol blog or article publishing workflows, or when mapping content to standard.site format from other sources.
What it needs
About 4k tokens when loaded.
What this skill does
Standard.site Convert data into Standard.site lexicon records for the AT Protocol and validate them against the official schemas. When to Use Creating publication, document, subscription, recommend, or theme records Converting blog posts, articles, or other content into standard.site format Validating existing records against standard.site lexicon schemas Working with AT Protocol publishing workflows that involve standard.site Mapping content from other formats (RSS, Markdown, JSON) to standard.site Lexicons at a Glance Lexicon $type Required Optional --- --- --- --- Publication site.standard.publication url, name icon, description, basicTheme, labels, preferences Document site.standard.document site, title, publishedAt path, description, coverImage, content, textContent, bskyPostRef, tags, links, labels, contributors, updatedAt Subscription site.standard.graph.subscription publication createdAt Recommend site.standard.graph.recommend document, createdAt — Theme site.standard.theme.basic background, foreground, accent, accentForeground — All colors in themes use site.standard.theme.color#rgb (r, g, b as integers 0–255) or site.standard.theme.color#rgba (adds a as integer 0–100). Conversion Workflow 1. Identify the target lexicon. Determine which record type the data maps to: A blog/site with a URL and name → publication An individual article or post → document A user following a publication → subscription A user endorsing a document → recommend Color scheme for a publication → theme (embedded inside publication as basicTheme) 2. Map required fields first. Every record must include $type and all required properties. See the quick reference table above. 3. Add optional fields. Include optional properties when the source data provides them. Do not invent values for missing optional fields. 4. Validate. Run the validation script before finalizing: Or pipe JSON via stdin: 5. Fix any errors. The script reports each issue with the property path and expected format. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills greedychipmunk/standard-site