Skill | Added | Review |
|---|---|---|
doc-pr Orchestrate an editorial review for pull requests targeting dev. Reviews changed markdown files and posts a structured comment to the PR. Vale and Dale issues are auto-fixed separately by the vale-autofix workflow. Use this skill whenever a PR involves markdown files in docs/ and targets the dev branch — triggered automatically by the doc-pr GitHub Actions workflow on PR open, sync, or when invoked manually via /doc-pr. | 87 1.92x Agent success vs baseline Impact 77% 1.92xAverage score across 3 eval scenarios Securityby Advisory Suggest reviewing before use Reviewed: Version: 6b797b3 | |
identify-security-vuln-discussion Screen GitHub issues and comments for inadvertent security vulnerability disclosure. Use when: (1) A new issue is created, (2) An issue body is edited, (3) A comment is added or edited, (4) Part of issue intake pipeline. Prevents bypass by editing clean issues to add vulnerabilities later. If a vulnerability is detected in title/body, closes the issue and tags @netwrix/security. If detected in a comment, deletes the comment and posts a security notice. | 91 2.00x Agent success vs baseline Impact 96% 2.00xAverage score across 3 eval scenarios Securityby Advisory Suggest reviewing before use Reviewed: Version: 6b797b3 | |
doc-help Interactive writing assistant for Netwrix documentation. Use when a writer wants hands-on, conversational help: brainstorming structure, drafting a section, editing existing content, incorporating external documents (e.g., .docx files) into existing markdown files, or understanding a style or Vale rule. For fully autonomous tasks (write this entire doc, fix all Vale errors end-to-end), use the tech-writer agent instead. | 85 1.18x Agent success vs baseline Impact 69% 1.18xAverage score across 3 eval scenarios Securityby Passed No known issues Reviewed: Version: 6b797b3 | |
content-fix Autonomous fixer for documentation content issues. Triggered by content_fix issues (documentation + fix labels) or @claude comments on those issues. Reads the issue, identifies affected files, applies fixes following Netwrix writing standards, and pushes a branch. A separate workflow step creates the PR. Asks clarifying questions if the request is ambiguous. | 96 1.60x Agent success vs baseline Impact 96% 1.60xAverage score across 3 eval scenarios Securityby Advisory Suggest reviewing before use Reviewed: Version: 6b797b3 | |
code-of-conduct-check Evaluate GitHub issues against the repository's code of conduct. Use when: (1) A new issue is created and needs conduct review, (2) Part of issue intake pipeline, (3) Evaluating whether issue content violates community guidelines. If violations are found, sanitizes offending content (including title, body, and comments) while preserving technical substance and notifies the author. Intelligently replaces titles when sanitization renders them meaningless. | 72 1.07x Agent success vs baseline Impact 60% 1.07xAverage score across 3 eval scenarios Securityby Advisory Suggest reviewing before use Reviewed: Version: 6b797b3 | |
doc-pr-fix Autonomous fixer for documentation PRs. Triggered by @claude comments on PRs targeting dev. Reads the writer's request and the doc-pr review comment, then applies fixes and commits. Use this skill whenever a writer tags @claude on a documentation PR — not for interactive help (use doc-help for that), but for autonomous, single-shot fixes in CI. | 68 Impact — No eval scenarios have been run Securityby Advisory Suggest reviewing before use Reviewed: Version: 6b797b3 | |
dale Any time a markdown file is edited in the docs/ directory, this skill should be run. | 36 Impact — No eval scenarios have been run Securityby Passed No known issues Reviewed: Version: 6b797b3 | |
derek KB article quality reviewer. Run against KB articles in docs/kb/ to review frontmatter, article type and structure, title format, product names, and keyword quality. Use when editing or reviewing any file under docs/kb/. | 72 Impact — No eval scenarios have been run Securityby Risky Do not use without reviewing Reviewed: Version: 6b797b3 | |
assign-label Assign GitHub issue labels based on content analysis. Use when: (1) A new issue is created and needs categorization, (2) An issue needs relabeling after content changes, (3) Analyzing issue content to determine appropriate labels. Intelligently preserves template-assigned and user-applied labels while updating skill-assigned labels based on current content. | 72 Impact — No eval scenarios have been run Securityby Advisory Suggest reviewing before use Reviewed: Version: 6b797b3 |