skills.rest
olaservo
olaservoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

no-prompt

Hide a Skill from user prompt menus via a frontmatter visibility flag.

17|5|Updated Jan 1, 2026
Search Tags:#security#access control#prompt management#user interface#visibility
One-click install
npx skills add https://github.com/olaservo/skilljack-mcp --skill no-prompt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: no-prompt
Source: https://github.com/olaservo/skilljack-mcp/tree/main/src/__fixtures__/skills/user-invocable-false
Command: npx skills add https://github.com/olaservo/skilljack-mcp --skill no-prompt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill remains hidden from the prompt menu, preventing unintended display or access by users.

Core Features & Use Cases

  • Access Control: Manages visibility of specific Skills to restrict user access.
  • Usage Scenario: An administrator configures this Skill to keep it out of user-facing menus, ensuring it's only activated by internal processes or specific conditions.
  • Technical Scope: Implements a visibility flag via metadata to control whether the Skill appears in prompt options, with no user interaction required.

Quick Start

Use the no-prompt skill to keep this Skill hidden from the general prompt menu.

Frequently Asked Questions about no-prompt

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

FAQPage Schema
How do I hide a skill from the user prompt menu and interface?▼

To hide a skill from the user prompt menu, you configure its visibility by setting the user-invocable flag to false within the skill's frontmatter metadata. This prevents it from appearing in user-facing menus.

What does setting the user-invocable flag to false do for access control?▼

Setting the user-invocable flag to false enforces access control by removing the skill from user prompt options. This ensures the skill is only activated by internal processes or specific conditions, preventing direct user invocation.

When should I restrict skill visibility in user prompts?▼

You should restrict skill visibility for internal or backup functions that should not be user-invoked directly. This prevents unintended access or display of administrative skills in general user interfaces.

Can I use no-prompt for internal processes that require no user interaction?▼

Yes, the no-prompt skill is suitable for internal processes requiring no user interaction. It implements a visibility flag via metadata to control whether the skill appears in prompt options, keeping it hidden from general users.

Does configuring skill visibility require modifying internal components or dependencies?▼

Configuring skill visibility does not require external dependencies or complex components. It is achieved by setting a metadata flag in the frontmatter configuration, controlling prompt menu appearance without user interaction.

Related Skills

Explore More Content & Communication Skills→
tvishwanadhatvishwanadha

skills-guide

Define and validate SKILL.md frontmatter conventions for reliable skill discovery.

Community
Intermediate
sannabotdevsannabotdev
22

notifications

Create and manage conditional rules for mobile notification automation.

Community
Intermediate
kristofferaaskristofferaas

convex-security-check

Audits Convex applications for security vulnerabilities with checklists and code examples.

Community
Intermediate
kraftvaerkkraftvaerk

umbraco-current-user-action

Generate custom Umbraco backoffice user menu actions with conditional display.

Official
Intermediate