sourcecraft-publisher
Publish static page artifacts to SourceCraft Sites (Yandex infrastructure, works in Russia), with advisory image optimization and an original-image path. Use when a static page/React artifact needs to be deployed to SourceCraft under YYYY/YYYY-MM/page-slug directory layout.
What this skill does
# 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. ```bash cp config/.env.example config/.env ``` Required: `SOURCECRAFT_TOKEN`, `SOURCECRAFT_REPO`, `SOURCECRAFT_SITE_URL`. ## Workflow 1. Determine the publish date bucket: - year = `YYYY` - year-month = `YYYY-MM` 2. Create or update target directory: - `<year>/<year-month>/<page-slug>/` 3. Copy artifact files into that directory 4. Verify there is an entrypoint (`index.html` normally) 5. Ensure `.sourcecraft/sites.yaml` exists in repo root 6. Commit and force-push to the SourceCraft repo 7. Return the final public URL ## Publishing command ```bash python3 scripts/publish_static.py --source <dir-or-html> --slug <name> [--date YYYY-MM-DD] [--image-max-kb 500] ``` The script: - Clones the SourceCraft repo (shallow) - Ensures `.sourcecraft/sites.yaml` config exists - Copies artifact into `YYYY/YYYY-MM/slug/` - Optimizes oversized `.jpg`, `.jpeg`, `.png`, and `.webp` images before commit - Commits and force-pushes - Prints the final public URL ## Image optimization Image optimization is a recommendation, not a hard requirement. By default, the publishing script tries to keep each raster image under `500KB` by stripping metadata, recompressing, and resizing long edges when needed. Use `--image-max-kb <kb>` for a different target. Use `--keep-large-images` or `--image-max-kb 0` when the user explicitly needs original-size images (for example, a full-resolution infographic, map, or downloadable media asset). The original `--source` artifact is not changed. Optimization happens only after files are copied into the publish repo target directory. If Pillow/uv is unavailable or optimization fails, continue publishing originals and mention the warning. Manual console run for a prepared artifact: ```bash uv run --with pillow python3 scripts/optimize_images.py <artifact-dir> --max-kb 500 ``` ## 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 - oversized raster images are optimized when practical, unless original-size sharing is intentional - 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
Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.