Two files, one repository
nicobailon/visual-explainer ships 1 format across 4 indexed files. The question worth asking is whether the second one says anything the first does not.
| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 0 | 0 | — |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 0 | 0 | — |
What each file covers
Sections
neither file has anyCommands
neither file has anySection tags
neither file has anyLine diff
nicobailon/visual-explainer · configs/codex/AGENTS.md
@@ −1 @@
1Use the canonical `visual-explainer` skill from `plugins/visual-explainer/`.
2
3For Codex CLI, copy the skill to `~/.codex/skills/visual-explainer`. If your Codex build supports prompt templates, you may also copy `plugins/visual-explainer/commands/*.md` to `~/.codex/prompts/`.
4
5Activate by asking Codex to use `$visual-explainer` or the `visual-explainer` skill before generating diagrams, diff reviews, plan reviews, slide decks, or complex tables. Generated pages go to `~/.agent/diagrams/`; opening the browser may depend on Codex sandbox permissions.
6
7Command-template support varies by Codex version. If prompts are unavailable, read the relevant command file and follow the skill workflow manually.
8
nicobailon/visual-explainer · configs/openclaw/AGENTS.md
@@ +1 @@
1Use the canonical `visual-explainer` skill from `plugins/visual-explainer/`.
2
3OpenClaw support is lightweight rules guidance, not a native plugin adapter. Point the agent at `plugins/visual-explainer/SKILL.md` and ask it to follow that workflow when producing diagrams, visual reviews, slide decks, or complex tables.
4
5Generated pages should be written to `~/.agent/diagrams/` and opened in a browser when the environment allows it. If OpenClaw does not support command templates, read the matching file under `plugins/visual-explainer/commands/` and execute its instructions manually.
6
@@ −1 +1 @@
11 Use the canonical `visual-explainer` skill from `plugins/visual-explainer/`.
22
3−For Codex CLI, copy the skill to `~/.codex/skills/visual-explainer`. If your Codex build supports prompt templates, you may also copy `plugins/visual-explainer/commands/*.md` to `~/.codex/prompts/`.
3+OpenClaw support is lightweight rules guidance, not a native plugin adapter. Point the agent at `plugins/visual-explainer/SKILL.md` and ask it to follow that workflow when producing diagrams, visual reviews, slide decks, or complex tables.
44
5−Activate by asking Codex to use `$visual-explainer` or the `visual-explainer` skill before generating diagrams, diff reviews, plan reviews, slide decks, or complex tables. Generated pages go to `~/.agent/diagrams/`; opening the browser may depend on Codex sandbox permissions.
6−
7−Command-template support varies by Codex version. If prompts are unavailable, read the relevant command file and follow the skill workflow manually.
5+Generated pages should be written to `~/.agent/diagrams/` and opened in a browser when the environment allows it. If OpenClaw does not support command templates, read the matching file under `plugins/visual-explainer/commands/` and execute its instructions manually.
86
