Skills for coding agents in the Tenzir ecosystem, built on the Agent Skills standard.
| Skill | Description |
|---|---|
tenzir-docs |
Tenzir documentation — TQL, operators, functions, integrations, deployment |
tenzir-ocsf |
OCSF schema reference — event classes, objects, attributes, profiles, extensions |
tenzir-create-parser-package |
Scaffold a parser package from sample log data |
tenzir-create-ocsf-mapping |
Create OCSF mapping operators for a parser package |
| Skill | Description |
|---|---|
tenzir-commit-changes |
Stage, split, and commit changes with clean messages |
tenzir-create-pull-requests |
Open PRs, add changelog entries, cross-link docs PRs |
tenzir-review-changes |
Code review with severity ratings and structured findings |
tenzir-design-system |
Frontend design tokens, components, and brand assets |
tenzir-ship |
Changelog entries, release notes, and GitHub releases |
tenzir-update-docs |
Coordinate docs.tenzir.com updates alongside code changes |
tenzir-technical-writing |
Technical documentation style following Google's developer docs guide |
Install all skills into the current project:
npx skills add tenzir/skillsOr install globally:
npx skills add -g tenzir/skillsInstall a specific skill into the current project, for example:
npx skills add tenzir/skills@tenzir-commit-changes
npx skills add tenzir/skills@tenzir-technical-writing
npx skills add tenzir/skills@tenzir-docs
npx skills add tenzir/skills@tenzir-ocsftenzir-docs is generated from the structured Markdown bundle published by
tenzir/docs.
tenzir-ocsf is generated directly from the upstream
ocsf-schema and
ocsf-docs repositories.
This repo uses a richer YAML frontmatter metadata structure to express skill dependencies between sibling skills.
Use unrolled YAML arrays:
---
name: tenzir-create-pull-requests
description: Create and update pull requests for Tenzir projects.
metadata:
requires:
skills:
- tenzir-commit-changes
- tenzir-update-docs
---Notes:
- Use
metadata.requires.skillsfor skill-to-skill dependencies. - Write the dependency list as YAML bullets, not inline bracket syntax.
- Dependency names must match the sibling skill
namefields exactly. - Keep dependent skills self-contained; use dependency metadata to express relationships instead of copying sibling workflow instructions inline.