nis2-compliance

Load the canonical nis2-compliance skill from .opencode/skills/nis2-compliance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ctimmerman-prog/ai-config-opencodeai-first-to-others --skill nis2-compliance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nis2-compliance
Source: https://github.com/ctimmerman-prog/ai-config-opencodeai-first-to-others/tree/main/.cursor/skills/nis2-compliance
Command: npx skills add https://github.com/ctimmerman-prog/ai-config-opencodeai-first-to-others --skill nis2-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This wrapper provides a stable pointer to the canonical nis2-compliance skill located under .opencode/skills/nis2-compliance, ensuring consistency across projects and toolchains.

Core Features & Use Cases

  • Redirects to the canonical skill to maintain a single source of truth for nis2-compliance workflows.
  • Enables teams to reference a standardized nis2-compliance implementation within OpenCode-enabled environments.

Quick Start

Load the canonical nis2-compliance skill from .opencode/skills/nis2-compliance and verify readiness.

Frequently Asked Questions about nis2-compliance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain a single source of truth for NIS2 compliance workflows across multiple projects?

You can maintain a single source of truth for NIS2 compliance by using a wrapper that redirects to a canonical skill file, ensuring consistent regulatory guidance and workflow orchestration across different toolchains.

What is a wrapper skill for in OpenCode regulatory compliance environments?

A wrapper skill in OpenCode regulatory environments acts as a stable pointer to a canonical compliance file, ensuring standardized NIS2 guidance and consistent workflow implementation across various projects.

How do I load the canonical NIS2 compliance skill from an OpenCode project directory?

You load the canonical NIS2 compliance skill by directing the environment to read the SKILL.md file from the .opencode/skills/nis2-compliance directory and verifying any supporting files if present.

Does this NIS2 compliance wrapper require any external dependencies to function?

The NIS2 compliance wrapper requires no external dependencies to function, relying solely on loading the canonical SKILL.md and supporting files from the local .opencode/skills/nis2-compliance directory path.

When should I use a wrapper instead of directly editing NIS2 regulatory compliance rules?

Use a wrapper instead of directly editing rules when you need consistent NIS2 compliance guidance across multiple tools, ensuring the canonical source remains unchanged and standardized across all projects.