handbook-visual-explainer Plugin
Generate beautiful HTML pages for diagrams, diff reviews, plan reviews, slides, and data tables
Install View latest version Open upstream repository
More actions and subscriptions
Compare latest version View observed updates for this package Subscribe with Atom View source record
Only the newest 50 observations in this subscription, not a full archive, upstream releases or installs. Updates-page links keep observation type and package filters; package-page links include all kinds for that package. Your local following list is not sent.
Install
This version is listed in the verified marketplace cc-handbook (repository NikiforovAll/claude-code-rules). Run these in Claude Code, in order:
- Add the marketplace
/plugin marketplace add NikiforovAll/claude-code-rules - Install the plugin
/plugin install handbook-visual-explainer@cc-handbook
These commands install the marketplace's current upstream state, not the pinned commit snapshot on this page; the two can differ.
Contents of latest version 0.10.0 (commit 281c063)
Contents 8
Skill1
-
visual-explainer
plugins/handbook-visual-explainer/skills/visual-explainer/SKILL.mdPermalink
Command7
-
diff-review
plugins/handbook-visual-explainer/commands/diff-review.mdPermalink -
fact-check
plugins/handbook-visual-explainer/commands/fact-check.mdPermalink -
plan-review
plugins/handbook-visual-explainer/commands/plan-review.mdPermalink -
project-recap
plugins/handbook-visual-explainer/commands/project-recap.mdPermalink -
slides
plugins/handbook-visual-explainer/commands/slides.mdPermalink -
visual-plan
plugins/handbook-visual-explainer/commands/visual-plan.mdPermalink -
web-diagram
plugins/handbook-visual-explainer/commands/web-diagram.mdPermalink
Nothing matches.
Dependencies, compatibility and skill declarations
Recorded dependencies 0
No dependency requirements were recorded from plugin.json or marketplace entries. Only manifest fields saved with the snapshot are shown here; dependency declarations in other files are outside the current collection scope.
Recorded compatibility
No compatibility requirement was recorded for this snapshot from plugin.json or a marketplace entry. Only manifest fields saved with the snapshot are shown here. Declarations in a skill's SKILL.md header are collected separately and, when present, shown on their own under “Skill file declarations”; they never overwrite or fill in this value.
Skill file declarations 1
The content below was read separately from the header of each skill file (SKILL.md) at its pinned commit. It is text the file declares about itself, shown as an annotation only. It is stored apart from the snapshot's dependencies and compatibility (manifest fields) above and does not overwrite them. It is not the package license, version, install count or a release record, and none of it is verified.
Evidence scope and limits
- Each entry is one file at one pinned commit, and field states hold for that file only. Components that point to the same file are merged into one entry; files with identical content share one extraction.
- “Declared in file” means the file's header has the field. “Not declared in this file” appears only when the header parsed successfully and lacks the field. “Invalid declaration” means the field is present but its type, length or characters do not meet the requirements; it is never rewritten or truncated. “Not read” means no usable header was obtained (not yet read, read failed, no header, or an unparseable header), which says neither that the field was declared nor that it was not.
- Compatibility and license text are the file's own wording. They do not show that anything runs, are not legal advice, and are not a license verification. metadata.version is only an annotation inside the file; it is not the package version and is not used to judge which is newer.
- This list groups the version's skill components by their recorded source. A listed source may still be unpinned, unread or unavailable; each entry shows its state. Collection runs in bounded batches and does not promise complete coverage.
- A file whose read failed shows a “retry eligible” time. It is only when the collector may try again, not a schedule, and it does not promise a read or completion.
1–1 of 1 skill file sources · As of
-
Not readplugins/handbook-visual-explainer/skills/visual-explainer/SKILL.mdComponents using this file 1
- visual-explainer
plugins/handbook-visual-explainer/skills/visual-explainer/SKILL.md
Fields declared in the file
- Compatibility (declared in file)
- Not readNo usable header, which says neither that it was declared nor that it was not.
- License text (declared in file, unverified)
- Not readNo usable header, which says neither that it was declared nor that it was not.
- metadata.version (file annotation)
- Not readNo usable header, which says neither that it was declared nor that it was not.
This file has no usable extraction record yet, so all three fields show as “Not read”.
- Source
- Open pinned source file
- Repository
nikiforovall/claude-code-rules- Pinned commit
281c0633da69a67d1e64b590f6278db9b897c2c5- File identity
- Regular-file identity recorded
- Blob SHA
449017ba712f6898c12a35362ed60cab5fc7282f- Mode
100644- Identity recorded
- Header parse
- Not read
- Why not read
- The file identity is recorded, but its content has not been read yet.
declaration_unread
No extraction record yet.
- visual-explainer