npx claudepluginhub ojowwalker77/claude-matrix --plugin matrixWant just this skill?
Then install: npx claudepluginhub u/[userId]/[slug]
This skill should be used when the user asks to "run markdown", "execute markdown", "run playbook", "runmd", "test markdown", "execute code blocks", "run shell blocks", or needs to execute shell code blocks from markdown files.
This skill is limited to using the following tools:
RunMD
Execute shell code blocks from markdown files using runmd.
Usage
Parse user arguments: <file.md> [options]
- file: Path to a markdown file containing shell code blocks
- --headless: Run in non-interactive mode (default when invoked from here)
- --fail-fast: Stop on first block failure
- --blocks 0,2,5: Run only specific block indices (0-based)
Process
- Confirm
runmdis installed:which runmd || bun install -g runmd - If no file specified, search for markdown files with shell blocks:
Find *.md files, scan for ```bash/```sh/```zsh/```shell code fences - Show the user which shell blocks exist in the file (list them with indices)
- Execute:
runmd run <file.md> [--fail-fast] [--blocks <indices>] - Report results — pass/fail per block with exit codes
Shell Block Detection
Executable code fences use these languages:
Other code blocks (js, python, etc.) are display-only and not executed.
Environment Variables
runmd auto-loads .env files from the markdown file's directory. Variables referenced as ${VAR_NAME} in shell blocks are substituted before execution.
Modes
| Mode | Command | Use Case |
|---|---|---|
| Headless | runmd run <file> | CI/CD, automation, scripted execution |
| Interactive | runmd <file> | Manual exploration, editing, step-by-step |
Default to headless mode (runmd run) when executing from this skill. Suggest interactive mode if the user wants to explore or edit.
Notes
- Exit code 1 if any block fails in headless mode
--fail-faststops at the first failure instead of running all blocks--blocksaccepts comma-separated 0-based indices to run selectively
Similar Skills
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.