skills.rest
wadebee
wadebeeCOMMUNITY
Explore all skills by this author →
GitHub

shimmy-tool-opnsense-mcp-admin

Guide OPNsense admin MCP maintenance using layered context files and change-window approvals.

2|Updated Feb 14, 2026
Search Tags:#tooling#mcp#podman#context-first#opnsense#shimmy
One-click install
npx skills add https://github.com/wadebee/shimmy --skill shimmy-tool-opnsense-mcp-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shimmy-tool-opnsense-mcp-admin
Source: https://github.com/wadebee/shimmy/tree/main/tools/opnsense-mcp-admin/agent
Command: npx skills add https://github.com/wadebee/shimmy --skill shimmy-tool-opnsense-mcp-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you work with the context-first OPNsense MCP admin tool without losing track of the repository’s layered guidance, safety constraints, and version-specific instructions.

Core Features & Use Cases

  • Safe admin workflows: Follow the canonical instructions for change-capable OPNsense MCP operations with the required safeguards.
  • Context-aware maintenance: Read the repository and tool-local context files in the intended order so edits stay aligned with the surrounding architecture.
  • Version-specific guidance: Use the tool’s versioned instructions to understand how the admin variant behaves and what protections apply.

Quick Start

Read the skill’s linked context files in order and then use the OPNsense admin MCP tool while respecting change-window approval and named Podman secret safeguards.

Frequently Asked Questions about shimmy-tool-opnsense-mcp-admin

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

FAQPage Schema
How do I safely manage OPNsense admin API operations using MCP?▼

To safely manage OPNsense admin API operations, you must follow a context-first workflow that enforces change-window approval and uses named Podman secrets to protect sensitive credentials during repository changes.

What is the context-first workflow for OPNsense MCP maintenance?▼

The context-first workflow requires reading layered guidance files and versioned tool directories in a specific canonical order before making edits, ensuring all repository changes stay aligned with the surrounding architecture and safety constraints.

Do I need Podman secrets configured to use the OPNsense admin MCP tool?▼

Yes, you need named Podman secrets configured and must adhere to change-window approval protocols to safely perform any change-capable admin API operations within the OPNsense MCP environment.

How do I navigate version-specific instructions for OPNsense MCP admin tasks?▼

You navigate version-specific instructions by accessing the tool’s versioned directories and reading the canonical context hierarchy in order, which defines how the admin variant behaves and what specific protections apply.

What are the constraints for modifying the OPNsense MCP repository?▼

Modifications to the OPNsense MCP repository are constrained by layered guidance files requiring strict adherence to change-window approvals, named Podman secret usage, and the canonical context hierarchy to prevent unsafe operations.

Related Skills

Explore More Software Engineering Skills→
wadebeewadebee
2

shimmy-tool-opnsense-mcp-read-only

Guide read-only OPNsense MCP workflows with Podman secrets and endpoint validation.

Community
Intermediate
JDL440JDL440

Dashboard Surface Retirement

Removes deprecated dashboard UI while preserving backend maintenance endpoints and storage.

Community
Intermediate
iamcapoteiamcapote

develop-secure-contracts

Integrate OpenZeppelin security patterns into Solidity, Cairo, Stylus, and Stellar smart contracts.

Community
Advanced
wadebeewadebee
2

shimmy-tool-logmine

Guide Logmine Shimmy maintenance using canonical context files and local-image workflows.

Community
Basic