agentleFS
LeostrukaLeostruka/devin-bundle/skills/media-tools/SKILL.md

media-tools

Skill0 starsChanged 3 months agoMITView on GitHub

Use when generating visual artifacts — ASCII art, halftone, dithering, matrix-rain, VHS, pixel-sort, voronoi, and other image/video FX — from images, GIFs, videos, GLB models, or webcam input. Local, offline-first.

  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every call prints {"ok": true, "path": ...} — verify ok before reporting done.

    line 55
  2. Very specific:

    If the user asks for a visual effect or media process NOT covered by the local generators above, MANDATORY: read …

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Media Tools

Local visual-FX generators (grainrad.com pipeline parity). Turns inputs — images, GIF/MP4/WebM, GLB 3D models, webcam frames — into stylized PNG/JPEG/ SVG/GIF/MP4 artifacts. All offline; JSON on stdout.

Where it is

  • Bundle source: extensions/media-tools/
  • Installed: %APPDATA%\devin\extensions\media-tools\ (Windows) or ~/.config/devin/extensions/media-tools/ (POSIX)
  • Deps: pillow, numpy, opencv-python — pinned in requirements.txt, install on demand: python -m pip install -r requirements.txt (no installer venv). cv2 is only needed for webcam/video input.

Tools

  • grainrad.py — unified FX CLI. --input (file | webcam[:N]), --effect, --param k=v (repeatable; prefix adjust./process./bloom./grain./ chromatic./scanlines./vignette. for pipeline stages), --preset, --frames, --fps, --format png|jpeg|svg|txt|threejs.
  • ascii_mancer.py — dense+block ASCII blend → PNG. --cell-detail, --cell-block.
  • glb_input.py — glTF-Binary loader/renderer (orthographic, flat shading); used via --input model.glb in grainrad.

Effects (--list-effects): ascii, blockify, contour, crosshatch, dithering, dots, edgeDetection, halftone, matrixRain, noiseField, pixelSort, threshold, vhs, voronoi, waveLines.

Flow

# discover effects/presets
python grainrad.py --list-effects
python grainrad.py --list-presets

# still image → stylized PNG
python grainrad.py --input photo.png --effect halftone --output out.png

# animated input → GIF (10fps default)
python grainrad.py --input clip.mp4 --effect vhs --output out.gif --fps 12

# webcam capture → effect
python grainrad.py --input webcam:0 --effect ascii --output selfie.png

Every call prints {"ok": true, "path": ...} — verify ok before reporting done. --self-test runs synthetic offline asserts per script.

External catalog — tooooools.app

If the user asks for a visual effect or media process NOT covered by the local generators above, MANDATORY: read extensions/media-tools/knowledge_bases/creative_tooooools.json first — a curated catalog (16 browser tools: stippling, dithering, CRT, cellular automata, displacement, ASCII, animate…) with name, URL, and description per tool. Use it to suggest the right external tool or as reference to implement a local equivalent. Refresh with python update_tooooools_db.py.

Craft suite dispatch (structured media ops)

For document-grade operations (timeline edits, PSD layers, PDF, sheets, slides, CAD, audio) prefer the storytold craft engines over reimplementing: every craft app is agent-native — <app>-cli commands, <app>-cli run, <app>-cli mcp (MCP server), some add --control JSON-lines. All Apache-2.0; spark is MIT for gsplat preview.

  • Bridge: extensions/craft-bridge/bridge.py — doctor, commands <app>, run <app> <command_id> [params] normalized across the suite.
  • Manifests: scene_manifest.py compiles our scene_manifest.json (schema v1) into engine command plans; unknown ops pass through marked unverified — confirm ids via bridge.py commands <app> first.
  • Coverage map: extensions/craft-bridge/ops_matrix.md.
  • gsplat preview: extensions/craft-bridge/spark-view/ (static three.js
    • spark page, opens .PLY/.SPZ).
  • MCP channels: register lazily per mcp-lazy-enablement — enable the one app server the task needs, never the whole suite.

Boundary

  • This skill is for visual artifact generation (stylized media).
  • UI/UX polish of interfaces → impeccable. Diagram artifacts (C4/topology) → architecture-diagrams. Launch videos from project sites → brag.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.