Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Standard.site Hugo Integration

    1

    Integrate standard.site lexicons into Hugo blogs for AT Protocol publishing and Bluesky rich previews.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Standard.site Hugo Integration

    Standard.site Hugo Integration

    Example session with this skill installed

    Help me integrate standard.site into my Hugo blog at devlog.example.com so my posts show up properly on Bluesky. I have my DID and a Bluesky handle.

    • Read your context and instructions
    • Compiled the standard site hugo
    • Generated the UI component

    I have analyzed your Hugo project and identified the necessary integration points for standard.site. I will now configure the atproto publication record and setup the sync script.

    Hugo standard.site Integration

    I have added the [params.standard_site] block to your hugo.toml, created the head partial, and initialized the publishing script.

    1. Configuration added to hugo.toml:

    [params.standard_site]
      enable = true
      did = "did:plc:z72i7hd7zzr..."
      publication_uri = "at://did:plc:z72i7hd7zzr.../site.standard.publication/self"
    

    2. New Partial: layouts/partials/standard-site.html:

    {{ if .Site.Params.standard_site.enable }}
      <link rel="site.standard.publication" href="{{ .Site.Params.standard_site.publication_uri | safeURL }}">
      {{ with .Params.standard_site_uri }}
        <link rel="site.standard.document" href="{{ . | safeURL }}">
      {{ end }}
    {{ end }}
    

    3. Deployment Script: scripts/publish-atproto.js:

    const { BskyAgent } = require('@atproto/api');
    const matter = require('gray-matter');
    const dotenv = require('dotenv');
    // Full implementation handles TID generation, PDS resolution, 
    // and record syncing for site.standard.document
    

    Next steps

    1. Add your Bluesky app password to the new .env file (do not commit this).
    2. Run npm install dotenv gray-matter to prepare the environment.
    3. Execute node scripts/publish-atproto.js to sync your first post to your PDS.

    standard-site.html

    TSX · React component

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Bluesky rich previews for Hugo blogs often fail because standard meta tags aren't enough for the AT Protocol. This skill implements the standard.site lexicons, syncing your Hugo posts directly to your Personal Data Server (PDS) so they appear natively in the ATmosphere.

    What it does

    • Lexicon Integration: Implements site.standard.publication and site.standard.document records on your PDS.
    • Rich Previews: Configures head partials to emit the required at:// link tags for Bluesky's AppView crawler.
    • Automated Publishing: Deploys a Node.js script to sync Hugo Markdown files to atproto records with idempotent hash checking.
    • Asset Handling: Uploads post cover images and site icons as blobs, respecting the 1MB lexicon limits.
    • Theme Sync: Maps Hugo site parameters to basicTheme hex colors for consistent branding across the AT Protocol.

    How it works

    1. Endpoint Resolution: Resolves your DID to find the correct PDS service endpoint via PLC directory or did.json.
    2. Template Injection: Modifies your Hugo head partials to include the <link> verification tags.
    3. Script Setup: Configures a publishing script with dotenv for secure app password management.
    4. Content Sync: Runs the sync process to write document records and update post frontmatter with AT-URIs.

    Frameworks & tools

    Hugo, Node.js, AT Protocol (atproto), Bluesky, gray-matter, dotenv.

    Why this beats prompting it yourself

    Manual integration often fails on AT Protocol specifics like TID rkey generation or missing $type fields in nested JSON objects which cause silent failures. This skill handles the PDS endpoint resolution and Go template safeURL escaping that standard AI prompts typically miss.

    Use cases

    • Syncing a self-hosted Hugo blog to the ATmosphere for native Bluesky discovery.
    • Enabling rich link previews for blog posts shared on Bluesky.
    • Managing decentralized site metadata via a personal PDS.

    Known limitations

    Does not handle DID/handle verification (DNS/well-known). Not suitable for CI/CD environments requiring repo-write-capable app passwords. Not compatible with non-Markdown Hugo content.

    Requires pre-existing AT Protocol handle verification. Not for CI/CD use due to app password security. Limited to Markdown-based Hugo posts. Requires Node.js runtime for the publishing script.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Requires

    Plc
    Node.js

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Environment Variables

    Allowed Hosts

    plc.directory
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    Standard meta tags often fail to render on Bluesky because the AT Protocol prioritizes PDS records. This skill implements the specific site.standard lexicons required for your Hugo posts to appear as native, rich-media objects within the ATmosphere.

    The package includes the Hugo head partial templates, a Node.js synchronization script for your PDS, and a configuration guide for environment variables. It provides everything necessary to bridge your local Markdown files with the AT Protocol.

    Yes, the synchronization script uses idempotent hash checking, meaning it only uploads new or modified posts and prevents duplicate records on your PDS. It also intelligently handles image blobs to ensure they stay within the protocol's 1MB limit.

    This skill is designed for any AI agent or developer environment with Node.js access and the ability to modify Hugo templates. It works best with agents that have file-system access to run the sync script and edit your theme’s partials.

    Currently, this skill requires your Hugo content to be in Markdown format with standard frontmatter. It also assumes you have already completed your DID/handle verification (via DNS or .well-known) as it focuses specifically on content and lexicon syncing.

    New in Agents & Orchestration