This release introduces the OCSF plugin for navigating the Open Cybersecurity Schema Framework with versioned reference documentation, and the Excalidraw plugin for generating valid diagrams. It also adds a reusable GitHub Action for automated changelog entries in CI.
Breaking changes include removing the meta and auto-update plugins from the marketplace.
💥 Breaking Changes
Section titled “💥 Breaking Changes”Meta plugin removed from marketplace
Section titled “Meta plugin removed from marketplace”Dec 25, 2025 · @mavam, @claude
The meta plugin provided guidance for managing plugins in this marketplace. Since it was self-referential and only useful within this repository, the managing-plugins skill has been moved to .claude/skills/ as a project-level skill.
Users who had meta@tenzir enabled should remove it from their settings. The validation script now detects stale plugin references in .claude/settings.json to prevent this issue in the future.
🚀 Features
Section titled “🚀 Features”Excalidraw diagram generation plugin
Section titled “Excalidraw diagram generation plugin”Generate valid Excalidraw diagrams with the new excalidraw:diagramming skill.
The skill provides comprehensive reference documentation for all element types
(shapes, text, arrows, lines, freedraw, images, frames, polygons) and styling
properties (colors, fill patterns, positioning, grouping). All values and
constants are derived from the Excalidraw source code, ensuring compatibility
with excalidraw.com and VS Code extensions.
OCSF plugin with understanding-ocsf skill
Section titled “OCSF plugin with understanding-ocsf skill”Dec 28, 2025 · @mavam, @claude
The OCSF plugin provides comprehensive schema navigation for the Open Cybersecurity Schema Framework through the understanding-ocsf skill. The skill guides users through five core OCSF concepts: attributes, objects, classes, profiles, and extensions, with detailed documentation for each.
Reference documentation is dynamically generated from schema.ocsf.io covering all stable versions from 1.0.0 to 1.7.0. The generator fetches versioned schemas and creates Markdown references for 83 event classes and 170 object types, organized by the 8 OCSF categories (System, Findings, IAM, Network, Discovery, Application, Remediation, Unmanned). Progressive disclosure is achieved through hierarchical index files that link from the main index to version-specific indices to individual class and object documentation.
Generated references are excluded from git due to their size (approximately 2.6 MB across 8 versions), and users run the generation script as needed after installation.
Reusable GitHub Action for automated changelog entries
Section titled “Reusable GitHub Action for automated changelog entries”Dec 28, 2025 · @mavam, @claude · #2
A reusable GitHub Action enables automated changelog entry creation for pull requests. The action uses the changelog:adder agent to analyze PR changes, determine if they are user-facing, and create appropriate changelog entries.
The action is idempotent, skipping execution if an entry already exists for the PR. After creating an entry, it posts a formatted comment to the PR with metadata and sync instructions for both Git and Jujutsu workflows.
Other repositories can integrate this action into their CI workflows by referencing tenzir/claude-plugins/.github/actions/changelog-adder@main and providing a Claude Code OAuth token.
🔧 Changes
Section titled “🔧 Changes”README documentation standards and validation
Section titled “README documentation standards and validation”Dec 29, 2025 · @mavam, @claude
Plugin READMEs now follow stricter documentation standards with validation.
The documentation script extracts title, description, features, and usage sections from READMEs. New requirements ensure consistency:
- Intro paragraph: 2-3 sentences after the title, kept up to date when plugins change
- Features section: Required with emoji-prefixed bullet points highlighting what the plugin provides
- Usage section: Required with real-world examples showing how to use each component
- Heading style: Standardized on
## ✨ Featuresand## 🚀 Usage
The validation script now enforces these requirements, catching missing sections and incorrect heading styles. This is important because the documentation at docs.tenzir.com relies on this structure.