unreachable-skill

To validate non-invocable skills in CI, load the skill in a test harness and confirm it cannot be executed. This verifies that frontmatter flags like user-invocable: false and disable-model-invocation: true correctly prevent users and agents from triggering the skill.

To prevent skill execution, the required frontmatter flags are user-invocable: false and disable-model-invocation: true. These access-control settings ensure the skill cannot be triggered by users or agents during testing and CI environments.

Access-control validation for restricted skills works by using a non-invocable unit to test gating logic and error handling. It confirms that systems respect disable-model-invocation settings and user restrictions, ensuring the skill remains untriggerable.

Yes, you can use a non-invocable skill to test invocation safety in development environments. It serves as a testing utility to verify that gating logic correctly prevents execution when user-invocable: false and disable-model-invocation: true flags are applied.

Testing non-invocable skills is necessary to enforce access controls and verify invocation safety. It confirms that your system's gating logic properly respects disable-model-invocation settings and prevents restricted skills from being triggered by users or agents.

A non-invocable skill in software engineering is used to validate access-control and invocation safety. It ensures certain skills cannot be triggered, applying frontmatter flags to prevent execution by users or agents in development and CI environments.