Skill

sourcecraft-publisher

Publishes built static page or React artifacts to SourceCraft Sites repo (Yandex infra, Russia) using YYYY/YYYY-MM/page-slug layout via Python script.

React

Python

Git

Html

deployment

Install

npx claudepluginhub artwist-polyakov/polyakov-claude-skills --plugin sourcecraft-publisher

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Publish already-built static artifacts to a SourceCraft Sites repository. Works from Russia (Yandex infrastructure).

Supporting Assets

config/README.mdreferences/publish-checklist.mdscripts/publish_static.py

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Parent Repo Stars80

Parent Repo Forks23

Last CommitMar 29, 2026

Actions

View Source View Plugin View on GitHub View README

SourceCraft Publisher

Publish already-built static artifacts to a SourceCraft Sites repository. Works from Russia (Yandex infrastructure).

This skill is the deployment/output layer for page artifacts created by other skills (e.g. telegram-channel-parser digest).

Required repository layout

Every published artifact must go into this path shape inside the target repo:

<year>/<year>-<month>/<page-slug>/

Example:

2026/2026-03/ai-digest-week/

Never publish flat at repo root. Never skip the year or year-month nesting.

What this skill expects

Input should already exist as one of these:

a folder of built static files
a single HTML artifact plus local assets
a small static site ready to serve from a subdirectory

This skill does not do frontend design work. It packages and publishes what already exists.

Config

Read config/README.md for required environment variables and token setup.

cp config/.env.example config/.env

Required: SOURCECRAFT_TOKEN, SOURCECRAFT_REPO, SOURCECRAFT_SITE_URL.

Workflow

Determine the publish date bucket:
- year = YYYY
- year-month = YYYY-MM
Create or update target directory:
- <year>/<year-month>/<page-slug>/
Copy artifact files into that directory
Verify there is an entrypoint (index.html normally)
Ensure .sourcecraft/sites.yaml exists in repo root
Commit and force-push to the SourceCraft repo
Return the final public URL

Publishing command

python3 scripts/publish_static.py --source <dir-or-html> --slug <name> [--date YYYY-MM-DD]

The script:

Clones the SourceCraft repo (shallow)
Ensures .sourcecraft/sites.yaml config exists
Copies artifact into YYYY/YYYY-MM/slug/
Commits and force-pushes
Prints the final public URL

Slug rules

use lowercase letters, digits, and hyphens
keep it short and descriptive
avoid spaces, underscores, Cyrillic

URL contract

Always return the final public URL: <SOURCECRAFT_SITE_URL>/<year>/<year>-<month>/<page-slug>/

Pre-publish validation

Before pushing, verify:

artifact has index.html entrypoint
no absolute local paths in HTML/CSS
no secrets in files
all local assets reachable from the target folder

Safety rules

do not delete unrelated directories in the repo
only replace contents of the target page directory
if overwriting, say so in the result
do not expose the token in output, logs, or committed files

References

Read if needed:

references/publish-checklist.md — operational checklist before pushing