Agent skill

Analog Occultism

by magnus919 in magnus919/agent-skills

A skill your agent uses to create subject-neutral images and videos in an analog occultism / industrial CRT noir aesthetic: near-monochrome archival technical atmosphere, severe low-key lighting…

MITAuto-check passedDevelopment

Install Analog Occultism

skills CLI
$ npx skills add magnus919/agent-skills --skill analog-occultism -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install magnus919/agent-skills analog-occultism --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/analog-occultism .claude/skills/analog-occultism && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
analog-occultism
GitHub stars
115
Token cost
~2.5k tokens
SKILL.md length
1,120 words
Files
5 (incl. references)
Skills in repo
131
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses to create subject-neutral images and videos in an analog occultism / industrial CRT noir aesthetic: near-monochrome archival technical atmosphere, severe low-key lighting…

  • Works in 8 steps: Identify the subject and its essential… → Choose one dominant practical source.… → Build the frame around depth and… → …
  • Severe low-key lighting
  • SKILL.md covers Core Workflow, Prompt Pattern, Video Direction and Shared Consistency Rules, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Analog Occultism is an agent skill from magnus919/agent-skills. Use this skill to create subject-neutral images and videos in an analog occultism / industrial CRT noir aesthetic: near-monochrome archival technical atmosphere, severe low-key lighting, tactile signal degradation, industrial geometry, and quiet unresolved tension. Use for portraits, products, environments, interfaces, diagrams, abstract forms, stills, and motion. Do not use for colorful cyberpunk, vaporwave, glossy advertising, conventional horror, or clean digital renders.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `README.md`, `evals/evals.json` and `references/image-prompting.md`). Compatibility notes: Compatible with image-generation and video-generation tools. Video workflows may require a configured video backend and FFmpeg for frame-level verification.

It sits in Development, covering Diagrams. The repository describes itself as: Curated collection of AI agent skills for Hermes and other agent frameworks. The licence is MIT.

When your agent uses it

  • Severe low-key lighting
  • Tactile signal degradation
  • Industrial geometry
  • Quiet unresolved tension

Example prompts

  • “/analog-occultism”

Requirements

  • Compatibility (from SKILL.md): Compatible with image-generation and video-generation tools. Video workflows may require a configured video backend and FFmpeg for frame-level verification.

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Identify the subject and its essential identity. Preserve the subject's
  2. Choose one dominant practical source. Prefer a screen, projector, narrow
  3. Build the frame around depth and obstruction. Use a square, portrait, or tight
  4. Apply the shared visual grammar. Use near-monochrome tonality, crushed blacks,
  5. Choose the capture layer explicitly. There are two related but different looks
  6. Make the recording medium the subject of the image. The result must read as
  7. Add signal treatment as physical evidence, not decoration. Use restrained CRT
  8. Check the result against the consistency rules. Reject outputs that become

What it can do on your machine

Read from SKILL.md and the folder at commit 22b4723. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Compatible with image-generation and video-generation tools. Video workflows may require a configured video backend and FFmpeg for frame-level verification.

    From compatibility in the SKILL.md frontmatter.

Context cost

Analog Occultism loads about 2.5k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 124 tokens; SKILL.md has 1,120 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~124
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from magnus919/agent-skills at commit 22b4723, republished under its MIT licence (© magnus919). 1,120 words, ~2,517 tokens.

Download SKILL.mdSave it as .claude/skills/analog-occultism/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
analog-occultism
description
Use this skill to create subject-neutral images and videos in an analog occultism / industrial CRT noir aesthetic: near-monochrome archival technical atmosphere, severe low-key lighting, tactile signal degradation, industrial geometry, and quiet unresolved tension. Use for portraits, products, environments, interfaces, diagrams, abstract forms, stills, and motion. Do not use for colorful cyberpunk, vaporwave, glossy advertising, conventional horror, or clean digital renders.
compatibility
Compatible with image-generation and video-generation tools. Video workflows may require a configured video backend and FFmpeg for frame-level verification.
license
MIT
metadata.tags
analog-occultism, industrial-crt-noir, archival, retro-futurist, image-generation, video-generation
metadata.source
user-provided aesthetic brief

Analog Occultism / Industrial CRT Noir

Apply a cross-media visual language, not a subject, character, brand, or story. The creative premise is: advanced systems seen through an obsolete recording medium. The result should feel like a mysterious technical artifact recovered from a forgotten research archive: intelligent, secretive, uncanny, severe, tactile, and quietly beautiful.

Core Workflow

  1. Identify the subject and its essential identity. Preserve the subject's recognizable structure, but treat it as evidence, artifact, specimen, icon, or component of a larger system rather than a casual commercial presentation.
  2. Choose one dominant practical source. Prefer a screen, projector, narrow overhead fixture, hard backlight, small industrial light, or source just outside frame. Let it reveal selected surfaces while most of the space falls into black.
  3. Build the frame around depth and obstruction. Use a square, portrait, or tight crop by default; central or slightly off-center placement; tunnel perspective, receding grids, corridors, cables, grilles, foreground obstruction, and a single luminous rectangle or focal object.
  4. Apply the shared visual grammar. Use near-monochrome tonality, crushed blacks, blown ivory highlights, sparse midtones, tactile age, geometric framing, and controlled imperfection. Color is absent or limited to a subtle cold green, blue-gray, desaturated amber, or signal-error cast.
  5. Choose the capture layer explicitly. There are two related but different looks: CRT-display view shows an image on a square monochrome tube; analog-camera documentary view shows a real-world object or scene recorded by a period analog video camera. Do not let the second collapse into the first. For documentary view, state that the subject is physically present in a real location and that the camera is photographing it directly, with practical lens behavior, imperfect focus, exposure, depth of field, reflections, and incidental set detail. The CRT or signal is the camera and recording chain, not the subject's entire reality.
  6. Make the recording medium the subject of the image. The result must read as a low-fidelity monochrome CRT capture or a photograph of one, not a clean digital scene with scanline overlays. Start from a small, soft, interlaced raster: visible scanline structure, phosphor bloom, coarse noise, sync wobble, barrel distortion, clipped whites, crushed blacks, ghosting, focus falloff, dust, scratches, and uneven exposure. Let detail disappear. Signal damage should reduce fidelity while preserving the essential subject.
  7. Add signal treatment as physical evidence, not decoration. Use restrained CRT scanlines, interlacing, film grain, dust, scratches, halation, phosphor bloom, soft focus, edge smearing, vignette, slight barrel distortion, ghosting, minor chromatic misregistration, and uneven exposure. Keep the subject legible.
  8. Check the result against the consistency rules. Reject outputs that become bright, evenly exposed, colorful, glossy, busy, generic glitch art, or polished CGI.

Prompt Pattern

Use the subject-neutral shorthand, then add only the details the specific asset needs:

text
[SUBJECT] shown as a low-fidelity monochrome CRT screen capture, rendered as analog
occultism / industrial CRT noir: visibly soft interlaced raster, coarse phosphor
structure, horizontal scanlines, sync wobble, barrel distortion, ghosting, uneven
tracking, crushed blacks, clipped ivory highlights, one luminous practical source,
claustrophobic geometry, archival technical atmosphere, tactile signal degradation,
quiet unresolved tension, controlled imperfection. It must look like an old recording
of a CRT, not a clean digital image with a scanline filter.

The recording defects are structural and unavoidable: low-resolution broadcast image,
soft focus, horizontal line structure, phosphor persistence trails, unstable vertical
hold, slight horizontal tearing, uneven brightness across the tube, black crush hiding
fine detail, white blooming around the screen, dirty glass, dust, and imperfect analog
capture. Do not render a sharp modern digital photograph and then add cosmetic lines.

Describe concrete objects, spatial relationships, and the information the viewer must understand. Do not rely on mood words alone. If typography is necessary, use original archival-technical labels, all-caps system annotations, monospaced text, framed emblems, diagrams, readouts, indexes, or specimen-card structures. Keep text sparse; models may render small annotations imperfectly.

For detailed still-image prompt blocks, reference-based generation, and negative prompt guidance, read references/image-prompting.md. If a user supplies a visual reference, use the actual reference in the image tool; a text description is not a substitute for the pixels.

Video Direction

Preserve the same visual grammar across time. Motion should be slow, deliberate, mechanical, and slightly uncanny:

  • slow push-ins or pull-backs, mechanical tracking, and subtle lateral drift;
  • focus breathing, screen flicker, small exposure shifts, servo-like camera motion;
  • long pauses, sparse cuts, gradual reveals, and loops that return unresolved;
  • camera behavior suggesting an automated observer or a machine becoming aware.

Describe motion as a restrained physical event, not as a collection of effects. Keep one dominant light source stable enough to anchor the shot, then allow small changes in flicker, exposure, focus, dust, or tracking. Use image-to-video when the opening composition matters, keyframes when a transformation or style continuity matters, and continuation when extending an established shot. Do not turn scanlines or jitter into frenetic glitch animation.

Before any video generation, load the configured video backend's prompting guide. For FLUX 3 workflows, use the video-generation skill and its required prompting guide, then verify a bounded sample of rendered frames with FFmpeg and visual inspection. Read references/video-prompting.md for shot templates and continuity rules.

Show full SKILL.md (405 more words)Show less

Shared Consistency Rules

Each asset should contain most of these ten signals:

  1. near-monochrome tonality;
  2. one dominant luminous source;
  3. severe black-and-white contrast;
  4. strong negative space;
  5. tactile analog or archival texture;
  6. geometric or industrial framing;
  7. hidden technical depth;
  8. quiet, unresolved tension;
  9. controlled imperfection;
  10. a discovered artifact quality rather than fresh manufacture.

The subject can change. The visual grammar cannot.

Avoid

  • Screen-capture fidelity: when the brief calls for CRT or recovered footage, name the raster defects explicitly: low resolution, soft focus, visible scanlines, interlacing, phosphor persistence, sync wobble, tracking errors, barrel distortion, clipped whites, crushed blacks, ghost trails, and dropped detail. A clean image with a decorative scanline overlay is a failure, not a pass.

Do not default to colorful cyberpunk, vaporwave, broad RGB neon, teal-and-orange cinema grading, clean SaaS minimalism, glossy product advertising, high-key studio photography, generic hacker imagery, excessive digital corruption, random interface clutter, cartoon horror, jump scares, gore, conventional horror iconography, or perfectly polished CGI. Do not use nostalgic retro props merely as decoration. Effects must never become more noticeable than the subject.

Reference and QA Boundaries

  • Use reference images to preserve identity, composition, or a visual anchor, but do not promise pixel-exact style transfer from an edit model.
  • For people and creatures, inspect anatomy before judging style. Clearly visible hands, limbs, cables, straps, and connected objects must have plausible geometry.
  • For typography and diagrams, verify every visible label, relationship, arrow, and hierarchy. Never invent technical data because the aesthetic suggests annotations.
  • For video, inspect sampled frames rather than trusting generation metadata. Confirm the dominant light, subject identity, motion restraint, and absence of accidental color or digital corruption. Sampling proves only the sampled times.
  • After one or two materially different failed generations, stop and report the model limitation or change the shot. Do not hide a failed subject behind more darkness or degradation.

When Not to Use

Use another aesthetic skill for a named brand's locked visual identity, a specific site's cover rules, colorful cyberdelic work, or a production video workflow that needs backend-specific operation rather than aesthetic direction. This skill defines visual language; it does not replace image-gen-reference, video-generation, or ffmpeg for their respective operational procedures.

Completion

The skill is complete when the still or shot preserves the subject, expresses the shared visual grammar, passes the relevant image or frame-level checks, and has an explicit note of any unresolved model limitation or sampling boundary.

© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in analog-occultism of magnus919/agent-skills.

  • SKILL.md
  • README.md
  • evals/evals.json
  • references/image-prompting.md
  • references/video-prompting.md

Open the folder on GitHubat commit 22b4723

Compare with similar skills

Analog Occultism next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Analog Occultism compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Analog Occultism this skillmagnus919/agent-skills115—~2.5kAutomated safety check: PassMIT
Archify Diagramstt-a1i/archify82k—~2.9kAutomated safety check: PassMIT
JSON Canvasheyitsnoah/claudesidian2.6k18 repos~3.5kAutomated safety check: PassMIT
Diagram Designcathrynlavery/diagram-design49k1 repos~7.6kAutomated safety check: PassMIT
Fireworks Tech Graphtisfeng/Easydict15k1 repos~1.4kAutomated safety check: PassMIT
Excalidraw Diagramcoleam00/excalidraw-diagram-skill5k2 repos~6.1kAutomated safety check: PassNone

Similar skills

  • Archify Diagrams

    tt-a1i/archify

    Creates interactive architecture, workflow, sequence, data-flow and lifecycle diagrams as standalone HTML with inline SVG, themes and image or video export.

    82k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed
  • JSON Canvas

    heyitsnoah/claudesidian

    Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections.

    2.6k GitHub starsUsed in 18 repos~3.5k tokens
    DevelopmentAuto-check passed
  • Diagram Design

    cathrynlavery/diagram-design

    Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.

    49k GitHub starsUsed in 1 repo~7.6k tokens
    DevelopmentAuto-check passed
  • Fireworks Tech Graph

    tisfeng/Easydict

    Create precise SVG technical diagrams, export PNG or offline HTML, and animate supported semantic SVGs to GIF.

    15k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Excalidraw Diagram

    coleam00/excalidraw-diagram-skill

    Create Excalidraw diagram JSON files that make visual arguments.

    5k GitHub starsUsed in 2 repos~6.1k tokens
    DevelopmentAuto-check passed
  • Draw.io Diagram Studio

    Agents365-ai/drawio-skill

    Creates and edits editable draw.io diagrams from descriptions, code, infrastructure files, SQL and API schemas, with sync, review, test and export tools.

    10k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check: notes

More from magnus919/agent-skills

All 131 skills in this repo
  • Artifact Pyramids

    magnus919/agent-skills

    Organize durable agent research outputs as summaries, analysis, and evidence dossiers.

    119 GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • Ascii City Engine

    magnus919/agent-skills

    Build portable, first-person colored ASCII city engines and small GIS-derived city packs.

    119 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Color Management

    magnus919/agent-skills

    Manage color workflows with ICC profiles, working spaces, gamut mapping, and color science.

    119 GitHub stars~2.6k tokensUpdated today
    Auto-check: notes
  • Data Scientist

    magnus919/agent-skills

    A skill your agent uses for PhD-level expertise in data science, statistics, and machine learning: rigorous statistical analysis, experimental design, causal inference, advanced modeling, research…

    119 GitHub stars~4.1k tokensUpdated today
    Auto-check passed
  • Docker Compose

    magnus919/agent-skills

    Use Docker Compose to define, run, debug, and harden multi-container applications.

    119 GitHub stars~2k tokensUpdated today
    Auto-check: notes
  • Fpga Development

    magnus919/agent-skills

    Design, review, simulate, and verify FPGA logic using explicit RTL contracts, clock and reset models, CDC analysis, timing constraints, and reproducible implementation evidence.

    119 GitHub stars~2.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Analog Occultism

What does Analog Occultism do?

A skill your agent uses to create subject-neutral images and videos in an analog occultism / industrial CRT noir aesthetic: near-monochrome archival technical atmosphere, severe low-key lighting…. Analog Occultism is an agent skill from magnus919/agent-skills. Use this skill to create subject-neutral images and videos in an analog occultism / industrial CRT noir aesthetic: near-monochrome archival technical atmosphere, severe low-key lighting, tactile signal degradation, industrial geometry, and quiet unresolved tension.

When should I use Analog Occultism?

Analog Occultism fits situations like: severe low-key lighting; tactile signal degradation; industrial geometry; quiet unresolved tension.

How do I install Analog Occultism in Claude Code?

Run `npx skills add magnus919/agent-skills --skill analog-occultism -a claude-code`. Or copy the skill folder (analog-occultism in magnus919/agent-skills) into .claude/skills/analog-occultism in your project. Claude Code loads it when a task matches its description.

How do I install Analog Occultism in Codex?

Run `npx skills add magnus919/agent-skills --skill analog-occultism -a codex`. Or copy the skill folder (analog-occultism in magnus919/agent-skills) into .agents/skills/analog-occultism in your project. Codex loads it when a task matches its description.

Can I use Analog Occultism in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add magnus919/agent-skills --skill analog-occultism -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analog-occultism, .gemini/skills/analog-occultism, .github/skills/analog-occultism and .opencode/skills/analog-occultism in your project.

What does Analog Occultism need to run?

SKILL.md names no scripts, command-line tools or credentials: Analog Occultism is instructions for the agent only. Compatibility (from SKILL.md): Compatible with image-generation and video-generation tools. Video workflows may require a configured video backend and FFmpeg for frame-level verification..

Does Analog Occultism access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Analog Occultism safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Analog Occultism use?

Analog Occultism is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Analog Occultism use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Analog Occultism?

Skills that share tags, products or a category with Analog Occultism: Archify Diagrams (tt-a1i/archify, 82k stars), JSON Canvas (heyitsnoah/claudesidian, 2.6k stars), Diagram Design (cathrynlavery/diagram-design, 49k stars) and Fireworks Tech Graph (tisfeng/Easydict, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Analog Occultism?

magnus919 (a GitHub user) maintains it in magnus919/agent-skills, which has 115 GitHub stars. The repository holds 131 skills in this directory. The repository was last updated on October 10, 2026.

Source: magnus919/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.