Menu
Phase-0 smoke test — verifies the feinklang CLI is callable as a bare command from a dependent plugin.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Iteratively improve a feinschliff diagram skill: loop measure, mutate one thing, keep or revert, consolidate, scoring generated output with `feinschliff-builder eval`. Rides the built-in /goal. Use when asked to autoloop against its evals.
Use when a brand pack scaffold exists and you need to close the structural fidelity gap against a source PPTX — runs the verify-loop, then fans out one sub-agent per layout above threshold so each slide is analysed and edited in parallel.
Use when authoring a CLI session recording for the cli-recorder skill. Translates a user's intent ("video of installing kubectl") into a valid recipe.toml through interactive Q&A.
Generate Excalidraw diagrams from a compact DSL with brand-resolved colors. Use for boxes/arrows flow diagrams.
Generate SVG diagrams from a compact DSL with brand-resolved colors. Use for charts, flows, and schematic 2D graphics.
Scaffold v2 `.slide.dsl` layout skeletons for a brand pack from its claude-design HTML. Use when adding new layouts.
| name | feinklang-smoke |
| description | Phase-0 smoke test — verifies the feinklang CLI is callable as a bare command from a dependent plugin. |
This plugin declares feinklang as a dependency. Enabling it should make
Claude Code auto-install and auto-enable feinklang, putting its feinklang
launcher on PATH. That proves the load-bearing coupling model of the
feinschmiede split: share capabilities across plugins (CLIs), never files.
Run, as bare commands (no path, no cd):
command -v feinklang # should print a path
feinklang --version # should print "feinklang <version>"
feinklang voices # lists voices (with ELEVENLABS_API_KEY) or a clean key-missing error
If command -v feinklang resolves and feinklang --version runs, the
dependencies → auto-install → PATH → CLI call chain works. A "key missing"
error from voices still counts as success for this PATH/auto-install check —
it only tests the wiring, not the API call.