disable-model-invocation

Enforce manual activation of skills using the disable-model-invocation frontmatter flag.

1.0k|92|Updated May 22, 2026
One-click install
npx skills add https://github.com/open-gsd/gsd-pi --skill disable-model-invocation-open-gsd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: disable-model-invocation
Source: https://github.com/open-gsd/gsd-pi/tree/main/packages/pi-coding-agent/test/fixtures/skills/disable-model-invocation
Command: npx skills add https://github.com/open-gsd/gsd-pi --skill disable-model-invocation-open-gsd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents automated model invocation by enforcing manual activation of the skill.

Core Features & Use Cases

  • Enforces manual activation to avoid accidental or unauthorized model-triggered actions.
  • Use Case: security-conscious workflows where human oversight is required for sensitive tasks.

Quick Start

Invoke this skill only through explicit human commands and never allow model-initiated execution.

Frequently Asked Questions about disable-model-invocation

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

FAQPage Schema
How do I prevent automated AI model invocation in my workflow?

Manual model invocation requires setting the frontmatter flag disable-model-invocation: true. This enforces human oversight by blocking models from triggering automated actions in sensitive AI workflows.

What is manual invocation in AI safety workflows?

Manual invocation in AI safety is a guardrail that prevents automated model execution by requiring explicit human activation. It enforces human oversight to protect sensitive actions and testing.

When do I need to disable model invocation for sensitive tasks?

You need to disable model invocation for security-conscious workflows requiring strict human oversight. This guardrail prevents accidental or unauthorized model-triggered actions during sensitive tasks and testing.

How to configure a skill for manual activation only?

To configure a skill for manual activation only, apply the frontmatter flag disable-model-invocation: true to mark manual invocability. This prevents models from initiating the skill automatically.

Can I allow model-initiated execution for testing if I use guardrails?

No, this approach strictly blocks model-initiated execution to enforce manual activation for sensitive testing. It serves as a guardrail ensuring actions require explicit human commands rather than automated model triggers.